Re: Mechanism for removing developers
Le Thu, Jan 28, 1999 at 09:13:04AM -0600, John Goerzen écrivait:
> Again, as I said in my message, I'm not proposing removing developers that
> maintain packages with bugs, or packages with very old bugs. This case is
> different. The developer has literally *ignored* bugs for over 700 or 800
> days, depending on the bug. That's right -- no response to the submittor.
Are you sure the developer still receive the bugs ? Are you sure the
developer is still in Debian ?
But it's the same for other packages, dpkg-ftp for example was maintained
by Klee Dienes and he did the same. But that's not the problem, in this
case the problem is that Klee has left the project without orphaning his
packages. I say "he left" because I was not able to join him by mail.
> have been developers maintaining packages with release-critical bugs during
> a freeze but have not even made any effort to fix them (I would be satisfied
> by an effort of saying "I can't fix this, can anyone help?" to debian-devel)
The list of important/grave/critical bugs is public, why should one
announce it ? Of course it's probably better to ask for help, but
I don't see it as an obligation.
> What you are talking about and what I am talking about are two different
> things.
I'm not sure... the solution to your problem is certainly not to remove the
developer but to orphan a package that a maintainer is not able to maintain.
But it's difficult to define what is good maintaining and what is not.
But if you look at a recent changelog, Vincent R. did an NMU of a
package which orphaned the package (with the permission of the maintainer).
You probably should try something similar, ask the maintainer if he *really*
still want to maintain that package. If not then orphan it.
Cheers,
--
Raphaël Hertzog >> 0C4CABF1 >> http://prope.insa-lyon.fr/~rhertzog/
Reply to: