NOTE
Create a group coreos-sig to use for regrouping access to packages maintained by the CoreOS team in Fedora.
coreos-sig
According to https://docs.fedoraproject.org/en-US/infra/howtos/groups_in_fedora/#_how_to_request_a_group_to_be_created, this would be a pkgdb group.
Unless it's strictly needed, we don't need a new mailing list.
See: https://github.com/coreos/fedora-coreos-tracker/issues/1631
No specific deadline.
Thanks!
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
package groups have to have a private list associated with them... this list gets all the bugs for packages that group manages and could get security bugs, so it needs to be private.
Is that acceptable?
Sure, should be fine.
Gentle ping :)
Metadata Update from @kevin: - Issue assigned to kevin
Sorry for the delay here, this dropped off my radar. :(
I have:
setup a coreos-sig group in fas with you as a member and manager. setup a private coreos-sig list with you as owner. added the coreos-sig group to src.fedoraproject.org.
You now need to create a bugzilla.redhat.com account: coreos-sig@lists.fedoraproject.org It should send the activation to the list, but hit moderation and let you use that to finish setting up the account. This is needed to allow the sig to get bugs cc'ed/assigned.
Let us know if you need anything further or have any questions or issues.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.