On Thu, Dec 7, 2023 at 3:26 AM Michal Schorm <mschorm@xxxxxxxxxx> wrote:
I'd advise to create PR - wait week or 2,
if left without response - create BZ for the specific PR as not
everyone watches PRs and PR notifications, and wait week or two,
if left without response - send a direct mail to the package maintainer.
Any automation around a notification workflow like this would be helpful. I've been using the dist-git PR flow and find it very useful.
Once I learned how to use fedpkg to do most of the work for me (i.e. `fedpkg fork`, etc.), it usually feels like maintaining my existing packages.
Where I have felt the process lacks is automated coordination with the package maintainers.
Jonathan Steffan
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
