Decide our gitlab permissions policy, and understand its implication.
We should figure out what we want our gitlab permissions to look like, so that we can make it easier to make decisions about account requests. This ticket isn't yet about requesting any particular action from the gitlab admins, but rather, deciding what to ask them for.
Here is a handy link about gitlab permissions: https://docs.gitlab.com/ee/user/permissions.html
The different permission levels are "Guest, Reporter, Developer, Maintainer, Owner", in order of ascending capability.
Users can be assigned these permissions in a single project (e.g., tpo/core/tor), or in an entire group (e.g. tpo/core). The highest level of permission applies, so for example if you are a tpo/core Reporter but a tpo/core/chutney Developer, you get counted as a "Developer" for all your chutney actions.
This small number of levels means that some permissions always go together. For example, a "Reporter" can view confidential issues, assign and label issues, lock threads, and pull projects... but unless you are a "Reporter" you cannot open a merge request.
Similarly, only a Developer can assign/approve/manage merge requests, or edit the wiki pages... but any Developer can also create new branches in the repository, push to non-protected branches, remove git tags and so on.
Taken together have implications for what things go in which "project".
For instance, can we have a wiki that anybody with an account can edit? Only if we put it in a project or group where nothing else important is, since we will need to make those people Developers in that project.
Can we use confidential issues? Only if we put them in a project where nobody untrusted can make merge requests, since only Reporters can make MRs, but everybody who can make MRs.
I'm suggest that we try to figure out something that works here for us in tpo/core, and then propose it to the rest of the org.