Extension Store

Use cases

1. 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.
2. 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.

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 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. (E.g. from open content service platform (wikibase solutions) or from document management package (NASA))
4. Certify the first extension and publish it safely* in the MWStake Extension Store.

References

• Legacy: https://mwstake.org/mwstake/img_auth.php/0/09/MW_Extensions_EMF_Certification.png
• https://www.mediawiki.org/wiki/Best_practices_for_extensions
• https://www.mediawiki.org/wiki/Project_Open_CSP