On Sat, May 27, 2023 at 2:52 PM Ali Erdinc Koroglu <aekoroglu@xxxxxxxxxxxxxxx> wrote: > > > > On 27/05/2023 15:18, Florian Weimer wrote: > > * Kevin Fenzi: > > > >> Today we have packager groups used in src.fedoraproject.org to allow a > >> group of people to maintain packages. In the past this has been used for > >> SIGs/packaging areas. ie, python-packaging-sig or robotics-sig or the > >> like. > >> > >> FESCo has been asked about creating company related groups. > >> ( https://pagure.io/fesco/issue/2966 and https://pagure.io/fesco/issue/2929 ) > >> ie, foocorp-sig / foocopr-packagers. These groups would then be used to > >> help maintain packages that foocorp finds of interest/value. > > > > Will these groups automatically make members part of the packager group? > > Or will that be a separate step? > > I think this can be like that: "To join the foocorp-SIG, packager group membership is a requirement" > IMO, we should not call these SIGs either. I'm not sure exactly what the naming convention should be, but one thought would be "corp-maint_<corpname>" (or flip it around if you wish). e.g., "corp-maint_aiven" for Aiven employees. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
