As I was writing examples for requesting EPEL packages, the wording of the Stalled EPEL Requests policy was bothering me. I have created a pull request to clarify a stalled request.
It's not really a change in policy, just clarifying what I think we meant.
-* A week goes by with no response
+* A week goes by with no action
+"Action" is considered something that progresses the bug.
+"Action" can be positive or negative. Such as a response of "The code
+has not been updated for 10 years and has security issues" and then they
+close the ticket.
+"No Action" could be no response at all, or it could be a response of
+"I do not want to do epel" and then they do nothing else.
+* A week goes by with no action
+"Action" is considered something that progresses the bug.
+"Action" can be positive or negative. Such as a response of "The code
+has not been updated for 10 years and has security issues" and then they
+close the ticket.
+"No Action" could be no response at all, or it could be a response of
+"I do not want to do epel" and then they do nothing else.
Let me know what people think.
Troy
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
