On Thu, Sep 26, 2019 at 06:59:37AM -0500, Richard Shaw wrote: > On Thu, Sep 26, 2019 at 6:35 AM Zbigniew Jędrzejewski-Szmek < > zbys...@in.waw.pl> 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?
That's always a possibility, and a very good one at that. FESCo permission is not needed for this though: the policy explicitly allows fixes for straightforward problems: From https://fedoraproject.org/wiki/Who_is_allowed_to_modify_which_packages: > a packager doesn't fix important bugs in time, > > there are problems known that might be bad for the whole Project or > a lot of users of the repo/a particular package, > > the changes are quite minor or considered as a general cleanup to a > lot of packages, or > > the changes are part of a Fedora Objective, with a specific plan > approved by FESCo, > > then provenpackagers are allowed to fix stuff in other peoples packages. Zbyszek _______________________________________________ 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
