On Mon, 2023-05-29 at 08:56 +0200, Neal Gompa wrote: > On Mon, May 29, 2023 at 8:50 AM Philip Wyett <philip.wy...@kathenas.org> > wrote: > > On Mon, 2023-05-29 at 07:50 +0200, Neal Gompa wrote: > > > On Sat, May 27, 2023 at 2:52 PM Ali Erdinc Koroglu > > > <aekoro...@linux.intel.com> 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. > > > > > > > > > > Maybe 'org' in the naming rather than 'corp' as not all businesses and > > entities are corps. More > > sedate naming and would cover other distros, charities and other groups in > > general? > > > > Sure. I'm fine with that. I think it's just important to not call it a > SIG, because it's not a "special interest group" in the sense that we > use it for. >
Agreed. SIG is not appropriate in this instance. > > -- > > *** Playing the game for the games own sake. *** > > > > > > Associations: > > > > * Debian Maintainer (DM) > > * Fedora/EPEL Maintainer. > > * Contributor member of the AlmaLinux foundation. > > > > Right, it's fairly well-known how broad my association in FOSS is too, > so I totally get this point. :) > Indeed. A man after my own heart. ;-) Regards Phil -- *** Playing the game for the games own sake. *** Associations: * Debian Maintainer (DM) * Fedora/EPEL Maintainer. * Contributor member of the AlmaLinux foundation. WWW: https://kathenas.org Buy Me a Coffee: https://www.buymeacoffee.com/kathenasorg Twitter: @kathenasorg Instagram: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
