The DCAT php code should really be in its own repo rather than in puppet. This will mean that some deployment setup for the code from its new repo will be needed as well.
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| snapshot: Deploy DCAT from operations/dumps/dcat | Hoo man | operations/puppet | production | +7 -1 K |
I chatted with @hoo on irc; the DCAT code will go into a misc repo and scap3 will be the likely deployment tool, using the dataset user (have to make sure that works).
Sounds fine by me. I still believe as in T103087#1386814 that mediawiki/extensions/Wikibase/repo/maintenance is the natural place (with config somewhere else) but I'm happy to have it anywhere which works and makes it maintainable.
If that's a better location, great, because that also solves the deployment issue. @hoo what are your thoughts?
DCAT is a w3c standard for describing dumps. I see the current code as a first step for us to support this for all dumps, not just for Wikidata / Wikibase. Thus I believe it should be managed as part of the dump infrastructure, not of Wikibase.
More reasons to decouple DCAT from Wikibase:
I've proposed operations/dumps/dcat as an alternative. There are several repos under dumps already.
Requested operations/dumps/dcat now (https://www.mediawiki.org/w/index.php?title=Git%2FNew_repositories%2FRequests%2FEntries&type=revision&diff=1961206&oldid=1960076).
Change 260247 had a related patch set uploaded (by Hoo man):
snapshot: Deploy DCAT from operations/dumps/dcat
The repo has been created and the code has been imported. A patch for removing the files from puppet and cloning from git instead has been uploaded (of course that's only a stopgap until we can move to scap3).
https://gerrit.wikimedia.org/r/260604 as the last piece and it's live and happy on snapshot1003. closing this.