We have cases were projects could be logically grouped into a meta-project, at least to avoid having a huge list of projects exposed to localizers. Example: AMO, (upcoming) system add-ons, Foundation. Not completely sure what grouping projects would look like: is it only to simplify the list of projects or something more (e.g. aggregated stats)?
I wonder if this could help manage permissions (bug 1223945). As locale leader, I’d rather set different permissions between meta-projects rather than per project.
I think we should not mix permissions and groupped projects and let it on every team to decide on who is doing what. For example AMO might be done as a website and system addons as part of Firefox instead of under AMO umbrella.
You need to log in before you can comment on or make changes to this bug.