Re: new non-responsive maintainer policy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Sep 26, 2019 at 6:35 AM Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote:

The process is streamlined to require fewer steps from the reporter
and to provide quicker access to the package.
FESCo takes care of the weekly reminders through the bug on its tracker.
It is possible to start the process without becoming the new maintainer.

Hopefully I don't have to test drive this any time but looks good on "paper". The old process was arduous enough I sometimes just didn't worry about it if I could work around the problem.

Just a thought (maybe doesn't need to be part of the official policy) but what about seeking proven packager support (or if you are a proven packager) getting FESCo permission to fix straightforward packaging problems? 

Thanks,
Richar
_______________________________________________
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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux