Once CC1 code is dropped, the legacy config files won't be read by any GrowthExperiments feature, so marking them as historical in all wikis should be safe.
Relevant files
- MediaWiki:GrowthExperimentsConfig.json
- MediaWiki:NewcomerTasks.json
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Remove no longer in use GENewcomerTasksTopicConfigTitle | mediawiki/extensions/GrowthExperiments | master | +0 -4 |
| 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 | T327655 Epic: Migration of some GrowthExperiments features into MediaWiki core | |||
| Resolved | Urbanecm_WMF | T323811 [EPIC] Community configuration 2.0: Factor Community configuration out of GrowthExperiments | |||
| Resolved | DMburugu | T367429 [Epic] FY 2024-25 Growth Maintenance Work | |||
| In Progress | Sgs | T367574 [Epic] Remove code for Special:EditGrowthConfig | |||
| Open | None | T388516 Retire legacy config pages |
Event Timeline
Comment Actions
We're looking into cleaning up the config pages where community configuration version 1 stored the JSON configs. We aren't sure if keep the history of these can be of any relevance for us the Growth team or communities in the future. I cannot think of any use aside from archeology work in community settings, I'm leaning towards nuking these pages, rather than keeping them in any form (archive or history export etc). What do you think? cc @Trizek-WMF @KStoller-WMF
Comment Actions
We used to track the number of changes on the old community configuration on T285423: Deploy Special:EditGrowthConfig to all wikis. The configuration was edited, but not as heavily as we expected. However, we have some history stored there so I'm reluctant dropping these pages. But wat is the benefit of keeping them no one has an idea of their existence, and didn's even asked to have them imported to the new config (they probably had no idea).
What would be the cost of keeping them?
I need to think more about it.
Comment Actions
Change #1134721 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):
[mediawiki/extensions/GrowthExperiments@master] Remove no longer in use GENewcomerTasksTopicConfigTitle
Comment Actions
Change #1134721 abandoned by Sergio Gimeno:
[mediawiki/extensions/GrowthExperiments@master] Remove no longer in use GENewcomerTasksTopicConfigTitle
Reason:
Done in I2e5bae74219b072636594c7142a55eff50857ad4
Comment Actions
What we can do:
Change the contentmodel for MediaWiki:NewcomerTasks.json and MediaWiki:GrowthExperimentsConfig.json to wikitext with using Special:ChangeContentModel. Then we can add the {{historical}} Template with a comment like {{historical|comment=[https://phabricator.wikimedia.org/T388516 T388516 Retire legacy config pages]}} or whatever would be a good copy to briefly explain the context.
We could also add an i18n system message like “This page is historical.” and then use that with some hard-coded styling and {{int:$historicalpage}}. (Thanks to @Xeno_WMF for the idea!)
Open Question:
- How to do this at scale? We probably don't want to do manual edits to two pages for 300+ Wikipedias