new non-responsive maintainer policy
A new non-responsive maintainer policy has been approved [1]. This announcement is a bit late because it took a while to update the documentation and add all the necessary templates in bugzilla. The new policy is at [2] (diff [3]). tl;dr: When a maintainer is not responding to bug reports, to start the non-responsive maintainer process, and either orphan or take over the package, module, or container, open a bug in bugzilla using one of the templates linked in the policy document, and send a query to fedora-devel, and later open a bug in the FESCo issue tracker. Assuming FESCo approves, the reporter gets commit access to the package after about a week, and full reassignment or orphaning happens after 4 weeks. 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. [1] https://pagure.io/fesco/issue/2149#comment-581834 [2] https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ [3] diff: https://pagure.io/fesco/fesco-docs/pull-request/15#request_diff Please see the document at [2] for all the details. Zbyszek (on behalf of FESCo) ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-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-announce@lists.fedoraproject.org
Re: new non-responsive maintainer policy
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
Re: new non-responsive maintainer policy
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? Thanks, Richar ___ 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
new non-responsive maintainer policy
A new non-responsive maintainer policy has been approved [1]. This announcement is a bit late because it took a while to update the documentation and add all the necessary templates in bugzilla. The new policy is at [2] (diff [3]). tl;dr: When a maintainer is not responding to bug reports, to start the non-responsive maintainer process, and either orphan or take over the package, module, or container, open a bug in bugzilla using one of the templates linked in the policy document, and send a query to fedora-devel, and later open a bug in the FESCo issue tracker. Assuming FESCo approves, the reporter gets commit access to the package after about a week, and full reassignment or orphaning happens after 4 weeks. 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. [1] https://pagure.io/fesco/issue/2149#comment-581834 [2] https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ [3] diff: https://pagure.io/fesco/fesco-docs/pull-request/15#request_diff Please see the document at [2] for all the details. Zbyszek (on behalf of FESCo) ___ 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
