Synopsis: This is a very good first pass but it will need a second pass to be completed. 

Below I will review the goals of the tasks.  Sorry for the lack of formatting in this forum.  View a cleaner copy at: http://www.peregrinehw.com/downloads/SpamAssassin/admin-crash/review1.txt.


Technical Requirements:

COMPLETED - 1 - Use a technical solution to submit your end-product that shows how we can identify changes you've made for approval.  In Microsoft Word and ASF OpenOffice.org Writer, you can use the "Track Changes" feature.  You can download Open Office from http://www.openoffice.org/


UNCERTAIN - 2 - You should include any and all sources for research. We are not expecting you to write the information first-hand and we may have to remove information that is copyrighted and/or improperly sourced.

KAM: UNCERTAIN - I do not see any sources.  Did you add any material to the document?

For example, items in the two Text files need sources.  They are just scraps of info that need time and attention.

You also don't have your name on the document.


Technical Tasks:


DONE-ish - 1 - Take the technical information in this document: http://www.peregrinehw.com/presentations/macsysadmin_2009_presentation_final_post.pdf

KAM: As you noted, the future tweaks items are missing.  In an engineering document, you must not be concerned with be 100% correct as being 100% thorough.  In the military, they refer to this as Unk Unks or Unknown Unknowns.  The first job is to identify all the unknowns.

So if you identify that an admin needs to know about Acronym XYZ but you don't know the meaning, you LEAVE IT IN THE DOCUMENT with a phrase that clearly states something to say "This needs more information."

This means anything you skipped over needs to be added to the document.


UNCERTAIN - 2 - Take the technical information in this document: http://www.peregrinehw.com/downloads/SpamAssassin/admin-crash/email-compendium-notes.txt

KAM: Appears verbatim but missing things. Where is last external relay, for example?


UNCERTAIN - 3 - Take the technical information in this document: http://www.peregrinehw.com/downloads/SpamAssassin/admin-crash/additional-email-compendium-notes.txt

KAM: As noted above, especially the two text files are just scraps of notes.  While the PDF is very polished, the other documents are not and the two need to be more suitably combined


LACKING SOME POLISH - 4 - Read it, organize it and clarify it to produce a document suitable for an Administrator Crash Course on Email and Spam using track changes.

KAM: I believe you missed the clarify points of the document.  More editing is needed especially for brevity.  However, if you don't understand it well enough to edit, you might need to actually research some blocks and ask questions.  I'm not looking for a 100% understanding but the goal is that you and others could read this document to get a crash course in lingo and technology needed to have a conversation about anti-Spam.


UNCERTAIN - 5 - Extract any Acronyms in the document and produce and Appendix of Accronyms in Alphabetical.

KAM: What would be better is a single page or so of acronyms in addition to the definitions after completing the document.  This will allow for things like a table of contents to be added just by giving things Heading levels.  You sort of merged the two concepts and not in Alphabetical order. 



Bonus tasks after Technical Tasks above are approved:

KAM: No Bonus tasks attempted.  Feel free to do so.  Or would you like us to see if we can create a separate task.