We're renaming the extension to Extension:JADE.
We have Diffusion and Github mirrors of this repo, those should be carried over to the new name by either moving or cloning.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T212435 Review real-world query plans and performance for Jade | |||
| Declined | None | T238877 Write Huggle labels to Jade | |||
| Declined | calbon | T183381 Deploy pilot of Jade to a small set of wikis. | |||
| Resolved | Reedy | T211046 Rename "JADE" extension to "Jade" | |||
| Resolved | Ladsgroup | T212181 Rename JADE->Jade in continuous integration | |||
| Resolved | Ladsgroup | T212182 Rename JADE->Jade in beta cluster configuration | |||
| Resolved | • mmodell | T212180 Clone gerrit repo mediawiki/extensions/JADE to mediawiki/extensions/Jade |
Event Timeline
Comment Actions
According to https://gerrit.wikimedia.org/r/Documentation/intro-project-owner.html#project-rename Gerrit core does not support the renaming of projects.
We could create a new repo, export everything from JADE and import it back to Jade; or
Install the rename-project plugin on Gerrit to do it (T201953).
I'm mentioning here @Paladox for advice.
Comment Actions
We should create a new repo for now, since the rename plugin does not support NoteDB yet.
Comment Actions
When importing a repo I usually do:
- git clone --bare ssh://$repo_clone_url
- git push --mirror ssh://$repo_dest_url
This needs the forge-author-id, forge-commit-id and push privs granted to the Gerrit Managers in the repo though.
Comment Actions
Looks good from a quick coup d'œil. Now they have to stop committing to JADE and continue on Jade.
Comment Actions
Yes it should be archived (and not deleted since we would lost changes and reviews made to it).
Projects-Cleanup has a link on the side bar Fill an archive request which comes with a long list of steps necessary to properly archive the extension. Tasks are typically handled by several volunteers (yeah!!).