#9345 Requesting group and mailing lists for EPEL Packagers SIG
Closed: Fixed 3 years ago by smooge. Opened 3 years ago by salimma.

Describe what you would like us to do:


Per discussions in the EPEL Steering Committee meeting:
https://meetbot.fedoraproject.org/teams/epel/epel.2020-09-18-21.00.log.html - timestamp 21:53:30

and on the mailing list
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/KICNW4ZY6QFUOC6G2ETKRJCE4QRCN4IH/

Can we have the following created?

  • epel-packagers-sig FAS group
  • epel-packagers-sig@ mailing list (for getting Bugzilla emails)

Discussions will happen in epel-devel@ so we don't need a separate mailing list for it.

This will be a reboot of the old proposed epel-wranglers; no one is aware of any infra automation that has been done for epel-wranglers that we can reuse, so it's probably best to start from scratch (also SIGs currently has to follow the *-sig naming convention, as far as we know).

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


2020/09/30


Here are the current groups for EPEL

epel-cabal  EPEL    tracking    cla_done    Approved
epelproject EPEL SCM    tracking    cla_done    Approved
epel-releng EPEL Release Engineering Group  shell   None    
epel-wranglers  EPEL Developers tracking    cla_done    Approved
gitepel Git group for fedorahosted page git cla_done    

I am not sure if any of them can be re-used. If not that is fine. The current mailing lists are:

epel-announce.lists.fedoraproject.org               
epel-devel.lists.fedoraproject.org                  
epel-package-announce.lists.fedoraproject.org       
epel-users.lists.fedoraproject.org

EPEL users is closed for archive versions so I think a epel-packagers-sig should be made.

From what I hear, epel-cabal predates epel-wranglers and was meant to be a similar effort; not sure what epelproject and epel-releng are for (or gitepel).

Anything that (a) makes it easier for infra, and (b) is the least confusing for users and developers would be fine. Most newer SIGs do seem to have FAS groups ending in -sig.

I wonder if we can delete some of the older groups if unused, but that's a separate discussion.

Groups like users can't be deleted... so I can remove people from those groups etc

Looks like I created epel-cabal on 2019-08-23 15:47:42.250972+00:00 and I created epel-wranglers on 2014-09-19 21:13:04.837110+00:00

Once I figure out if I need this to be a tracking group or something else I will create epel-packagers-sig with the correct perms.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

3 years ago

Once I figure out if I need this to be a tracking group or something else I will create epel-packagers-sig with the correct perms.

We used to make the dist-git group be of the type "pkgdb" but pagure no longer enforces that, we try to stick with it for consistency but that's it. There is no technical blocker in re-using an existing group.

Group has been created.

List has been created. You have been made the owner/admin for both.,

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

3 years ago

Thanks! Will set them up once devconf is over

@kevin added it to src.fedoraproject.org and I've set up Bugzilla, so everything now works.

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Done