In T374431, we added a maintenance script that updates emergency defaults (to be checked into the repository). However, the path to them is currently hardcoded, even though it would make more sense if they were close to the schema files (as those two files are related to each other). The original idea was to allow extensions to customize that path via attributes. However, this is not readily possible, as ExtensionRegistry only returns attributes in their merged form (from _all_ extensions together), without including information about what extension defined what value. Hence, this is filled as a separate task, following up the work done in T374431.
Description
Description
| 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 | |||
| Open | None | T350731 Community Configuration: Monitoring & Contingency plan | |||
| Open | None | T367516 Community Configuration: Create Emergency Shutdown option | |||
| Open | None | T376985 Allow extensions to define where emergency defaults are stored |