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.

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...).

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.

Re-organise and improve the skeleton providing a better more concise set of pages

Organise some sprints to refine and improve the pages to make them comprehensive to everyone.

Mentor students as part of the GSoC program, understand the good parts and the pain parts for both student and mentor.

Mentor GSoC students.
Hold a regular meeting for mentors to discuss progress, feedback, issues.
Look at ways to bring students into the community to get feedback, and feel involved.

Review the Mentoring process from both student and mentor perspectives, from start to end, look for and suggest improvements and goals for 2012.
Encourage GSoC students to keep contributing.

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

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).

Examine ways of improving the review system, including but not limited to distribution of reviews, initial response times, follow-up response times.

Improve communication to Thunderbird developers and other interested parties.

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