Realize the Potential of the Third-Party Ecosystem

Q 1 What is your Recommendation?

We think there is a large third-party user base potential that is not currently realized. Successful open source projects tend to receive resources (money, staff and volunteer time, etc.) from a diverse set of entities, which have different goals but work together to improve the tool they all need. MediaWiki on the other hand is a monoculture, almost entirely dependent on Wikimedia, even though there seems to be a much wider demand for the functionality it provides. If there is, in fact, the potential for such an ecosystem, the movement entity stewarding development should identify and resolve chokepoints which prevent it from being realized.

(MediaWiki is used in the wide sense here, including all technologies built around it, such as Wikibase or Parsoid.)

Q 2-1 What assumptions are you making about the future context that led you to make this Recommendation?

Becoming the essential infrastructure of free knowledge is a vast undertaking and will require all the resources the movement can muster, and more. Improving our platform ties down a significant fraction of our budget, and even so the rate of progress is much slower than we’d like. If there is an opportunity to resource platform improvements in from external sources, we should take it.

Q 3-1 What will change because of the Recommendation?

Directly, an analysis of user needs and market opportunities of the MediaWiki ecosystem will be performed to identify investments that make that ecosystem more self-sustaining, and those investments will be made. (Alternatively, the analysis will demonstrate that no such investments are viable, putting an end to a long and at times acrimonious debate). Indirectly, the MediaWiki ecosystem will be more thriving and more self-sustaining, freeing up movement resources to be put towards work more specific to Wikimedia projects.

Q 3-2 Who specifically will be influenced by this recommendation?

Immediately, the recommendation would instruct some group (presumably the WMF with the support of external expertise) to perform the research described in the previous sections, and follow up on its recommendations. Ultimately, if that has the expected results, third-party MediaWiki users will be influenced in that using MediaWiki will become easier for them and their numbers will grow, and the WMF and other movement organizations will see a reduced need of investment into platform and product features where the use cases are shared with third parties, due to increased involvement from them.

Q 4-1 Could this Recommendation have a negative impact/change?

The assumption that there is a wide potential for MediaWiki and related technologies might be wrong, in which case any effort invested into unlocking this potential would be wasted.

If Wikimedia and other entities with a significant stake in the platform end up with diverging technical visions they cannot reconcile, that might result in conflicts (such as a project fork) and bad publicity.

Compromises made to keep the Wikimedia tech platform appealing to the widest range of interested parties might hurt its efficiency for the Wikimedia use cases.

Q 4-2 What could be done to mitigate this risk?

The theory that the MediaWiki ecosystem has significant third-party potential should be confirmed by research or small-scale experiments with early involvement of third parties, before any major investment is made.

The risk of fallout between major stakeholders is expected to be both unlikely and low-impact, as long as the trademark and core development infrastructure is owned by Wikimedia.

The risk of making the architecture too generic or too flexible will have to be weighed whenever we make design decisions, and also as a cost during the business and market potential analysis.

Q 5 How does this Recommendation relate to the current structural reality?

If it’s successful, it would add a new region to the current stakeholder structure, although one that’s not part of the Wikimedia movement in the traditional sense.

Q 6-1 Does this Recommendation connect or depend on another of your Recommendations? If yes, how?

Not directly, although it complements Decentralization in some ways: it’s a different way of distributing the development burden in a more resilient and sustainable manner, and both will require similar improvements in communication and governance.

Q 6-2 Does this Recommendation connect or relate to your Scoping Questions? If yes, how?

It is a (provisional) answer to the scoping question “What is the relationship between funding the Wikimedia Movement and funding the Mediawiki ecosystem?” In a way it also answers “Should software/tech be considered as a possible revenue-generating avenue?” although instead of directly generating revenue for the Wikimedia movement, the third-party ecosystem is seen as saving resources by sharing some of the burden of evolving the platform.

Q 7 How is this Recommendation connected to other WGs?

It is relevant to Revenue Streams - even though the third-party ecosystem is not a source of revenue to the movement (to some extent it could be, e.g. by exploiting the MediaWiki trademark, but that is not expected to be significant), it would free up resources currently tied down by the needs of the platform to be used elsewhere, so in many ways its analogous to a new resource stream.

It would also set us up for collaboration with other actors sharing a technology platform with us, which in the scope of Partnerships. It is especially close to their “Technical Partnership For Developments under a shared vision and resource collaboration” recommendation, except that recommendation takes a traditional and narrow view on what counts as a partnership.

Q 8 Do you have anything to add that was not covered with previous questions, yet essential for understanding the recommendation?

While a proper business analysis was beyond the capabilities of the working group, here are some quick facts on which we based our assessment of the third-party ecosystem having high potential:

MediaWiki is one of the two market leaders in wiki software; the other one, Confluence, which has a comparable user base (tens of thousands) and feature set, has over $100M annual revenue.
Wordpress, which has 500x the downloads and 1000x the install base of MediaWiki, has been estimated to have an $1B plugin market.

v t e Movement Strategy Working Group recommendations (September 2019) Now merged into the final 10 recommendations
Advocacy	1. Transparency 2. Diversity 3. Global conversation 4. Knowledge management 5. Advocacy Hub 6. Common positioning 7. Partnerships 8. Empowerment of advocates 9. Self-Determination 10. Protection of Advocates
Capacity Building	1. Building Capacity for Capacity Building 2. Matching human assets and online knowledge resources with capacity building needs 3. Capacity Building Should Occur in Context 4. Provide Capacity Building for Organizational Development 5. Resources for Capacity Building 6. Evaluating Capacity Building 7. Online Training 8. Mentoring and leadership development 9. Recognizing Individuals 10. Independently governed Capacity Building ‘Unit’
Community Health	1. A joint set of rules we all agree to live by (a.k.a. Code of Conduct) 2. Redefining power structures to better serve the communities 3. Building the leadership of the future 4. Structure for handling conflicts- before, during and after 5. Investing in building an inclusive global community 6. Newcomers are a key indicator to the success of the movement 7. “Democratizing” participation (making Wikipedia/Wikimedia everyone’s responsibility) and reducing barriers for participation 8. Privacy and security for everyone 9. Opening the circle: All terrain readiness 10. Network to continually support community health 11. Aligning resource allocation with community health goals 12. Investing in equity-centered technologies
Diversity	1. Introducing people-centered principles within the Wikimedia movement 2. Reaching a self-aware and dynamic structure aimed at community diversity and health 3. Redesigning the platforms for more diversity of people and content experiences 4. Planned community diversification 5. Reflective policies for participation and governance 6. Establishing partnerships in order to represent and protect worlds’ cultural diversity 7. Decentralized administrative structure for resource allocation 8. Bridging different local contexts and Wikimedia projects' notability and verifiability policies
Partnerships	1. Provide the knowledge needed for understanding and solving global issues 2. Wikimedia as steward of the Free Knowledge Ecosystem 3. Shared ecosystem of services and tools for content partnerships 4. Data partnerships approach to fulfill the vision of knowledge as a service for our partners 5. Focus on knowledge equity when determining priorities for Partnerships 6. Partnerships as part of a Distributed Vision 7. Partnerships as a shared and equitable resource and activity 8. Prioritise documentation 9. Invest in sharing knowledge about partnerships across the movement 10. Support the skills development of people working on partnerships 11. Invest in the leadership potential of community members 12. Establish recognition principles for new partners for attribution and content donation 13. Additional research for areas where we have identified issues but haven’t made recommendations
Product & Technology	1. Evaluate and Decentralize Technology Components 2. Support Community Decision-making 3. Open Product Proposal Process 4. Deployment Council 5. Disseminate Product Knowledge 6A. Improve Technical Contributor Engagement 6B. Modernize Technical Contributor Tooling 7. Realize the Potential of the Third-Party Ecosystem 8. Movement Technology Ethics Review Process 9. Monitoring Product Trust and Availability 10. Developing an Evolving Technology Vision and Strategy
Resource Allocation	A. Set Common Framework of Principles for Resource Allocation B. Design participatory decision making for Resource Allocation C. Recognize privileges / Design for equity D. Distribute existing structures E. Build Thematic hubs – to provide services to the free knowledge movement long term F. Ensure flexible approach to resource allocation in a complex, fast moving and changeable space G. Allocate resources for capacity and sustainability H. Allocate resources to new types of partners/organisations (essential infrastructure of the free knowledge ecosystem) I. Include knowledge consumers
Revenue Streams	1. Turn the Wikimedia API into a revenue source 2. Provide Paid Wiki-related Services 3. Monetize merchandise 4. Expand global fundraising 5. Develop non-fundraising revenue streams for affiliates 6. Set a goal of financial sustainability for all movement actors 7. Diversification of revenue channels
Roles & Responsibilities	0. Scenario 1. All of this exists to support our primary purpose: free knowledge and its distribution (Original) 2&3. Decentralisation and self-management 4&5. Establish a Movement Charter 6. Wikimedia movement organisations will be governed by inclusive, diverse, and accountable boards 7. Capacity building