Engineering Community Team/Planning/2013/Q4

Guillaume

 * Provide ongoing communications support (blog post reviews, activity pages, etc.).
 * Assemble and publish monthly reports.
 * Grow tech news and try to assemble a team of volunteers.
 * Experiment with "bug of the week" engagement on social media? (and other small experiments we discussed in SF: https://commons.wikimedia.org/wiki/File:Sustainability_tech_contributors.png ) put on backburner in favor of Google Code-In
 * Prepare Google Code-In, publicize communications/documentation tasks, and mentor students.

Andre

 * Make "guided bug report form" usable for Bugzilla newbies (inherit feedback from design team)
 * Show InlineHistory in Bugzilla - 47256.
 * Prepare and organize Wikimedia participation in Google Code-In with Quim.
 * Work on "etiquette" draft for behavior in Bugzilla, as discussed on teampractices@.
 * Evaluate Project management / issue tracking requirements and potential tools. - kicked off on teampractices@ and wiki on 2013-12-13
 * Prepare / start testing upgrade to Bugzilla 4.4 (and our custom patches) - 49597.
 * See Bug management/Task list for full list of plans and more information.

Quim

 * FOSS Outreach Program for Women - round 7 kicked off with at least 8 6 interns and new lessons learned.
 * First Wikimedia participation in Google Code-In headed to a successful completion.
 * About 6 volunteers contributing to automated tests regularly. (cancelled)
 * At least 3 Key Progress Indicators integrated to the Tech Communit Metrics dashboard.
 * MediaWiki Architecture Summit, Wikimedia participation at FOSDEM and pre-Wikimania London hackathons ready to roll.
 * "Bug of the Week" process working, including promotion. (after Google Code-in)
 * MediaWiki OSS Way of Working proposal discussed publicly with Wikimedia Foundation development teams and community liaisons. (maybe after Google Code-in)

Sumana

 * On sabbatical until Jan 2014.