Thunderbird/Development/Goals/2011: Difference between revisions

← Older edit

Thunderbird/Development/Goals/2011 (view source)

Revision as of 20:04, 1 March 2011

444 bytes removed , 1 March 2011

no edit summary

Standard8

canmove, Confirmed users, Bureaucrats and Sysops emeriti

3,628

edits

@@ Line 1: / Line 1: @@
 {{Draft}}
-== Goal 1: Contributor Funnel for development ==
+== Plans ==
-''By the end of 2011 have in place a comprehensive set of web pages for a development funnel/introduction for contributors.''
+=== Quarter 1 Goals ===
-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...).
+# 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.
+# L10n
+#* Get a contact
+# Reviews
+#* Implement / obtain a sane metrics gathering system
+#* Reduce outstanding Mailnews Core reviews to less than one month old
+# Communication
+#* Analyse existing developer communication methods and propose two improvements.
-=== Plan ===
+=== Quarter 2 Goals ===
-==== Q1 ====
+# Contributor Funnel
+#* Re-organise and improve the skeleton providing a better more concise set of pages
+# L10n
+# Reviews
+#* Examine ways of improving the review system, including but not limited to distribution of reviews, initial response times, follow-up response times.
+# Communication
+#* Implement one of the proposed improvements.
+#* Get feedback on it.
+#* Look at refining it.
-* Basic development page(s) with pointers to existing documentation on developing Thunderbird, and contacts for where to get help.
+=== Quarter 3 Goals ===
-* Analysis of what is missing from the existing pages, and initial skeleton pages for those missing.
-==== Q2 ====
+# Contributor Funnel
+#* Organise some sprints to refine and improve the pages to make them comprehensive to everyone.
+# L10n
+# Reviews
+# Communication
-* Re-organise and improve the skeleton providing a better more concise set of pages
+=== Quarter 4 Goals ===
-==== Q3 & Q4 ====
+# Contributor Funnel
+#* Organise some sprints to refine and improve the pages to make them comprehensive to everyone.
+# L10n
+# Reviews
+# Communication
-* Organise some sprints to refine and improve the pages to make them comprehensive to everyone.
+== Goal 1: Contributor Funnel for development ==
-== Goal 2: Mentoring ==
+''By the end of 2011 have in place a comprehensive set of web pages for a development funnel/introduction for contributors.''
-''Mentor students as part of the GSoC program, understand the good parts and the pain parts for both student and mentor.''
+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...).
-=== Plan ===
+== Goal 2: L10n contact ==
-==== Q1 ====
+''Get an new L10n contact for Thunderbird and hooked up with the community''
-* Review 2010 GSoC.
-* Propose at least 10 projects for GSoC.
-* Encourage new/recent contributors to take part.
-* Find possible mentors. Determine basic selection criteria.
-==== Q2 & Q3 ====
-* 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.
-==== Q4 ====
-* 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.
 == Goal 3: Reviews ==
@@ Line 57: / Line 65: @@
 (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).
-=== Plan ===
-==== Q1 ====
-* Implement / obtain sane metrics gathering system for review data. Achieve 3.1.
-==== Q2 ====
-* Examine ways of improving the review system, including but not limited to distribution of reviews, initial response times, follow-up response times.
-==== Q3 & Q4 ====
-* to be decided on the outcome of Q2.
 == Goal 4: Communication ==
@@ Line 79: / Line 73: @@
 * Subgoal 4.1: Post at least one Thunderbird specific (i.e. not experiments/labs) blog post each month by a team member.
-=== Plan ===
-==== Q1 ====
-* Analyse existing developer communication methods and propose two improvements.
-==== Q2 ====
-* Implement one of the proposed improvements.
-* Get feedback on it.
-* Look at refining it.
-==== Q3 & Q4 ====
-* To be defined depending on the outcome of Q1 & Q2