Change Details

WARNING: this is a wild draft; everything may still change. == Strategic goal: Volunteer developer contributions aligned with Wikimedia communities' requests == We will connect our volunteer developers with the needs of the Wikimedia communities expressed through the Community Wishlist survey. This focus will guide our efforts reaching out to new developers, onboarding, and supporting them, and increasing the levels of retention. We will promote the use of our APIs as a way to get started in Wikimedia development without having to go first through the complexities of MediaWiki development and deployment to Wikimedia servers. === Project / Initiative 1: Connect free software developers with the Community Wishlist === Focus our developer outreach activities in the resolution of projects listed in the Community Wishlist maintained by the Community Tech team. This comprises the hackathons we support, outreach programs like Google Summer of Code and Outreachy, and the onboarding support for new contributors, as well as our support to volunteer collaboration in documentation, project management, and code review processes. === Project / initiative 2: Promote the Wikimedia APIs === Build a platform to promote the Wikimedia APIs, improving our documentation, showcasing best practices, offering technical support, and advocating in developer events and online venues beyond Wikimedia. Our focus will be the Wikimedia Tool Labs community as well as third party developers willing to integrate Wikimedia content in their projects. == Milestones/Results/Impact == Please provide milestones/results/impact and describe how they will impact/contribute to the Wikimedia movement and projects and/or the Wikimedia Foundation. Project/Initiative 1: * Milestone: Triage of the Community Wishlist tasks, selecting those apt for our developer outreach activities based on votes and strategic fit. * Milestone: Recruitment of mentors for the top 10 tasks selected. * Milestone: Each selected task is promoted to the most suitable outreach activities: hackathons, GSoC, Outreachy, collaboration with universities. * Impact: new volunteer developers find useful tasks and mentors easily, increase their chances of deploying useful features. * Impact: our hackathons and outreach programs increase their productivity just by channeling their work toward popular community requests. * Result: 10 technical community requests with strong demand to be completed by volunteer developers. Project/Initiative 2: * Milestone: launch of the Wikimedia Web APIs Hub. (#web-apis-hub) * Milestone: creation of 10 video tutorials for new developers, supported by documentation and examples. * Milestone: basic and advanced workshops about the use of Wikimedia APIs in all Wikimedia developer events and 4 external developer conferences. * Impact: better technical support to the Wikimedia Tool Labs community, supplementing the Community Tech and Labs teams. * Impact: better technical support to partners identified by the Partnerships and Wikipedia Zero team. * Impact: better awareness of the Wikimedia APIs in developer circles, out of the Wikimedia movement. * Result: A Wikimedia Web APIs Hub becomes an entry point for new developers creating tools to consume, distribute, and improve Wikimedia content. * Result: Wikimedia tools developers with technical questions receive support and improvements in documentation reliably. * Result: A catalog of Wikimedia tools helps identifying useful tools and their developers. (T115650) == Key Performance Indicators (KPIs) or Metrics to measure milestones/success of projects/initiatives == Please ensure that these are both qualitative and quantitative. Some departments may have the same metrics as the following 7 Global Metrics identified for the FDC proposals. Others may need to identify their own KPIs or metrics that are appropriate for their objectives. For example a supporting function such as Office Admin, KPIs or metrics may be in the form of Service Level Agreements. === Project/Initiative 1 Number of volunteer code contributors to Community Wishlist projects Number of new Wikimedia volunteers contributing to Community Wishlist projects Total number of code contributors to Community Wishlist projects Number of Community Wishlist projects completed Percentage of completion of Top 10 Community Wishlist projects (selected by Technical Collaboration) Community health survey for Wikimedia technical spaces === Project/Initiative 2 === Number of articles about use of Wikimedia APIs in Wikimedia / non-Wikimedia media Number of presentations about Wikimedia APIs or development in Wikimedia / non-Wikimedia events == Staffing requests == * Technical Writer * Developer Advocate == Budget requests == (For now the numbers are provided only in the WMF internal draft) * Events (Logistics and volunteer travel sponsorship for Wikimedia Developer Summit and Wikimedia Hackathon) * Outreachy internships * Additional travel budget for the developer advocate * Merchandising * Maintenance of tech community metrics (http://korma.wmflabs.org/) Due Date:   Friday, March 4, 2016 Solid draft expected by Feb 26 See also {T124041}

WARNING: this is a wild draft; everything may still change. == Strategic goal: Volunteer developer contributions aligned with Wikimedia communities' requests == We will connect our volunteer developers with the needs of the Wikimedia communities expressed through the Community Wishlist survey. This focus will guide our efforts reaching out to new developers, onboarding, and supporting them, and increasing the levels of retention. We will promote the use of our APIs as a way to get started in Wikimedia development without having to go first through the complexities of MediaWiki development and deployment to Wikimedia servers. === Project / Initiative 1: Connect free software developers with the Community Wishlist === Focus our developer outreach activities in the resolution of projects listed in the Community Wishlist maintained by the Community Tech team. This comprises the hackathons we support, outreach programs like Google Summer of Code and Outreachy, and the onboarding support for new contributors, as well as our support to volunteer collaboration in documentation, project management, and code review processes. == Milestones/Results/Impact == Please provide milestones/results/impact and describe how they will impact/contribute to the Wikimedia movement and projects and/or the Wikimedia Foundation. Project/Initiative 1: * Milestone: Triage of the Community Wishlist tasks, selecting those apt for our developer outreach activities based on votes and strategic fit. * Milestone: Recruitment of mentors for the top 10 tasks selected. * Milestone: Each selected task is promoted to the most suitable outreach activities: hackathons, GSoC, Outreachy, collaboration with universities. * Impact: new volunteer developers find useful tasks and mentors easily, increase their chances of deploying useful features. * Impact: our hackathons and outreach programs increase their productivity just by channeling their work toward popular community requests. * Result: 10 technical community requests with strong demand to be completed by volunteer developers. == Key Performance Indicators (KPIs) or Metrics to measure milestones/success of projects/initiatives == Please ensure that these are both qualitative and quantitative. Some departments may have the same metrics as the following 7 Global Metrics identified for the FDC proposals. Others may need to identify their own KPIs or metrics that are appropriate for their objectives. For example a supporting function such as Office Admin, KPIs or metrics may be in the form of Service Level Agreements. === Project/Initiative 1 Number of volunteer code contributors to Community Wishlist projects Number of Community Wishlist projects completed Community health survey for Wikimedia technical spaces == Budget requests == (For now the numbers are provided only in the WMF internal draft) * Events (Logistics and volunteer travel sponsorship for Wikimedia Developer Summit and Wikimedia Hackathon) * Outreachy internships * Merchandising * Maintenance of tech community metrics (http://korma.wmflabs.org/) Due Date:   Friday, March 4, 2016 Solid draft expected by Feb 26 See also {T124041}

WARNING: this is a wild draft; everything may still change. == Strategic goal: Volunteer developer contributions aligned with Wikimedia communities' requests == We will connect our volunteer developers with the needs of the Wikimedia communities expressed through the Community Wishlist survey. This focus will guide our efforts reaching out to new developers, onboarding, and supporting them, and increasing the levels of retention. We will promote the use of our APIs as a way to get started in Wikimedia development without having to go first through the complexities of MediaWiki development and deployment to Wikimedia servers. === Project / Initiative 1: Connect free software developers with the Community Wishlist === Focus our developer outreach activities in the resolution of projects listed in the Community Wishlist maintained by the Community Tech team. This comprises the hackathons we support, outreach programs like Google Summer of Code and Outreachy, and the onboarding support for new contributors, as well as our support to volunteer collaboration in documentation, project management, and code review processes. === Project / initiative 2: Promote the Wikimedia APIs === Build a platform to promote the Wikimedia APIs, improving our documentation, showcasing best practices, offering technical support, and advocating in developer events and online venues beyond Wikimedia. Our focus will be the Wikimedia Tool Labs community as well as third party developers willing to integrate Wikimedia content in their projects. == Milestones/Results/Impact == Please provide milestones/results/impact and describe how they will impact/contribute to the Wikimedia movement and projects and/or the Wikimedia Foundation. Project/Initiative 1: * Milestone: Triage of the Community Wishlist tasks, selecting those apt for our developer outreach activities based on votes and strategic fit. * Milestone: Recruitment of mentors for the top 10 tasks selected. * Milestone: Each selected task is promoted to the most suitable outreach activities: hackathons, GSoC, Outreachy, collaboration with universities. * Impact: new volunteer developers find useful tasks and mentors easily, increase their chances of deploying useful features. * Impact: our hackathons and outreach programs increase their productivity just by channeling their work toward popular community requests. * Result: 10 technical community requests with strong demand to be completed by volunteer developers. Project/Initiative 2: * Milestone: launch of the Wikimedia Web APIs Hub. (#web-apis-hub) * Milestone: creation of 10 video tutorials for new developers, supported by documentation and examples. * Milestone: basic and advanced workshops about the use of Wikimedia APIs in all Wikimedia developer events and 4 external developer conferences. * Impact: better technical support to the Wikimedia Tool Labs community, supplementing the Community Tech and Labs teams. * Impact: better technical support to partners identified by the Partnerships and Wikipedia Zero team. * Impact: better awareness of the Wikimedia APIs in developer circles, out of the Wikimedia movement. * Result: A Wikimedia Web APIs Hub becomes an entry point for new developers creating tools to consume, distribute, and improve Wikimedia content. * Result: Wikimedia tools developers with technical questions receive support and improvements in documentation reliably. * Result: A catalog of Wikimedia tools helps identifying useful tools and their developers. (T115650) == Key Performance Indicators (KPIs) or Metrics to measure milestones/success of projects/initiatives == Please ensure that these are both qualitative and quantitative. Some departments may have the same metrics as the following 7 Global Metrics identified for the FDC proposals. Others may need to identify their own KPIs or metrics that are appropriate for their objectives. For example a supporting function such as Office Admin, KPIs or metrics may be in the form of Service Level Agreements. === Project/Initiative 1 Number of volunteer code contributors to Community Wishlist projects Number of new Wikimedia volunteers contributing to Community Wishlist projects Total number of code contributors to Community Wishlist projects Number of Community Wishlist projects completed Percentage of completion of Top 10 Community Wishlist projects (selected by Technical Collaboration) Community health survey for Wikimedia technical spaces === Project/Initiative 2 === Number of articles about use of Wikimedia APIs in Wikimedia / non-Wikimedia media Number of presentations about Wikimedia APIs or development in Wikimedia / non-Wikimedia events == Staffing requests == * Technical Writer * Developer Advocate == Budget requests == (For now the numbers are provided only in the WMF internal draft) * Events (Logistics and volunteer travel sponsorship for Wikimedia Developer Summit and Wikimedia Hackathon) * Outreachy internships * Additional travel budget for the developer advocate * Merchandising * Maintenance of tech community metrics (http://korma.wmflabs.org/) Due Date:   Friday, March 4, 2016 Solid draft expected by Feb 26 See also {T124041}