Non-responsive maintainer process for kurzawa / Krzysztof Kurzawski

Till Maas opensource at till.name
Fri Sep 18 16:39:29 UTC 2009


On Fri, Sep 18, 2009 at 12:03:59PM -0400, Jon Stanley wrote:
> On Sat, Sep 12, 2009 at 10:30 PM, Kevin Kofler <kevin.kofler at chello.at> wrote:
> 
> > Neither am I. Yet I do all I can to stay reachable.
> 
> Right, but even still, I don't really think that "you're not online
> for a week, you're gone!" is the right approach.  There are probably a
> good many packagers that don't check in once a week or more.  Not the
> case for you or I obviously, but I wouldn't discount that they exist.
> 
> There have been times when I'm on vacation in the middle of nowhere
> and couldn't get Internet, etc.  Do I have to orphan all my packages
> when I'm planning on being on vacation for two weeks? There are also
> times when I can get Internet but would prefer not to, etc.

The current non-responsive maintainer policy and even my proposal won't
exclude anyone from Fedora, just because he is not online. So in case a
issue cannot be handled by someone and the process is executed, then the
old maintainer can still become maintainer of their packages again
afaics. Imho it is more important to fix bugs or issues, than to make
sure that packages are only maintained by certain people. Maybe there
will be even co-maintainers after the non-responsive maintainer policy
is executed. The one who will maintain it after the procedure and the
original maintainer if he or she becomes resposive again.

Regards
Till




More information about the devel mailing list