On Mon, Nov 28, 2011 at 7:32 PM, Russ Allbery wrote: > Michael Gilbert writes: >> On Mon, Nov 28, 2011 at 5:41 PM, Alexander Wirt wrote: > >>> The question is: who decides? I have a bunch of packages and an >>> established workflow that served me well over the last years. I don't >>> want to learn another *censored* system, just because someone said its >>> the new standard or it is better. I can't remember that somebody asked >>> about deprecating well established and working tools. > >> Simple answer: the maintainer(s) of that tool. If he/she/they think it >> needs to go, then it should. > > If someone else is willing to be the maintainer of the tool (as is the > case here), I think it's a bit more complicated than that.
That isn't quite the case. The existing maintainer isn't stepping down, he's consciously deprecating the tool (and will continue to maintain it for years until the deprecation process is complete). Anyway, from what I've seen in the past the utmost deference is always been given to maintainers. If one wants to second-guess maintainer decisions, they need to appeal to the tech committee. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANTw=MO4oFzR=T6rEfJaBSZFebKKbd_EQrytznWmN1vkquu�@mail.gmail.com
