Strategy/Wikimedia movement/2018-20/Working Groups/Product & Technology/Recommendations/7
- 1 Recommendations 7: Growing the Third-Party Ecosystem
- 1.1 Q 1 What is your Recommendation?
- 1.2 Q 2-1 What assumptions are you making about the future context that led you to make this Recommendation?
- 1.3 Q 4-1 Could this Recommendation have a negative impact/change?
- 1.4 Q 4-2 What could be done to mitigate this risk?
- 1.5 Q 5 How does this Recommendation relate to the current structural reality? Does it keep something, change something, stop something, or add something new?
- 1.6 Q 6-1 Does this Recommendation connect or depend on another of your Recommendations? If yes, how?
- 1.7 Q 6-2 Does this Recommendation connect or relate to your Scoping Questions? If yes, how?
- 1.8 Q 7 How is this Recommendation connected to other WGs?
Recommendations 7: Growing 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; this assumption should be tested. Successful open source projects tend to receive resources (money, staff and volunteer time, brand and marketing, 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. The Wikimedia Foundation (or another movement entity with sufficient capacity) should research what blocks the development of such an ecosystem in the MediaWiki case.
(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 (especially given the current trends around disintermediation that are negative to our revenue model). 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 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 the effort invested into unlocking this potential will 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 a 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 weighed whenever we make design decisions.
Q 5 How does this Recommendation relate to the current structural reality? Does it keep something, change something, stop something, or add something new?
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.