Extension Store: Difference between revisions
Jump to navigation
Jump to search
Lex Sulzer (talk | contribs) (โโ) |
Lex Sulzer (talk | contribs) (โโ) |
||
| Line 21: | Line 21: | ||
#* [[Action:7]] | #* [[Action:7]] | ||
#* [[Event:85|Voted that the Duplicator will be the first extension]] | #* [[Event:85|Voted that the Duplicator will be the first extension]] | ||
#* Or from open content service platform (wikibase solutions) or from document management package (NASA) | |||
# 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") | # 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") | ||
# Certify the first extension and publish it safely* in the MWStake Extension Store. | # Certify the first extension and publish it safely* in the MWStake Extension Store. | ||
# Secure longterm stewardship for the extension. | # Secure longterm stewardship for the extension. | ||
Revision as of 05:02, 24 March 2022
Use cases
- 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.
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:
- The MWStake ES Certification Committee accepts MyExtension's unit tests as being sufficient.
- All of MyExtension's unit tests are passing.
- 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
- Constitute the MWStake ES Certification Committee.
- Decide on the MWStake ES Certification Committee members' remuneration of $X.-/hour.
- Decide on the first extension to certify.
- Kick-off MWStake extension stewardship at SMWCon 2019
- Voted that the Duplicator will be the first extension
- Or from open content service platform (wikibase solutions) or from document management package (NASA)
- 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")
- Certify the first extension and publish it safely* in the MWStake Extension Store.
- Secure longterm stewardship for the extension.
- Ensure unit and integration tests sufficiency and passing with regard to evolving MW core and extension packages.
