Hi Russ, On Tue, Jul 6, 2010 at 00:12, Russ Allbery <[email protected]> wrote: > Sandro Tosi <[email protected]> writes: >> On Mon, Jul 5, 2010 at 23:50, Russ Allbery <[email protected]> wrote: >>> Russ Allbery <[email protected]> writes: >>> >>>> I'm disturbed by the tone of some of the recent traffic which seems to >>>> imply that Matthias must either personally respond to people's e-mail >>>> or be completely removed from any role with the Python packages in >>>> order for this complaint to be satisfied. > >> well, prior than 9 months ago, he was the only one maintainer the whole >> python stack in debian, so yes, I'd except a personal reply from him >> when a python discussion is run on [email protected] or highlight on >> IRC; but that didn't happened so often, decreasing by time. > > Yes, but that's about what you expected then, when he was the sole > maintainer. I think there's general agreement in the discussion here that > Python should have some co-maintainers. > > My point is that, *given the addition of co-maintainers* (which I agree > would be important), if Matthias then wants to go heads-down on his > technical work and not engage in some or all of the debates, I'm not sure > that poses an ongoing problem provided that his co-maintainers do the > other work required to maintain the packages and he doesn't stand in their > way. And if that's the case, I don't think the requirement that he either > reply or stop being on the maintenance team is well-defended.
Ok, probably I didn't express myself clearly enough. you are talking about the future, when python will have co-maintainers (python*-default already has them), am I correct? I was referring instead to the current situation where python*-default has co-maintainers while python interpreter packages still has not. It seems to me that Matthias is still the key to make the architecture works, since he controls interpreters and co-control (horrible expression) the *-default, so without his ack (and so public discussion when needed) we are stuck. > There has been a lot of long-term bickering and heated words over Python > in Debian, and from what I've seen that's spilled over into debian-devel, > I'm very reluctant to put the weight of that problem on one party. Probably it's also my fault in hoping things would have solved by themselves and I've brought this to the CTTE too late, but please also consider I've joined the debian-python after the 2006 (and like me many others), so where all the problem origins tracks back. But the problem is still actual, I think. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
