As discussed internally by the Growth-Team, we would like to rename the existing MediaWiki-extensions-CommunityConfiguration project to something like CommunityConfiguration-Growth and then to create a new project with the name CommunityConfiguration.
The goal is to solve/prevent this problem:
- the current MediaWiki-extensions-CommunityConfiguration tag is focused on developing the CommunityConfiguration extension itself, with the prototypical use-case being the GrowthExperiments extension
- with the CommunityConfiguration extension being close to being deployed to the pilot production wikis, other teams are starting to look into making use of it for their own extensions as well (YAY!)
- that means we are seeing tasks like T366016 that are not about developing the CommunityConfiguration extension itself, but about making use of it in another project
- It makes a lot of sense for these projects to have a tag for the CommunityConfiguration component on Phabricator, however this clashes with the current use of that tag
- In addition, a Herald rule is adding the Growth-Team tag to every task tagged with MediaWiki-extensions-CommunityConfiguration. Which means that T366016 and all future such tasks will also be tagged with out team-tag, even though there is nothing for us to do there at all.
Thus with the current setup, we are going to face a lot of noise/unrelated tasks on the Growth-Team and MediaWiki-extensions-CommunityConfiguration boards. That is what we would like to prevent, while still allowing teams integrating with CommunityConfiguration to add a tag for this component to their tasks.