Project "MWStake Certified Extensions"

Administrators can rely on the extension store to know whether a certain extension is safe and performant to be run in conjunction with a specific MediaWiki setup. Developers can submit their extensions to the extension store in order to certify them as safe and performant to be run in conjunction with specific MediaWiki setups.

In this context What links here? Main Page Project Project "Tests and Documentation Maker" Event "MWStake Meeting 04/05/2019"

Define "safe and performant to be run in conjunction with specific MediaWiki setups"

An extension MyExtension which is featured in the MWStake Extension Store is certified e.g. as "MWStake ES 1.37.1 CSP", which means:

1. The MWStake ES Certification Committee accepts MyExtension's unit tests as being sufficient.
   • All of MyExtension's unit tests are passing.
2. The MWStake ES Certification Committee accepts MyExtension's integration/API tests as being sufficient.
   • MyExtension's integration tests are substantiating MyExtension's interoperability with MW Core 1.37.1 and all of the extensions included in the CSP extension package.
   • All of MyExtension's integration tests are passing.

Implementation

1. Constitute the MWStake ES Certification Committee.
2. Decide on the MWStake ES Certification Committee members' remuneration of $X.-/hour.
3. Decide on the first extension to certify.
   • Action:7
   • Voted that the Duplicator will be the first extension
   • Or from open content service platform (wikibase solutions) or from document management package (NASA)
4. Decide which SLA to set up (e.g. "the stewardship of the RDFIO Extension guarantees that a) 30 days after release of a new MW Core Version, the RDFIO Extension passes all unit and integration tests for an installation on the new Core and that b) 30 days after releasing a new version of one of the other 9 Top 10 Extensions, the RDFIO Extensions passes all unit and integration tests in joint operation")
5. Certify the first extension and publish it safely* in the MWStake Extension Store.
6. Secure longterm stewardship for the extension.
   • Ensure unit and integration tests sufficiency and passing with regard to evolving MW core and extension packages.

Idea: Kickoff

1. Decide which top 10 extensions (which are not part of the MW core) are of strategic importance for us as professional and commercial MW 3rd party users for customer projects
2. Decide which community members are appointed as stewards for which of these 10 extensions
3. Decide which SLA to set up (e.g. "the stewardship of the RDFIO Extension guarantees that a) 30 days after release of a new MW Core Version, the RDFIO Extension passes all unit and integration tests for an installation on the new Core and that b) 30 days after releasing a new version of one of the other 9 Top 10 Extensions, the RDFIO Extensions passes all unit and integration tests in joint operation")
4. Decide which annual contribution is due for a company (e.g. 20 companies at $200/y = $4000 / 10 stewards = $400 per steward per year for "monitoring an extension")
5. Decide whether the public should be excluded from this benefit or whether we should rely on FairPlay.

CONSIDER: Spin off project "Self-containered Extension Stack"

Purpose: testing, showcasing and documenting

Project "Tests and Documentation Maker" provides Cypress tests.

• Guided tour
• Auto tutorials
• Testing
• Container-based examples
  • e.g. https://spacy.io/usage/rule-based-matching
  • e.g. Jupyter/Colab

---

• On GitHub:README or mediawiki.org/wiki/Extension:<NAME> press button -> redirect/open Iframe -> Dockerized Wiki running showcasing a specific extension (MVP)
• Post to API of service the repo URL
• Build this repo and

References

• Idea: format: https://github.com/dataspects/mediawiki-manager/blob/main/catalogues/extensions.json
• Legacy:
  • 
  • 
• https://www.mediawiki.org/wiki/Best_practices_for_extensions
• https://www.mediawiki.org/wiki/Project_Open_CSP