Re: On unresponsive maintainers (was: Re: On using magicfilter and gs)

On Dec 01 2004, s. keeling wrote: > A couple of them have replied to mine, mentioning that woody's old as > dirt, and they're up to their eyeballs trying to bring sarge to > stable. 'Sounds like a fairly reasonable excuse to me. I don't > begrudge them that. But the fact is that I *am* using tes

Re: On unresponsive maintainers (was: Re: On using magicfilter and gs)

Incoming from Rogério Brito: > On Nov 27 2004, Michael D. Crawford wrote: > > I don't know anything about the packages in question or their maintainer, > > but if he's really being unresponsive, somebody should look into it in a > > serious way. > > Actually, I think that there are quite a lot of

Re: On unresponsive maintainers (was: Re: On using magicfilter and gs)

RogÃrio Brito <[EMAIL PROTECTED]> writes: > Anyway, I have already merged some bugs on the BTS, but I myself can't do > much. I would invite other users to help with this. Perhaps this way the > bug count will drop and the maintainers will give up maintaining their > packages, leaving room for som

Re: On unresponsive maintainers (was: Re: On using magicfilter and gs)

On Nov 27 2004, Michael D. Crawford wrote: > I don't know anything about the packages in question or their maintainer, > but if he's really being unresponsive, somebody should look into it in a > serious way. Actually, I think that there are quite a lot of maintainers being unresponsive to users's

Re: On unresponsive maintainers (was: Re: On using magicfilter and gs)

Michael D. Crawford wrote: Is there any formal requirement that a maintainer be responsive, or even do his job at all? Is there a procedure for taking a package away from a maintainer, and having someone else take care of maintaining it? I don't know anything about the packages in question or t

Re: On unresponsive maintainers (was: Re: On using magicfilter and gs)

"Michael D. Crawford" <[EMAIL PROTECTED]> writes: > Is there any formal requirement that a maintainer be responsive, or even > do his job at all? No. Debian's Constitution actually states that you can't force a developer to do any work he or she doesn't want to do. > Is there a procedure for ta

Re: On unresponsive maintainers (was: Re: On using magicfilter and gs)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Nov 27, 2004 at 09:50:32PM -0400, Michael D. Crawford wrote: > Is there any formal requirement that a maintainer be responsive, or even do > his job at all? > > Is there a procedure for taking a package away from a maintainer, and > having s

Re: On unresponsive maintainers

See section 7.4 in -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: On unresponsive maintainers (was: Re: On using magicfilter and gs)

Is there any formal requirement that a maintainer be responsive, or even do his job at all? Is there a procedure for taking a package away from a maintainer, and having someone else take care of maintaining it? I don't know anything about the packages in question or their maintainer, but if he

On unresponsive maintainers (was: Re: On using magicfilter and gs)

On Nov 25 2004, Anthony Campbell wrote: > On 25 Nov 2004, Rogério Brito wrote: > > And while I am at it, it seems that this maintainer is a little bit > > unresponsive, since the other bug that I filed had the same destination, > > apparently (/dev/null): > > > > http://bugs.debian.org/cgi-bin/bug