Hi all, I'll reply to all emails here, just to not spam that much the list.
On Mon, Jul 5, 2010 at 14:44, Ian Jackson <[email protected]> wrote: > Sandro Tosi writes ("Re: Bug#573745: Please decide on Python interpreter > packages maintainership"): >> Also, an additional level of "management" has to be well received from >> who has to be managed: are we really sure Matthias will follow even >> controversial decisions (so in opposition to some of his ideas) the >> core team will take? > > I don't think we are considering adding an additional layer of > management. Currently the person in charge is Matthias; he is the > maintainer of python2.6 et al.[1] > > We would hand the maintainership of these packages to the new team. Aaah, now I see: I completely mis-interpreted the proposal before. > Ian. > > [1] What is the exact list of packages in question ? I make it as > follows. Core Python packages: [8<] I'd just add python2.7. > Python extensions and libraries: [8<] I don't think they are part of this appeal; of course I (at least) have asked several times to inject this modules/extensions in the DPMT repo, and only once I got a "maybe" as reply... I still welcome that, but personally I won't add them in any resolution. On Mon, Jul 5, 2010 at 19:04, Andreas Barth <[email protected]> wrote: >> We still don't have a new team. The only coherent team that has been >> suggested has been the four people who emailed the TC to start with. >> As they wrote: >> Luca Falavigna >> Josselin Mouette >> Sandro Tosi >> Bernd Zeimetz >> anyone else willing to help, including of course the current >> maintainer, provided the above points are met. > > I don't think that's a coherent team, at least none I would like to be > the maintainer of the python packages. I need to admit that I don't > think that either Josselin nor Bernd are capable to do that proper. I > have no strong opinion on the others yet, which also means I don't > think they should make them the maintainers. (I think if we do a > change we should be convinced it gets better.) May I ask for reasons for these rebuttals? in particular to the: > I don't think that's a coherent team, at least none I would like to be > the maintainer of the python packages. On Mon, Jul 5, 2010 at 19:13, Ian Jackson <[email protected]> wrote: > Andreas Barth writes ("Re: Bug#573745: Please decide on Python interpreter > packages maintainership"): >> * Ian Jackson ([email protected]) [100705 15:02]: >> > I wrote: >> > > I don't think we are considering adding an additional layer of >> > > management. Currently the person in charge is Matthias; he is the >> > > maintainer of python2.6 et al.[1] >> >> Plus Scott Kitterman and Piotr O?arowski. > > I was looking at the Maintainer field of the packages in unstable. > I'd be happy to add Scott and Piotr to my list. FWIW, I'd be happy to if they are in. On Mon, Jul 5, 2010 at 19:23, Andreas Barth <[email protected]> wrote: > * Ian Jackson ([email protected]) [100705 19:13]: >> I think ultimately what we need to do is empower the people currently >> doing most of the work. > > "Doing most of the work" is not the same as "being the loudest ones in > complaining". Honestly, I should feel quite offended by this, but I'll take none ;) Speaking for myself, I did the best I could, and in comparison a huge lot more than Matthias. > I had quite much to do with a few python-people for the recent > transition. Jakub (jwilk) did a really fantastic job there (I was next > to handing him binNMU permissions), agreed, and if he would accept, I think he'd be an important addition to the list of maintainers for python. > but also Piotr and Scott did quite > much (and are always nice and helpful). ack, of course. > The few occasions Matthias > needed to do someting it worked also quite well, at least for me. I think this is because you're wearing an official hat (even more than one), while several other a "just" contributors to Debian. > (And > once the release team had finally found an slot for python-defaults > pointing to 2.6 in unstable Matthias did an upload quite fast - as it > should be.) ah so the maintainership is reduced to a "please release a new package" button? :) what you describe it ALL that he did for the transition. I don't call it helping, I call it passive blocking it, personally I'd expect more from him: are you really fine with a "superb" maintainer not "wasting" his time in collaboration and with a debian-python environment that it's forced to do all the work because it really cares about python? I'm not, sorry. 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]
