Email Schedules

This area is for estimating what tasks will be necessary for various email-related schedules, and to make a first SWAG at how long each of those tasks will take. The purpose of these schedules is to figure out how many people OSAF will need to hire.

Tasks are not necessarily in order, and it's likely that there will be more than one person working on some of these tasks. This is just to figure out person-hours needed.

If you think these schedules are inaccurate, please please add your estimates with your initials. For example, if DuckySherwood thinks that the floss recycling project will take one to two weeks and MabelZellaGarcia thinks it will take three to four weeks, there should be an entry that looks something like this:

• Floss recycling project.
  • KDS: 1-2 weeks
  • MZG: 3-4 weeks

(And please add your initials to the initials-to-names translation.)

---

For each developer:

• Get up to speed on OSAF (finding bathrooms, etc) and the existing code base.
  • KDS: 1-2 weeks
• Get up to speed on Python (less productivity over the course of the project than someone who already knows Python).
  • KDS: 1-2 weeks

---

Alternative cases for giving Chandler POP, IMAP, and SMTP email libraries:

• ScheduleForDevelopingEmailLibrariesInHouse
  • KDS: 26-48 weeks
• ScheduleForIntegratingExistingLibraries
  • KDS: 6-15 weeks

---

Regardless of case:

• Time to integrate an email parsing library

(more tasks/schedules, including preferences dialogs, UI, user feedback, etc. to follow)

Initials-to-name translations

Please alphabetize by first letter:

• KDS = DuckySherwood
• MZG = MabelZellaGarcia (a phony person, here just as an example...)

-- DuckySherwood - 18 Jun 2003