Dear all, Over the past months FESCo has been considering my proposal to have a lighter weight process to get needed changes for Fedora packages (whether getting a PR merged and built, or a package branched, etc.) - since the alternatives up to now is just pinging a PR or bugzilla issue, or escalating and getting the maintainer declared non responsive.
We think we have a suggested process that would work well - thank you to everyone in the committee for their inputs - but would like to get community feedback on this, since we’re only human and there might be something we miss. Hopefully this balances out the need to get fixes in, with not bypassing maintainers’ concerns (or surprising them with a fait accompli if they’re on vacation, busy at a conference, etc.). But please chime in and let us know of any improvement we can make to this before it lands. https://pagure.io/fesco/fesco-docs/pull-request/94 This is also cross-posted to Discourse: https://discussion.fedoraproject.org/t/rfc-lightweight-stalled-request-process/148733 Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 README: https://fedoraproject.org/wiki/User:Salimma#README
signature.asc
Description: This is a digitally signed message part
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
