help: Certain terms lack definitions
Supposedly, issues regarding the help pages should be posted to this very issues list. (Am I correct?)
Summary
The CONTRIBUTING and permissions pages make certain assumptions about readers' knowledge. Certain terms lack explicit definitions. (BTW, presumably this arose from the curse of knowledge.)
Expected behavior
1. The CONTRIBUTING page should state explicitly where to post issues about the help pages.
2. Section Request Access to a Project (on the Add User page) should state explicitly (if true) that by the term "user," it means anyone in the world.
Also, more simply, it should use the term "users" (instead of introducing a new term, "non-members").
3. The permissions page should describe explicitly the particular permissions which are granted to anyone in the world, by default.
4. That page should describe the general purpose of the Reporter role, and of the Guest role.
5. Section Protected Branches (on the Protected Branches page) says:
To prevent people from messing with history or pushing code without review, we've created protected branches.
The term "people" here should be "Developers and above."
6. Section Overview (on the Protected Branches page) says:
By default, a protected branch...prevents anyone from force pushing to the branch [and] prevents anyone from deleting the branch[.]
Similarly, the term "anyone" here should be "Developers and above."
Actual behavior
1. The CONTRIBUTING page doesn't explicitly say where issues about the help pages should be posted.
2. Section Request Access to a Project (on the Add User page) says:
As a user, you can request to be a member of a project.
By the term "user", I think this sentence means anyone in the world. This fact is not stated explicitly. It also says:
As a project owner you can enable or disable non members to request access to your project. Go to the project settings and click on Allow users to request access.
The term "non members" here seems equivalent to "users." (Thus the present text is confusing.)
3. The permissions page doesn't explicitly describe the particular permissions which are granted to anyone in the world, by default.
4. That page doesn't describe the general purpose of the Reporter role, or even of the Guest role.
5. Section Protected Branches (on the Protected Branches page) says:
To prevent people from messing with history or pushing code without review, we've created protected branches.
However, users (in the world) below the Developer level already are prevented from pushing to unprotected branches. (Thus the present text is confusing.)
6. Section Overview (on the Protected Branches page) says:
By default, a protected branch...prevents anyone from deleting the branch [and] prevents anyone from force pushing to the branch[.]
However, similarly, users (in the world) below the Developer level already are prevented from deleting or force-pushing to unprotected branches. (Thus the present text is confusing.)
Output of checks
This bug happens on GitLab.com.