If you like we can do a bit better than that...

We can make a freeipa-sig 'team' fas group. Anyone added to the group will get commit to the packages with it as point of contact and its email in fas will sending all the commits and bugs to the list.

I am not sure I understand how the sig FAS group would work in our case. We already have a commit group to FreeIPA git, which does not necessarily need to contain the same people as the Bugzilla response team. So all we need to solve is just the default Bugzilla contact actually.

Sure we can do the old way too I think.

The new way is for managing commits to the fedora packages, not git.

Ie, if you have 10 packages and freeipa-sig is point of contact for them and you add a new maintainer, you just add them to the freeipa-sig fas group and they can commit to the fedora branches instead of having to add them for commit acls to each one of the 10 packages.

Ah, I see. But for current FreeIPA this is not required as it is just a single package. But I will keep that possibility surely in mind - thanks.

Sorry for the long delay here. ;(

I have created the account.

Next steps:

• You want the freeipa package set to ipa-maint as point of contact? Any other packages?

• I haven't made the bugzilla account, can you do so? Note that it will send the activation emails to the list, so you should set it to moderate everything until you can look at those emails and activate the bugzilla account. You will then have to make sure it's allowed to post.

Thanks!

Replying to [comment:5 kevin]:

• You want the freeipa package set to ipa-maint as point of contact? Any other packages?

Only "freeipa" package for now, current main maintainer is CCed.

• I haven't made the bugzilla account, can you do so? Note that it will send the activation emails to the list, so you should set it to moderate everything until you can look at those emails and activate the bugzilla account. You will then have to make sure it's allowed to post.

This is already done - ipa-maint is the main point of contact for "ipa" RHEL bugs already - see for example [https://bugzilla.redhat.com/show_bug.cgi?id=1149124 Bug 1149124].

Point of contact should be set now.

Please let us know if you need anything further.

Thanks kevin! Just checking, is it ok that the new ''ipa-maint'' user is not visible on https://admin.fedoraproject.org/pkgdb/packager/ipa-maint/ ? libvirt-main user is, so I wanted to check that everything is set properly.

https://admin.fedoraproject.org/pkgdb/packager/ipa-maint/
That's likely something in pkgdb, I'll take a look

Got it, that's because libvirt-maint has ACLs while ipa-maint does not have any

Giving ipa-maint watch* ACL should fix this

Ok, thanks for info. I personally do not care much, it is more a question to you and what are your expectations of such service accounts.

I just gave ipa-maint wathcommit on all branches so that it shows up as packager.

Note: the difference between ipa-maint and libvirt-maint is that ipa-maint is the first pseudo user we're creating with pkgdb2. libvirt-maint has been transferred from pkgdb1.
And to be honest, I didn't quite consider the pseudo-user when building pkgdb2 (my mistake), I thought the FAS groups would take them over.