...
I have grouped them in the following types of repos:
API
Core
Documentation
Integration
Several of these are managed by community members and will have their own permissions that need to be set up
Language packs
Plugin
These need to have the same semantic versioning as core
Tools
These are tools that are used by the project or things like Docker
Theme
These need to have the same semantic versioning as core
Website
...
List of current labels on mautic/mautic
Used gh api /repos/elastic/$repo/labels --paginate
to get a list.
https://docs.google.com/spreadsheets/d/1A7Mxcqo4h8ZA18rbGi0awEmIFC8KD-322ztQxE4TSd8/edit?usp=sharing
...
https://docs.google.com/spreadsheets/d/1sGUGnv19qJ3CP_rKUuNdvipzLaI5bqNnPQuPHRWr14c/edit?usp=sharing
Proposed groupings of repos & team permissions
We can group repos together so that they get the same set of rules, rather than having to set them individually. I propose that we group them as in the spreadsheet above with the addition of a group called security.
We can set the permissions by team using the org file - I have set the suggested permission levels in the spreadsheet.