#11438 RFR: FAS group pytorch-sig
Closed: Fixed by ryanlerch. Opened by jsteffan.

Describe what you would like us to do:


Create a FAS group pytorch-sig for the purpose of shared package ownership and maintenance.

When do you need this to be done by? (YYYY/MM/DD)


At leisure.


Ok! There are a few steps to getting this done:

  1. A mailing list needs to be created to get all the mails to the group. I assume pytorch-sig@lists.fedoraproject.org ? This list has to be created by fedora-infra, we just need to get your confirmation the address is OK - This must be a private list as it will be CC'ed on security bugs.
  2. Next, you will need to create a bugzilla.redhat.com account with that mailing list as the username (obviously the list will need to be created first).
  3. fedora-infra will need to create the pytorch-sig group to Fedora Accounts aka FAS
  4. fedora-infra will need to add the pytorch-sig group to src.fedoraproject.org this is a pagure group on the pagure instance (fedora infra)
  5. You can then add the users as members to the new Fedora Accounts group will need to logout and back on to src.fedoraproject.org to get the new group membership.
  6. Finally the group will need to be added to all the packages in src.fedoraproject.org pagure

Info we need from you:

  • pytorch-sig@lists.fedoraproject.org ok for the mailing list?
  • Fedora accounts usernames of the users that are sponsors in the new group. (they can then add the members as required)
  • Short Description for the Fedora Accounts group.

Metadata Update from @ryanlerch:
- Issue assigned to ryanlerch

  • pytorch-sig@lists.fedoraproject.org ok for the mailing list?

+1

  • Fedora accounts usernames of the users that are sponsors in the new group. (they can then add the members as required)

jsteffan

I'll collect and add more sponsors after this is all setup.

  • Short Description for the Fedora Accounts group.

Maintainers responsible for packages that enable PyTorch in Fedora.

Ok!

Note that after you add users to this group in Fedora Accounts, they will need to logout and log back in again to src.fp.o to get the permissions to sync.

Metadata Update from @ryanlerch:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Thanks.

@ryanlerch will members of the FAS group automatically be added to the mailing list or do we need to manage that?

@ryanlerch will members of the FAS group automatically be added to the mailing list or do we need to manage that?

Sadly, no -- you will need to manage the users of the mailing list as per normal. AUIU, the main role of this mailing list is to be the user for the bugzilla account (and has to remain private as, in theory, security issues may be filed against it)

Metadata