Wikimedia Technology/Annual Plans/FY2019/TEC10: Build Technical Community

Teams contributing to the program
Wikimedia Cloud Services, CTO Team, MediaWiki Platform, Research

Annual Plan priorities
Primary Goal: 3. Knowledge as a Service - evolve our systems and structures

Program Goal
Wikimedia's software products and platforms have a diverse collection of technical communities including code contributors, documentation contributors, bug reporters, API consumers, volunteers who build innovative solutions to on-wiki workflow issues, researchers who examine the data generated by the Wikimedia projects, value-added vendors who provide services and support based on Wikimedia free and open-source software products, and true 'third parties' who install and use FLOSS software produced by the Wikimedia movement on their own computers for various reasons. These audiences contribute directly and indirectly to the broadest goal of the movement: to collect and disseminate knowledge. However, they have not always been well recognized for these contributions and supported in their work. The technical community support project will attempt to begin to address this shortcoming by providing better documentation, facilitating community building, and establishing better pathways for communication between these communities and the Foundation.

We will expand and strengthen our technical communities, focusing on understanding their needs and measuring the progress and outcome of our efforts. In particular, we will focus on three traditionally underserved communities: tool and bot developers; API and data consumers; and third-party users of our software.
 * Outcome 1
 * Becoming a technical contributor to the Wikimedia movement by creating and maintaining 'tools' and other innovative solutions is easier than it has been historically because documentation is easier to find, more comprehensive, and descriptive of start to finish steps needed to solve common problems. Cloud Services product users feel comfortable sharing their knowledge with others as part of a community with a culture of sharing via documentation and mutual support.
 * Output
 * Support the collaborative work of the 'Tech writing (Re)working group'.
 * Output
 * Improve documentation for Toolforge & Cloud VPS based on gaps identified by the 'Tech writing (Re)working group' and via the Toolforge Annual Survey.
 * Output
 * Attract and foster a robust community of skilled and aspiring technical writing contributors. Help them build skills, while addressing gaps in Wikimedia technical documentation


 * Outcome 2
 * Contributors and consumers are able to locate and use software resources that extend their capabilities and insights beyond those provided by the core wiki experience.
 * Output
 * Ship a read-write tools catalog product
 * Output
 * Promote adoption of the catalog by key audiences; namely, contributors and movement organizers
 * Output
 * Develop a community of tool developers and tool users interested in maintaining, expanding, and curating the catalog to ensure that it remains a viable resource


 * Outcome 3
 * Support use of Wikimedia services by Foundation staff, Wikimedia community members, and third-party consumers by providing evangelism and technical guidance resources.
 * Output
 * Promote Wikimedia Cloud Services products at relevant conferences, hackathons, and within the Wikimedia communities
 * Output
 * Provide first line technical support resources to triage and respond to Cloud Services product support requests


 * Outcome 4
 * Organize the Wikimedia Developer Summit as a four day meeting of ~70 senior technical contributors focusing on one strategic theme that will be announced before the call for participation and scholarship requests start.
 * Output
 * Developer Summit web page will be published four months before the event that will include date and location (as well as nearest airport), strategic theme, call for participation, call for scholarship requests, and a calendar schedule with deadlines. A good representation of non-WMF stakeholders related to the main theme will be invited to participate in person at the event (preferred) or online.
 * Output
 * A process which allows the prospective participants to submit statements and proposals regarding the main strategic theme, as well as allowing the Program Committee to review everything and notify the prospective participants the Committee's decisions. Discussions will start before the event with the involvement of all relevant stakeholders, in order to identify the points that need to be addressed at the event.
 * Output
 * Activities during the Summit will be well documented, especially the outcomes of the sessions and follow-up actions, which will be compiled in a systematic way for further evaluation and followup.


 * Outcome 5
 * There is an established, bidirectional channel of communication between Foundation staff and value-added vendors who provide services and support based on Wikimedia software and true 'third parties' who install and use software produced by the Wikimedia movement on their own computers
 * Output
 * Attend, present at, and assist in the organization of third-party hosted conferences and meetings
 * Output
 * Maintain, promote, and interact on Q&A (e.g. Discourse) and chat (e.g. Riot) servers directed at the third-party community


 * Outcome 6
 * Third-party MediaWiki developers feel confident creating and maintaining MediaWiki extensions, and third-party MediaWiki users feel confident using MediaWiki extensions
 * Output
 * Maintain an up-to-date list of MediaWiki extensions including information documenting the level of support of those that are supported
 * Output
 * Maintain and evolve the extension management system in MediaWiki to increase dissemination of extension information


 * Outcome 7
 * Collaboration with the community of researchers in industry and academia is further scaled and supported, so that more findings and datasets are published and disseminated under an open license, to help us answer strategically important questions.
 * Output
 * Organize and host the annual Wiki Research Workshop to help align the interests of the academic community to issues of strategic importance for the movement. Continue to successfully run a research workshop at a major conference, as we have for the past 4 years.
 * Output
 * Maintain the current capacity for formal research collaborations with industry and academia to reduce the overall cost for the organization to carry out research projects.

Outcome 1

 * Target
 * Users are able to more easily find documentation they need.


 * Measurement method
 * Agree/Disagree answer ratio for "Documentation is easy to find" annual developer survey question improves compared to prior surveys.


 * Target
 * Size of active technical documentation editing community increases.


 * Measurement method
 * 3 month count of editors making an edit in the Help namespace on Wikitech increases by 10% or more in FY2018/19 Q3 over FY2017/18 Q3.

Outcome 2

 * Target
 * Tools catalog product is deployed for general use.


 * Measurement method
 * Product is available at a documented public URL by the end of FY2018/19 Q3.
 * Tools catalog product is adopted by publishing community.
 * Month over month count of tools documented in the catalog grows by 5% or more per month for the first 3 months after official launch.

Outcome 3

 * Target
 * Cloud Services products are promoted at community events.


 * Measurement method
 * Presentation, Roundtable, or Poster session presented at Wikimania
 * Presentation or Roundtable session presented at Hackathon

Dependencies

 * Community Engagement: Community Liaison support
 * Community Engagement: Collaboration with Developer Relations team on API documentation/tutorials/outreach
 * Community Engagement: Event planning and logistics support from Developer Relations team
 * Research: External collaborators, conference chairs (workshop); Legal, Ops, Analytics (formal collaborations)