Hi Folks!
We had a thread a few weeks ago about the usage of the “centos” namespace on gitlab: https://lists.centos.org/pipermail/centos-devel/2022-February/120216.html
The authentication angle is progressing up to the point that we would like to open up the opportunity for a couple of SIGs to onboard with gitlab and help us round the edges. The idea being to open this up to all the SIGs interested in a few weeks once we have clearer documentations and guidelines around the usage of GitLab.
We are currently working on that set of best-practices that SIGs which would like to use the centos namespace on gitlab will need to agree and follow.
If you are interested, please let us know (just not everyone at once!) :)
Thanks,
Brian
On behalf of the CentOS Automotive SIG, we'd be glad to be guinea pigs part of this effort. Thanks for setting it up!
Jeffrey "Jefro" Osier-Mixon | jefro@redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive
On Thu, Mar 31, 2022 at 10:44 AM Brian Stinson bstinson@redhat.com wrote:
Hi Folks!
We had a thread a few weeks ago about the usage of the “centos” namespace on gitlab: https://lists.centos.org/pipermail/centos-devel/2022-February/120216.html
The authentication angle is progressing up to the point that we would like to open up the opportunity for a couple of SIGs to onboard with gitlab and help us round the edges. The idea being to open this up to all the SIGs interested in a few weeks once we have clearer documentations and guidelines around the usage of GitLab.
We are currently working on that set of best-practices that SIGs which would like to use the centos namespace on gitlab will need to agree and follow.
If you are interested, please let us know (just not everyone at once!) :)
Thanks,
Brian
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Thu, 2022-03-31 at 12:44 -0500, Brian Stinson wrote:
Hi Folks!
We had a thread a few weeks ago about the usage of the “centos” namespace on gitlab: https://lists.centos.org/pipermail/centos-devel/2022-February/120216.html
The authentication angle is progressing up to the point that we would like to open up the opportunity for a couple of SIGs to onboard with gitlab and help us round the edges. The idea being to open this up to all the SIGs interested in a few weeks once we have clearer documentations and guidelines around the usage of GitLab.
We are currently working on that set of best-practices that SIGs which would like to use the centos namespace on gitlab will need to agree and follow.
If you are interested, please let us know (just not everyone at once!) :)
The Hyperscale SIG already has a private repo on gitlab we use for secrets management. Would that be an appropriate usecase for this namespace?
Cheers Davide
On 31/03/2022 19.44, Brian Stinson wrote:
Hi Folks!
We had a thread a few weeks ago about the usage of the “centos” namespace on gitlab: https://lists.centos.org/pipermail/centos-devel/2022-February/120216.html
The authentication angle is progressing up to the point that we would like to open up the opportunity for a couple of SIGs to onboard with gitlab and help us round the edges. The idea being to open this up to all the SIGs interested in a few weeks once we have clearer documentations and guidelines around the usage of GitLab.
We are currently working on that set of best-practices that SIGs which would like to use the centos namespace on gitlab will need to agree and follow.
If you are interested, please let us know (just not everyone at once!) :)
I'm interest and happy to help testing the new gitlab centos namespace for the Kmods SIG.
Best
Peter
Thanks,
Brian
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 31/03/2022 20:33, Davide Cavalca via CentOS-devel wrote:
On Thu, 2022-03-31 at 12:44 -0500, Brian Stinson wrote:
Hi Folks!
We had a thread a few weeks ago about the usage of the “centos” namespace on gitlab: https://lists.centos.org/pipermail/centos-devel/2022-February/120216.html
The authentication angle is progressing up to the point that we would like to open up the opportunity for a couple of SIGs to onboard with gitlab and help us round the edges. The idea being to open this up to all the SIGs interested in a few weeks once we have clearer documentations and guidelines around the usage of GitLab.
We are currently working on that set of best-practices that SIGs which would like to use the centos namespace on gitlab will need to agree and follow.
If you are interested, please let us know (just not everyone at once!) :)
The Hyperscale SIG already has a private repo on gitlab we use for secrets management. Would that be an appropriate usecase for this namespace?
Basically gitlab.com/CentOS is tied to SSO (and so reusing your existing ACO/FAS account) and so we can reuse group memberships to grant permissions on subgroups/projects
BTW, Pingou started a PR (open for comments) for the SIG Guide (https://git.centos.org/centos/sig-guide/pull-request/4) so either we discuss it on centos-devel list, or just discuss it there (through comments and multiple iterations)
On Thu, Mar 31, 2022 at 06:33:12PM +0000, Davide Cavalca via CentOS-devel wrote:
The Hyperscale SIG already has a private repo on gitlab we use for secrets management. Would that be an appropriate usecase for this namespace?
One thing to be aware of with private repos is that gitlab's access are hierarchical. So owners/maintainers at the "centos" namespace level will have access to everything under it. Similarly, if you have owner/maintainer to say, centos/hyperscale, you will have access to everything underneath it.
In other words, if a SIG creates a private project, that project will be accessible to everyone who has access to the namespaces above it, so concretely, that private project will be accessible to the people administrating the "centos" namespace, regardless of if they are a member of the SIG or not.
Am I clear in what I'm saying here? I feel like I'm confusing.
Pierre