Thunderbird/Development/Goals/2011

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

Plans

Quarter 1 Goals

1. Contributor Funnel
   • Basic development page(s) with pointers to existing documentation on developing Thunderbird, and contacts for where to get help.
   • Analysis of what is missing from the existing pages, and initial skeleton pages for those missing.
2. L10n
   • Get a contact
3. Reviews
   • Implement / obtain a sane metrics gathering system
   • Reduce outstanding Mailnews Core reviews to less than one month old
4. Communication
   • Analyse existing developer communication methods and propose two improvements.

Quarter 2 Goals

1. Contributor Funnel
   • Re-organise and improve the skeleton providing a better more concise set of pages
2. L10n
3. Reviews
   • Examine ways of improving the review system, including but not limited to distribution of reviews, initial response times, follow-up response times.
4. Communication
   • Implement one of the proposed improvements.
   • Get feedback on it.
   • Look at refining it.

Quarter 3 Goals

1. Contributor Funnel
   • Organise some sprints to refine and improve the pages to make them comprehensive to everyone.
2. L10n
3. Reviews
4. Communication

Quarter 4 Goals

1. Contributor Funnel
   • Organise some sprints to refine and improve the pages to make them comprehensive to everyone.
2. L10n
3. Reviews
4. Communication

Goal 1: Contributor Funnel for development

By the end of 2011 have in place a comprehensive set of web pages for a development funnel/introduction for contributors.

The funnel being a page where contributors can start (e.g. how to contribute to Thunderbird, here's all the information you need to know...).

Goal 2: L10n contact

Get an new L10n contact for Thunderbird and hooked up with the community

Goal 3: Reviews

Improve review reaction times for Thunderbird and MailNews Core Products, to encourage more contributions by getting responses to patches quicker.

Subgoals

• Subgoal 3.1: By the end of Q1, reduce all outstanding MailNews Core reviews to no more than a month old.
• Subgoal 3.2: For the Thunderbird product, achieve an average review time of 2 weeks during 2011.
• Subgoal 3.3: For the MailNews Core product, achieve an average review time of 3 weeks during 2011.

(note: slightly longer time for MailNews Core, as I don't know how much we'll be able to get non-Mozilla Messaging folks on board with this).

Goal 4: Communication

Improve communication to Thunderbird developers and other interested parties.

Subgoal

• Subgoal 4.1: Post at least one Thunderbird specific (i.e. not experiments/labs) blog post each month by a team member.