Vincent Bernat <ber...@debian.org> writes: > Russ Allbery <r...@debian.org> disait:
>> Well, I'm personally not directly involved with Python development, but >> it seems like a lot of people are upset with the way that the python >> package is being maintained. We do have a procedure for this: it falls >> under the jurisdiction of the Debian Technical Committee. If there is >> a group of people who believe they would be better able to maintain the >> python package than the current maintainer and are willing to assemble >> a team and propose themselves as the maintainers, that's certainly >> something that can be appealed to the Debian Technical Committee for >> discussion. > Some respectable people keep telling us that the problem is handled and > the solution will come soon. Going to the technical committee may be > seen at confrontational against them, I think. Eh, I'd hope not. We're pretty good at not doing anything when that seems to be the best choice of action, and we're identifiable people with delegated project authority who can be contacted in private if for some reason information absolutely must be shared in private. Other than a formal appeal being viewed as escalation, which is a risk, I'm not sure that this would make the situation any worse. I would hope that any third-party mediators wouldn't take it as an affront. One of the advantages of the TC process is that it inherently requires that something constructive be proposed. One can't simply present a problem; one has to propose a solution at the same time so that the TC can make a decision. This can be marvelously clarifying. Often as soon as one starts thinking about a problem from that angle, a lot of the uncertainy falls away and the choices reduce to a manageable set of options with clearer tradeoffs. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- 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/87lje27ybr....@windlord.stanford.edu