Change Details

WARNING: this is a wild draft; everything may still change. Straw dog proposal: == Strategic goal: Boost developer contributions == (Wikimedia is a top Internet site and a major free software community. Our software stack offers possibilities for developers with different skills and levels of expertise. Our APIs allow developers to redistribute and transform our content, media, and data. However, overall our developer community is stalled, if not declining. Developers out there are not aware of the possibilities of our APIs. We are not the exciting developer destination we could be.) (This is the problem statement, we need a proper description of the goal.) === Project/Initiative 1: connect free software developers with the Community Wishlist === (The size, diversity, and complexity of our stack becomes a problem for developers willing to contribute. The Community Wishlist offers a sample still big enough to offer diversity of projects. Let's use it to channel as many developer contributions as we can.) === Project/Initiative 2: promote the Wikimedia APIs === (Taking as a basis the Labs Tools community, let's build a platform to promote the Wikimedia APIs, improving our documentation, showcasing products and features relying in our APIs, advocating at developer venues beyond the Wikimedia circles.) Due Date:   Friday, March 4, 2016 Solid draft probably 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: Coming soon, we want to hear feedback about the goals & projects first. Project/Initiative 2: Coming soon, we want to hear feedback about the goals & projects first. == 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 active projects using our APIs (Wikimedia Labs / External) Number of new projects using our APIs (Wikimedia Labs / External) Number of non-reverted contributions to Wikimedia projects made via Wikimedia Labs / External API requests Number of Wikimedia read queries made via Wikimedia labs / External requests 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 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. Straw dog proposal: == Strategic goal: Boost developer contributions == (Wikimedia is a top Internet site and a major free software community.== 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, Our software stack offers possibilities for developers with different skills and levels of expertise.onboarding, Our APIs allow developers to redistribute and transform our contentand supporting them, media,and increasing the levels of retention. and dataWe 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. HoweverThis comprises the hackathons we support, overall our developer community is stalledoutreach programs like Google Summer of Code and Outreachy, if not declining.and the onboarding support for new contributors, Developeras well as out there are not aware of the possibilities of our APIs.r support to volunteer collaboration in documentation, We are not the exciting developer destination we could be.) (This is the problem statement, we need a proper description of the goal.) === Project/Initiative 1: connect free software developers with the Community Wishlist === (The sizeproject 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, diversityoffering technical support, and complexity of our stack becomes a problem for developers willing to contributeadvocating in developer events and online venues beyond Wikimedia. The Community Wishlist offers a sample still big enough to offer diversity of projects.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: Coming soon, Let's use it to channel as many developer contributions as we can.) === Project/Initiative 2: promote the Wikimedia APIs === (Taking as a basis the Labs Tools community,we want to hear feedback about the goals & projects first. Project/Initiative 2: Coming soon, we want to hear feedback about the goals & projects first. == Key Performance Indicators (KPIs) or Metrics to measure milestones/success of projects/initiatives == Please ensure that these are both qualitative and quantitative. let's build a platform to promoteSome departments may have the same metrics as the following 7 Global Metrics identified for the Wikimedia APIs,FDC proposals. improving our documentation,Others may need to identify their own KPIs or metrics that are appropriate for their objectives. showcasing products and features relying in our APIsFor example a supporting function such as Office Admin, advocating at developer venues beyond the Wikimedia circles.) 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 active projects using our APIs (Wikimedia Labs / External) Number of new projects using our APIs (Wikimedia Labs / External) Number of non-reverted contributions to Wikimedia projects made via Wikimedia Labs / External API requests Number of Wikimedia read queries made via Wikimedia labs / External requests 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 Due Date:   Friday, March 4, 2016 Solid draft probably expected by Feb 26 See also {T124041}