I would like to request a formal guideline/policy be put into place for how to handle old/broken/vulnerable packages that need fixing by the EPEL Wranglers group. This will allow for a specific order of operations be followed and current package maintainers who may have an EPEL Wranger step in to fix their package on their behalf will know why as per the guideline/policy.
I think we can close this?
Metadata Update from @gotmax23: - Issue close_status updated to: None
I believe so.
I don't think EPEL Wranglers is a thing anymore. I'm actually not even sure what its exact purpose was. My guess is that the EPEL Packagers SIG more or less replaces it.
Another thing to consider is that this issue predates pull requests for packages (pagure over dist-git). Now anyone can propose a change to an EPEL package via pull request, and in an emergency a Proven Packager can merge such a pull request. That seems like the logical evolution of the "step in to fix their package" workflow.
If I'm missing anything here @maxamillion (especially any gaps you think we might have in the current policies/guidelines), please open a new issue.
Metadata Update from @carlwgeorge: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.