Ticket #251 (closed task: fixed)
simplify non-responsive maintainer process
|Reported by:||till||Owned by:||kevin|
The non-responsive maintainer process is very complex and therefore I want to propose a much simpler alternative.
I want to make the current procedure to become more a guideline about how many communication attempts should be made and the final procedure to become this:
1) Write a mail to fedora-devel with the problems of the package and a summary of communication attempts and open a ticket in FESCo to track all this. 2) If nobody from FESCo objects and two members agree after three days, the package can be reassigned.
This proposal focuses on easy addressing the problems caused by non-responsive maintainers, which are out of date or broken packages that nobody fixes. The Fedora community seems to be sane enough to handle these problems in a good way without the restriction to actually write several mails in a certain timeframe to make sure that nothing bad happens. And even if a package is reassigned and the original maintainer becomes responsive again, then it will probably not be a problem to reassign it to him or her. If someone really feels that this procedure may be abused in some way, then this could be address if this really happens.
The following wiki page needs to be updated: https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
There should also be an announcement be written to the fedora-devel-announcement mailinglist.
People who maintain packages for the Fedora Collection are primary affected. Also users of Fedora will experience better maintained packages. The workload on FESCo will probably increase a little, because the procedure might be used a little more.
Till Maas, Fas Account: till