Developer Relations

Purpose

 * Attract and support volunteer technologists so that they can become an even more powerful force in driving improvement on the website
 * Help nurture volunteer-developed extensions and widgets
 * Provide communications support for all groups in the engineering department
 * Develop clear documentation for MediaWiki so that new staff, volunteer developers and external users have a smooth ramp-up process to becoming MediaWiki developers

Events
Where to meet us face to face. See also Calendar.
 * WikiCon 2013 in Karlsruhe (DE), November 22-24, 2013

Current activities
See also Engineering Community team meetings.


 * }

Planning
We connect our short term plans with the 2013-14 Engineering Community goals at the ECT Showcase. We might fine tune plans in our weekly meetings.


 * /November 2013 Quarterly Review

Guillaume

 * Publish the engineering report for November
 * Follow up on support requests (e.g. blog post reviews)
 * Get the weekly tech newsletter assembled, published, translated and delivered (ideally with help)
 * Publish behind-the-scenes article about how the tech newsletter is assembled and delivered
 * Prepare Google Code-In tasks for the Community change team and serve as a proxy
 * Mentor Google Code-In students
 * With Andre: Start planning evaluation of Project management / issue tracking requirements and potential tools.

Quim

 * Keep pushing Google Code-In
 * Coordinate FOSS Outreach Program for Women - Round 7
 * Co-mentor OPW project mediawiki.org homepage redesign
 * Start Facebook Open Academy Program
 * Co-organize Wikis devroom at FOSDEM (schedule defined)
 * Organize Wikimedia Multimedia meetup in San Francisco
 * Complete Community metrics: Who contributes code and Gerrit review queue key progress indicators. (Bitergia) (moved from November)
 * Select one technical writer temporary contractor
 * Convert to GCI tasks:
 * Wrap up Google Summer of Code 2013 (moved from October)
 * Self-help guide to organize events. See Events kit and how WordPress does it.
 * Plan a Guided Tour at mediawiki.org.
 * Improve the confirmation email sent to new registered users and sync Template:Welcome.
 * What to do with the social media stats being collected at Talk:Community metrics?

Andre

 * Google Code-In: Run and organize contest with Quim.
 * Agree and finalize on "etiquette" for behavior in Bugzilla, as discussed on teampractices@. - discussion on teampractices mailing list and talk page
 * Start planning evaluation of Project management / issue tracking requirements and potential tools.
 * Test Bugzilla 4.4 with our custom patches on Labs (or zirconium in eqiad if production is still on kaulen in Tampa)., will need help from ops
 * Deploy Bugzilla 4.4 to production., will need help from ops

Guillaume

 * Publish the engineering report for October
 * Follow up on support requests (e.g. blog post reviews)
 * Get the weekly tech newsletter assembled, published, translated and delivered (ideally with help)
 * Prepare for Google Code-In: prepare tasks and add them to melange, reach out to volunteers and other Wikimedia teams for collaboration
 * Mentor Google Code-In students

Quim

 * Start Google Code-In
 * Start FOSS Outreach Program for Women - Round 7
 * Engineering Community team quarterly review
 * Proposal for a Wikimedia stand at FOSDEM submitted by November 20. (Dimitar Parvanov)
 * Complete Community metrics: Who contributes code and Gerrit review queue key progress indicators. (Bitergia)
 * Send Request for Proposals for a technical writer temporary contractor
 * Help organizing Architecture meetings
 * Convert to GCI tasks:
 * Google Code-in
 * Review and polish browser test automation docs for newcomers. (moved from October) (QA team is working on this)
 * Screencast: how to file your first bug report. (moved from October) (Part 1)
 * Wrap up Google Summer of Code 2013 (moved from October)
 * Update Possible Projects (moved from October)

Andre

 * Google Code-In: Define generic information (template) for all task descriptions; clean up & import tasks from wiki into Google Melange. (except for tasks missing a mentor)
 * Finish cleaning up and syncing custom CSS in Wikimedia Bugzilla. - done (except for two CSS files) (54823)
 * Write an "etiquette" draft for behavior in Bugzilla, as discussed on teampractices@. - first draft available
 * Start planning evaluation of Project management / issue tracking requirements and potential tools.
 * Start porting our custom Bugzilla patches by porting our 4.2 custom patches to deploy on a vanilla Bugzilla 4.4. (49597)

October 2013
Guillaume
 * Publish the engineering report for September ✅
 * Follow up on outstanding requests (e.g. blog post reviews) ✅
 * Finish to assemble and publish the tech newsletter ✅
 * Rest! ✅
 * Catch up ✅
 * Assemble and publish tech newsletter ✅
 * Start drafting the engineering report for October ✅
 * Plan the activities for the next month ✅

Quim
 * Events: MediaWiki 1.22 Release Plan tech talk ✅ and Flow UX Workshop meetup ✅
 * Participating in Google Code-in ✅
 * Bootstrap experiment of ECT public meetings. ✅
 * Wrap up Google Summer of Code 2013 and leave Possible Projects ready for FOSS Outreach Program for Women - round 7
 * Community metrics: Who contributes code key progress indicator
 * Bug of the Week ready to start.
 * Start drafting MediaWiki OSS Way of Working (too busy, maybe after GCI)
 * Promote OAuth to app developers? (waiting for the team to answer back)

Quarterly goals
October to December 2013.

Guillaume

 * Provide ongoing communications support (blog post reviews, activity pages, etc.)
 * Assemble and publish monthly reports
 * Revive 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.
 * Prepare / start testing upgrade to Bugzilla 4.4 (and our custom patches) - 49597.
 * Think about better Bugzilla taxonomy (products/components structure) and identify some initial non-controversial tasks. - 38990., first small steps: 57738, 54063
 * 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 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.