Developer Relations/Goals
Appearance
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. See m:Technical Collaboration/Goals for updated information. |
For the process for defining these goals, see Developer Relations/Planning#Quarterly goals.
January - March 2016
[edit]These goals must be synced with Wikimedia Engineering/2015-16 Q3 Goals. Related task: Phab:T119388.
Team goals
[edit]Objective | Key result | Dependency | ETA | Status |
---|---|---|---|---|
Connect the priorities of the Community Wishlist and other tech priorities with the Wikimedia Hackathon 2016 |
|
Community Tech, Wikimedia Hackathon 2016 organizers | March/April 2016 | Proposed; Results |
Agree on and implement actions to prioritize code review of patches submitted by volunteers | Discussion and consensus among stakeholders which process changes to effectively implement and how | WMF Engineering and product teams; |
February/March 2016 | Not done: Actions identified and agreed on, but not implemented yet |
Partner with WMIL on a successful Wikimedia Hackathon 2016 | International hackathon in Jerusalem March 30 - April 3, 2016. Supporting newcomers, demo-able projects and showcase, main themes and focus areas, successful social events, productive environment. | WMIL, WMF engineering teams | March/April, 2016 | Proposed |
Help Hackathon participants with project pre-planning | Try to connect paid and volunteer developers with projects and each other in advance of hackathons. | WMF Engineering teams, Volunteer Devs | March/April, 2016 | Proposed |
Individual goals
[edit]Quim
[edit]Objective | Key result | Dependency | ETA | Status |
---|---|---|---|---|
Connect the priorities of the Community Wishlist and other tech priorities with the Wikimedia Hackathon 2016 | See Team goals | |||
FY 2016-17 Annual Plan for Developer Relations (Phabricator task coming soon) |
|
|||
Align Community Liaison and Developer Relations project management practices |
|
March | Ongoing | |
Deploy Newsletter extension in Wikimedia |
|
Newsletter-extension project volunteers | March | Ongoing (Deployed on beta cluster but not in production yet) |
Rachel
[edit]Objective | Key result | Dependency | ETA | Status |
---|---|---|---|---|
Lessons Learned from WikiDev 2016 | How did it go? What could have gone better? Ideas for next year. | WikiDev participants, creation of feedback survey. | Feb - Mar 2016 | Proposed |
Redefine Wikimedia Hackathons | Define key roles that need to be filled at every hackathon, size limitations so that we can hold more hackahtons? New budget allocations. | WMF budget process, DR team, Hackathon organizers | Fed - Mar 2016 | Proposed |
Selection process for Wikimedia Hackathon 2017 | Work with hackathon organizers and DR to come up with a better and more transparent selection process for Wikimedia Hackathons. Who decides where and how? | Hackathon organizers | Feb - Mar 2016 | Proposed |
Partner with WMIL on a successful Wikimedia Hackathon 2016 | International hackathon in Jerusalem March 30 - April 3, 2016. Supporting newcomers, demo-able projects and showcase, main themes and focus areas, successful social events, productive environment. | WMIL, WMF engineering teams | March/April, 2016 | Proposed |
Help Hackathon participants with project pre-planning | Try to connect paid and volunteer developers with projects and each other in advance of hackathons. | WMF Engineering teams, Volunteer Devs | March/April, 2016 | Proposed |
Andre
[edit]Objective | Key result | Dependency | ETA | Status |
---|---|---|---|---|
Agree on and implement actions to prioritize code review of patches submitted by volunteers | Discussion and consensus among stakeholders which process changes to effectively implement and how | WMF Engineering and product teams; |
Feb-Mar 2016 | Not done: Actions identified and agreed on, but not implemented yet |
All WMF developer teams join. 50% of unreviewed patches contributed by volunteers have at least one review. Improved awareness and knowledge about Differential's workflows across the developer community. | All WMF Engineering and Technology teams (through their managers); mw:Wikimedia Release Engineering Team (for Differential) | Canceled Not done |