We want to deploy EntitySchema to production and for that we need to enable it on test first.
- Due Date
- May 22 2019, 10:00 PM
|operations/mediawiki-config : master||deploy WikibaseSchema to test|
|Resolved||noarave||T216955 deploy EntitySchema to production|
|Resolved||Ladsgroup||T216956 deploy EntitySchema to test|
|Resolved||Michael||T216957 deploy EntitySchema to beta|
|Resolved||Reedy||T216692 Security review for WikibaseSchema|
|Resolved||hoo||T221648 Add EntitySchema to make-wmf-branch/config.json|
|Declined||Lucas_Werkmeister_WMDE||T221649 Add WikibaseSchema submodule to 1.34.0-wmf.1 branch of mediawiki/core.git|
|Resolved||Michael||T221650 Add WikibaseSchema to wmf-config/extension-list|
|Resolved||Michael||T221651 Define wmgUseWikibaseSchema variable in mediawiki/config (default false)|
|Resolved||Michael||T221652 Set wmgUseWikibaseSchema to true on beta|
|Resolved||Rosalie_WMDE||T221653 Update EntitySchema extension on mediawiki.org|
|Resolved||WMDE-leszek||T223120 Add configuration for ShExSimple url|
@Ifygal3 - thanks for your offer of help :)
Unfortunately, this issue is not one that can be just picked up.
It's really being used as a "todo" task for the team at WMDE working on shape expressions for Wikidata. It doesn't really require any "code" to be written but is more a of a procedure that needs to be undertaken by someone who's already working on this new extension.
I don't know where to leave this feedback, but I'll place it here for now:
- This extension registers a generically called namespace named "Schema", this overlaps with at least one other extension already (EventLogging). I recommend choosing a more specific name.
- This extension registers two generically called special pages, "Special:NewSchema" and "Special:SchemaText". I don't know what they do. Knowing Wikidata from a user perspective mainly, I would expect the name to be more clear and specific about what it is for.
- It's unclear to me why this is going through the costly overhead of yet another Wikibase* MediaWiki extension. If the code is meant to be re-usable, perhaps publish it as a Composer library installed into Wikibase via vendor or gitmodule? I understand that is how other parts of Wikibase are organised. What end-user product story is the extension offering on its own? (It appears none, but I don't know for sure.)