Engineering Community Team/Planning/2014/Q1

2013-Q4

Engineering Community Team — Quarterly planning, 2014-Q1

2014-Q2

January to March 2014

Guillaume

• Provide ongoing communications support (blog post reviews, activity pages, etc.). Status:    Done
• Assemble and publish monthly reports. Status:    Done
• Complete Google Code-In: publicize communications/documentation tasks, and mentor students. Status:    Done
• Edit and publish the best discovery reports from Google Code-In on the tech blog. Status:    Done
• Ensure the weekly publication of Tech/News. Status:    Done
• Advertise Tech/News to increase readership. Status:    Done
• (With Andre) Meet Project management tools stakeholders, determine requirements, and document this research. Status:    Done
• (With Andre) Lead the community discussion about the shortlist of candidates for Project management tools, take the first implementation steps (possibly in Labs). Status:    Done
• (With Andre) Set up and facilitate the community RfC about Project management tools, and bring it to a decision. Status:    Started, continued in 2014-Q2

Andre

• Social:
  • (With Guillaume) Meet Project management tools stakeholders, determine requirements, and document this research. Status:    Done
  • (With Guillaume) Lead the community discussion about the shortlist of candidates for Project management tools, take the first implementation steps (possibly in Labs). Status:    In progress
  • (With Guillaume) Set up and facilitate the community RfC about Project management tools, and bring it to a decision. Status:    Not done - postponed to April 2014
  • (With Quim) Reboot Annoying little bugs; Bugzilla's easy keyword; exposing an easy "bug of the week": Based on Google Code-In experience, decrease manual curation work by providing links to common "getting started" questions. Status:    Done on 2014-03-07
  • Finalize Bugzilla etiquette draft. Status:    Done - 2014-02-05: Announcement
  • Better Bugzilla taxonomy: Discuss using classifications in Bugzilla and identify some initial non-controversial changes. - bugzilla:38990. Status:    In progress; first smaller cleanup steps about "Tools" and deprecated stuff are bugzilla:57738, bugzilla:54063, bugzilla:53986#c15, bugzilla:55351#c4, bugzilla:62386, bugzilla:62384; Proposal to use Bugzilla classifications on 2014-03-10
• Bugzilla setup / code:
  • Upgrade Bugzilla to 4.4 Status:    Done on 2014-02-13
  • Common queries on Bugzilla frontpage - bugzilla:22170. Status:    Done on 2014-02-13
  • Provide a way to mark an item as NEEDINFO in Bugzilla - bugzilla:36064. Status:    In progress: Created list of pros and cons of two implementations on 2014-03-10; next step is start broader discussion on wikitech-l@ and agree on which way to do
  • Install component watching extension to be able to receive bugmail for specific product/component for devs and triagers, plus no more manual adding of people to auto-CC by admins. Status:    Not done -- postponed to Q2/2014

Quim

• Google Code-in successfully completed, analyzed, and reported via blog post
• FOSS Outreach Program for Women - Round 7 successfully completed, analyzed, and reported via blog post
  • mediawiki.org homepage redesign proposal made by OPW intern, ready to be implemented
• Facebook Open Academy program started with at least 3 Wikimedia projects
• Google Summer of Code 2014 and FOSS OPW - Round 8 lined up with at least 10 projects
• All five Key Progress Indicators integrated to the Tech Community Metrics dashboard.
• Successful FOSDEM with Wikis devroom, "The Wikipedia Stack" main track session, and Wikimedia stand, analyzed, and reported via blog post
• Architecture process and queue of Requests for comment clean.
• Reboot Annoying little bugs.