The Growth team introducedCommunity configurationto allow administrators to customize how the Growth features should work like at individual wikis. Community configuration makes deployment easier for Growth, as we don't have to deliver a "one size fits all" approach. It is also easier for communities to make use of Special:EditGrowthConfig, than having to communicate with the Growth team to request a change in the mediawiki configuration.
As of 2022, Community configuration is an integral part of the GrowthExperiments extension, which means that only the Growth team can benefit easily from it as of now. However, Community configuration can be useful for other teams/projects as well (see usecases below), and ideally, Community configuration should be usable for any MW extension/skin/core feature, not only for the Growth features.
Workboard:MediaWiki-extensions-CommunityConfiguration
Release plan:T360571: CommunityConfiguration Extension Release Plan
Mediawiki Project Page:Community Configuration
Possible usecases
- T323632: Special:PageTriageSettings
- T265163: Create a system to encode best practices into editing experiencesEdit check:If Editing works on encoding best practices into editing experiences, they might want to make these features community configurable.
- T328171: Use Community Configuration in Babel extension
- Citoid configuration
- Web2Cit(T337105)
- T335124: Create a framework for enrolling users in experimentsfor enabling / disabling experiments or adjusting opt-in rates by platform
- T336934: Enable communities to configure automated reversion of bad edits(Moderator Tools team): Based on Research's revert prediction model (T314384).
- Local customization of AbuseFilter (T45761)
- SpamBlacklist (T337431#8885041)
- T322740: Contribute entry point:communities may want to disable or reorganize Contribute menu options
- Private Incident Reporting System- allow some degree of community configuration for incident reporting.Incident-Reporting-System Phabricator Workboard
- T326152: [16 hours] Spike: Explore using growthexperiments user configuration for QuickSurveys
- Gadgets 2.0? (Gadget definitions are already implemented in a different way:T106177: Implement Gadget and Gadget definition namespaces plus their content modelsbut conceptually, it seems like a good match)
- T341386: Allow On-wiki configuration for temporary site logo changes
- NewUserActionsconfiguration
- translatewiki.netterminology gadget's terminology pages
- campaign configuration (GrowthExperiments,UploadWizard,MediaUploader,ContentTranslation)
- T303433: Allow Stewards to enable 'emergency CAPTCHAs' for anonymous IP edits
- Extension:Proofread Page/ProofreadPage
- Move-Files-To-Commons
- WikiLovecustomization
- TemplateData'stemplatedata-doc-subpagefake message that encodes the local naming scheme for template documentation subpages
- T330354: [Goal] Build the Metrics Platform control plane
- T326354: Community Configuration for Revert notification: improve language and allow communities to configure defaults
- Android App Edit Patrol feature: 1) to allow communities to add/remove user talk Example Messages from the AppT358265and 2) to allow communities to lower the threshold of who this task is available to