The #growth-team currently works on the [Community configuration 2.0](https://www.mediawiki.org/wiki/Community_configuration_2.0). The feature is implemented as a separate extension, which is called [CommunityConfiguration](https://www.mediawiki.org/wiki/Extension:CommunityConfiguration). To make it easy to work with Community configuration in a shared environment, we'd like to deploy it to beta as soon as reasonably possible. This task exists to track the deployment of Community configuration into the Beta cluster.
==== Checklist
According to the [Writing an extension for deployment](https://www.mediawiki.org/wiki/Extension:CommunityConfiguration) guide at MediaWiki.org, the following needs to be done before beta deployment.
[X] MediaWiki.org extension documentation page ([exists](https://www.mediawiki.org/wiki/Extension:CommunityConfiguration))
[ ] MediaWiki help page (suggested name `Help:Extension:CommunityConfiguration`)
[X] Gerrit repository exists (done in T354360)
[X] Phabricator project exists (#communityconfiguration)
[ ] Stewardship: [Developes/Maintainers](https://www.mediawiki.org/wiki/Special:MyLanguage/Developers/Maintainers) lists who is responsible for the project long-term
[ ] Localization: Extension is localizable via TranslateWiki.net
[ ] Reviews
[ ] Application security review (T349568)
[ ] Security review of any new external dependencies
We will also need to request a performance review, but that is typically not a deployment blocker, hence, not including it in the checklist above.
In addition to the checklist above, the guideline also recommends upholding the following standards; before proceeding with deployment, we should double check they're met.
[ ] Unit testing: The extension should be reasonably unit testable
[ ] Reasonable feature flags (probably not appropriate for our use-case)