**Project Information **
* Name of tool/project: Community Configuration
* Project home page: https://www.mediawiki.org/wiki/Community_configuration_2.0
* Name of team requesting review: #growth-team
* Primary contact: @KStoller-WMF (Product Manager), @Sgs @Urbanecm_WMF (Growth Team engineers)
* Target date for deployment: **March 2024**
* Link to code repository / patchset: https://gitlab.wikimedia.org/repos/growth/community-configuration
* Link to scc output for general sizing of codebases (https://github.com/boyter/scc):
**Description of the tool/project: **
The #growth-team is currently working on the [Community configuration 2.0](https://www.mediawiki.org/wiki/Community_configuration_2.0) project, which allows wiki administrators to configure MediaWiki on-wiki, without having to go through Phabricator or editing the mediawiki configuration. This is a continuation, and improvement of the [Community configuration 1.0 project](https://www.mediawiki.org/wiki/Growth/Community_configuration), which is implemented within the GrowthExperiments as one of its integral parts.
Detailed information about the project, issues identified in the CC1.0 implementation, as well as a high-level overview of its architecture, can be found in the [CC2.0 Product Requirements Document](https://docs.google.com/document/d/1Ai7ib6h1q9ly5xClowK2cn0CKIJp3Z1KpkvwzVMk32U/edit).
**Description of how the tool will be used at WMF:**
[[ https://www.mediawiki.org/wiki/Community_configuration_2.0#Use_cases | Product teams with a Community Configuration use case ]], will be able to utilize the Community Configuration extension to allow communities to customize funtionality.
**Dependencies**
>TBD: List dependencies, or upstream projects that this project relies on.
**Has this project been reviewed before?**
> No. Related: {T207798}.
**Working test environment**
>TBD
**Post-deployment**
> #growth-team
NOTE: this project is part of the [[ https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2023-2024/Product_%26_Technology/OKRs | WMF Annual Plan: WE1.2 ]]. The Growth team is not yet ready for a full review, but hopes the Security review can be scheduled for **February 2024**.