From: agustin.benito@codethink.co.uk (Agustín Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Proposal: Gitlab role policy
Date: Mon, 20 Aug 2018 18:32:28 +0200 [thread overview]
Message-ID: <4289285.ekA2XtEEmD@linux-if6s> (raw)
In-Reply-To: <8acc7cf1-e1b9-524c-3452-3204ac355fdb@toshiba.co.jp>
Hi,
On Monday, 20 August 2018 16:08:36 CEST KOBAYASHI Yoshitake wrote:
> Hi Agustin,
>
> Thanks for the proposal.
> I think this simple policy works fine in CIP project.
In today's TSC meeting this policy was approved. Thank you all. I will implement it in the coming days. I might ping you individually if you are affected by it.
>
> Best regards,
> Yoshi
>
> On 2018/08/09 18:21, Agust?n Benito Bethencourt wrote:
> > 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
> >
> >
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
>
--
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd
We respect your privacy. See https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2018-08-20 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 9:21 [cip-dev] Proposal: Gitlab role policy Agustín Benito Bethencourt
2018-08-20 14:08 ` KOBAYASHI Yoshitake
2018-08-20 16:32 ` Agustín Benito Bethencourt [this message]
2018-08-30 9:18 ` Agustín Benito Bethencourt
2018-09-03 6:50 ` 河合英宏 / KAWAI，HIDEHIRO
2018-09-03 7:45 ` Agustín Benito Bethencourt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4289285.ekA2XtEEmD@linux-if6s \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox