The "Extension Used by Wikimedia" group in translatewiki has grown very large over the years. It has nearly 14,000 messages to translate, and this is hard to manage, especially in languages that have a small translators community—often just one person.
It has an "Extension Used by Wikimedia - Main" subgroup, but both have become very large, and the distinction between them is not entirely clear.
At this point I propose to convert the "Extension Used by Wikimedia" group into a group that only includes other aggregate groups. These are the groups I suggest:
- Main: Messages that are likely to be seen by most readers or editors. This group already exists, but may be adjusted somewhat in the future after the initial split of the full extensions group.
- Technical: API help messages (see T189982), and some other extensions that are useful only for developers and ops people, for example OpenStackManager. (patch)
- Legacy: Extensions that are deployed on projects, but are not likely to be developed further or installed on new wikis. Examples: LiquidThreads, EducationProgram. This may also include old skins such as Cologne Blue, given that they are mostly used by users of projects that started long ago, and are most likely already translated. (patch)
- Fundraising: Donation gateways, Contribution tracking, etc. (patch)
- Wikivoyage: GeoCrumbs, WikidataPageBanner, and several others. (patch)
- (Perhaps also Wikisource, Wikinews, and Wikibooks, but there aren't a lot of extensions that are unique to these projects, so it's not a high priority.)
- Media: MediaViewer, VIPS, GWToolset, etc. (patch)
- Community: CentralNotice, SecurePoll, Translate, etc.
- Upcoming: Extension that may be deployed in the future. Current examples: CollaborationKit, JADE, Capiunto. (patch)
- Advanced: Everything else. A lot of these extensions are pretty important, such as Score, CentralAuth, FlaggedRevs, etc. (patch)
A somewhat related task: T167762: Split core en.json to several files.