Hi,
I'd like to request to request a group for the NetworkManager maintainers. We maintain multiple packages (libnl, libnl3, NetworkManageri itself, all the VPN plugins, the applet) and would like to consistently manage the commit privileges.
Not sure what an appropriate group name would be. Perhaps "network-manager" or "network-manager-maintainers" or something like that.
The initial member list would be lkundrak (me), bgalvani, fguidici, dcbw and thaller. I guess I could propagate the group once it's create.
Thank you, Lubo
ping?
Metadata Update from @smooge: - Issue assigned to smooge
Account has been made. I have added bgalvani, dcbw and thaller but not sponsored them as you should confirm that I added the right ones. I could not find an account for fguidici
The account should be available in 30 minutes and scripts will need to be run in releng to have this group own packages.
Thank you. Is there anything I need to do in order for the releng scripts to be run?
The mailing list for the group has been created. You should get a notification to your fas email address and need to add the email addresses for the other maintainers to the list.
Created mailing list: network-manager-maint@lists.fedoraproject.org
Can you provide a list of packages that should be owned by the group?
I can then do that and we should be done.
The mailing list for the group has been created. You should get a notification to your fas email address and need to add the email addresses for the other maintainers to the list. Created mailing list: network-manager-maint @lists.fedoraproject.org
Do we need a mailing list for this? Not sure if this is something that needs to exist for a FAS group, but NetworkManager already has an upstream mailing list and existence of yet another one could potentially be confusing.
Can you provide a list of packages that should be owned by the group? I can then do that and we should be done.
Does the group needs to own the packages? The packages we maintain do have their primary contacts/admins and I think we shouldn't change that. The group should just be used to manage the commit permissions -- it shouldn't be the contact for the package or bugzilla assignee. And I think Pagure allows us to add the group to the package ourselves?
In any case the affected packages would be: libnl3, NetworkManager, NetworkManager-libreswan, NetworkManager-openvpn, NetworkManager-vpnc, NetworkManager-openconnect, wpa_supplicant, network-manager-applet.
Well, typically next we have you setup a bugzilla account that is the mailing list so bugzilla email goes to that. We want a seperate (private) list for this as it could get security bugs. The only folks on the list or allowed to read it should be the people in the group. This is how they get notification about bugs (since they are just in the group, but not directly cc'ed on the bugs)
I suppose you could just make the group an commit / watch on the packages if you wanted, it doesn't need to be point of contact/owner.
So, if you can do those two steps (make a bugzilla account with the list as account name (and make sure to moderate the list so you can catch the bugzilla activacion email), and add the group to commit on the various packages I think we are done?
Does that all make sense?
@lkundrak Is there anything further we need to do here? Or are you all set now?
I guess I'll close this and you can re-open if there's anything further you need us to do?
As far as I can tell it should be all set.
:globe_with_meridians:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.