It would be nice, if there is email alias similar to <package>-owner@fedoraproject.org allowing to contact EPEL maintainers. More details and reasoning is available in infrastructure ML thread [1].
<package>-owner@fedoraproject.org
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: groomed, low-trouble, medium-gain
One question to answer before we can work on this is: who do we include behind this alias?
Should it be just the POC set for epel for the package?
Metadata Update from @pingou: - Issue tagged with: dev
Could we do:
If there are bugzilla overrides for epel on the package, just include those
If there are not bugzilla overrides make it the same as -maintainer ?
+1 to @kevin proposal. For me as a casual user, there is not better way to know the information other the checking the pagure UI. And as somebody not interested in EPEL, I'd be happy to not receive any EPEL notifications if there is somebody designated as EPEL maintainer.
For me as a casual user, there is not better way to know the information other the checking the pagure UI.
We could add this to the fedora packages page. @fnux has already put the x-owner@fedoraproject.org alias on fedora-packages-static.
x-owner@fedoraproject.org
Will look into this, see the source for the script in https://pagure.io/fedora-infra/ansible/blob/main/f/roles/packager_alias
Metadata Update from @asaleh: - Issue assigned to asaleh
Finaly got around to it: https://pagure.io/fedora-infra/ansible/pull-request/608
@vondruch does that work for your use case(es) ?
Do I understand correctly that the PR implement the following aliases?
package-mainainers - This reach everybody package-mainainers-fedora - This reach just Fedora maintainers package-mainainers-epel - This reach just EPEL maintainers
If that is the case, then it sounds perfect :thumbsup:
yes, that is the plan :) Just mergeg, now off ot do the update.
Is this live? I did run the bastion playbook, but it doesn't seem to be making the epel aliases... (but I haven't dug into it much)
It is live and updating fine.
I'll send an announcement that it's done! :)
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.