From mboxrd@z Thu Jan  1 00:00:00 1970
From: agustin.benito@codethink.co.uk (=?ISO-8859-1?Q?Agust=EDn?= Benito Bethencourt)
Date: Thu, 09 Aug 2018 11:21:50 +0200
Subject: [cip-dev] Proposal: Gitlab role policy
Message-ID: <2718361.41IWGt5yYx@linux-if6s>
To: cip-dev@lists.cip-project.org
List-Id: cip-dev.lists.cip-project.org

Hi,

now that we have new kernel maintainers it might be time to pay a little attention  to the user permissions/roles policy at Gitlab.com.

Some time ago we agreed to divide the different repositories in subgroups in preparation for this time. We can segment the permissions we provide to CIP contributors by subgroup. We have the following subgroups:
* 3rd party software (mostly related with testing for now (special case)
* cip-testing
* cip-kernel
* cip-core

For simplicity, I suggest the following:
* TSC representatives from each company will be owners, as well as the tool admin, at group level.
* We will have no group maintainers by default since we will not have repos at this level but we will enclose them in subgroups. So at this group level we will provide Developer or Reporter roles only to CIP participants.
* We assign the maintainer role to those who should have it, because they are responsible of a specific area, at subgroup level. 
* Specific people can hold the maintainer role at repo (project) level based on the subgroup maintainer decision. 

This simple policy can be extended as more people join.

Best Regards
 
-- 
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd
We respect your privacy.   See https://www.codethink.co.uk/privacy.html