The initial repository for the extension is hosted in gitlab.wikimedia.org/repos/growth/community-configuration. We should move it to gerrit so we can start using the CI and eventually test in beta.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T265163 Create a system to encode best practices into editing experiences | |||
| Open | None | T327563 Enable volunteers to configure Edit Check in ways that align with project policies and norms | |||
| Open | None | T340453 [Epic] FY 2023-24 Growth Maintenance Work | |||
| Open | None | T327655 Epic: Migration of some GrowthExperiments features into MediaWiki core | |||
| Stalled | Feature | None | T328171 Use Community Configuration in Babel extension | ||
| Open | None | T323811 [EPIC] Community configuration 2.0: Factor Community configuration out of GrowthExperiments | |||
| Open | None | T360571 CommunityConfiguration Extension Release Plan | |||
| Resolved | Urbanecm_WMF | T357766 Deploy Community configuration to beta wiki | |||
| Resolved | Sgs | T354360 Community configuration: Migrate repository to gerrit | |||
| Open | None | T360954 Deploy CommunityConfiguration to testwiki |
So you migrate from GitLab to Gerrit to have to migrate back to GitLab at some point in the future? :-/
Unfortunately, that's the state of things right now :-/. Wikimedia GitLab currently does not have a working CI setup for MediaWiki, and it is unreasonable to expect Growth team engineers to be capable of setting a CI pipeline in GitLab, since that's not where we shine. I agree it is unfortunate the migration will happen twice, but I think that's the easiest way as of now.
That's sadly correct. The reason for it is to have standard CI jobs and deploymeny pipeline applied to the extension asap given our tight timeline. At the moment of writing the issue I had no knowledge of the https://gitlab.wikimedia.org/repos/technical-documentation/deployment-pipeline-sandbox repository which seems a starting point for anyone willing to apply MW aware CI jobs in Gitlab. I will take a look into it and try to use it for setting up CI in our demo extension for the CC2.0 project https://gitlab.wikimedia.org/repos/growth/community-configuration-example. Thanks for sharing your question :)
Change 994692 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):
[integration/config@master] Zuul: [mediawiki/extensions/CommunityConfiguration] Add basic tests
Change 994692 merged by jenkins-bot:
[integration/config@master] Zuul: [mediawiki/extensions/CommunityConfiguration] Add basic tests
Change 994703 had a related patch set uploaded (by Jforrester; author: Jforrester):
[integration/config@master] Zuul: [mediawiki/extensions/CommunityConfiguration] Add in-wikimedia-production
Change 994703 merged by jenkins-bot:
[integration/config@master] Zuul: [mediawiki/extensions/CommunityConfiguration] Add in-wikimedia-production
Change 994700 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):
[mediawiki/extensions/CommunityConfiguration@master] Clean code style and phan errors
Change 994700 merged by jenkins-bot:
[mediawiki/extensions/CommunityConfiguration@master] Clean code style and phan errors
I noted the migration in the GitLab repo README and marked it read-only. Is there something else that needs to be as part of this task, @Sgs?