Commit 69b79c76 authored by intrigeri's avatar intrigeri
Browse files

Restructure + add link

parent 1be868c0
......@@ -326,12 +326,26 @@ first, to ensure you're not asking them to do something that's outside
of the scope of their job. And please justify your suggestions.
Please check these views once in a while and talk to us! :)
# Access control
<a id="operations"></a>
# Operations
## Administration of GitLab
Our friends at <https://www.immerda.ch/> host [[!tails_gitlab desc="our GitLab
instance"]].
The Tails [[system administrators|working_together/roles/sysadmins]]
administrate this GitLab instance.
<a id="access-control"></a>
## Access control
XXX: document the process to grant access level to users, once this [is
implemented](https://salsa.debian.org/tails-team/gitlab-migration/issues/33).
## Objects
### Objects
- _Canonical Git repo_: the authoritative [[!tails_gitlab tails/tails]]
repository, hosted on GitLab
......@@ -360,7 +374,7 @@ implemented](https://salsa.debian.org/tails-team/gitlab-migration/issues/33).
end-to-end encryption between members of these teams.
This is a hypothetical problem for now.
## Subjects
### Subjects
- An _admin_ can do anything that other roles can, and:
- can delete issues
......@@ -405,16 +419,16 @@ implemented](https://salsa.debian.org/tails-team/gitlab-migration/issues/33).
- can submit issues
- can submit MRs
## Implementation
### Implementation
### Relevant GitLab doc
#### Relevant GitLab doc
- [Permissions](https://docs.gitlab.com/ee/user/permissions.html)
- [Authorization for Merge requests](https://docs.gitlab.com/ce/user/project/merge_requests/authorization_for_merge_requests.html)
- [Protected Branches](https://docs.gitlab.com/ce/user/project/protected_branches.html)
- [Groups](https://docs.gitlab.com/ee/user/group/)
### Access levels
#### Access levels
We use the [Protected branch
flow](https://docs.gitlab.com/ce/user/project/merge_requests/authorization_for_merge_requests.html#protected-branch-flow):
......@@ -430,10 +444,3 @@ flow](https://docs.gitlab.com/ce/user/project/merge_requests/authorization_for_m
create merge requests.
- Our Jenkins CI jobs generation process is the same as in pre-GitLab days.
# Administration of GitLab
Our friends at <https://www.immerda.ch/> host [[!tails_gitlab desc="our GitLab
instance"]].
The Tails [[system administrators|working_together/roles/sysadmins]]
administrate this GitLab instance.
......@@ -229,6 +229,7 @@ Below, importance level is evaluated based on:
- host Tails issues
- host most Tails [[Git repositories|contribute/git]]
* access: public + some data with more restricted access
* operations documentation: [[contribute/GitLab#operations]]
* end-user documentation: [[contribute/GitLab]]
* configuration:
- immerda hosts our GitLab instance using [this Puppet
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment