Bug#573745: Things have changed significantly for the better

[Andreas Barth <aba@not.so.argh.org>]

* Sandro Tosi (morph@debian.org) [100705 23:28]:
> On Mon, Jul 5, 2010 at 21:46, Piotr Ożarowski <piotr@debian.org> wrote:
> > Here's my proposal:
> >
> > * Ask Barry to join Matthias (and Matthias to accept Barry) as
> 
> adding Barry (if he accepts, of course) to the maints of python would
> be a huge win...

I would be happy if we can identify things to do which everyone agrees
one. Adding Barry to pythonX.Y packages seems one of them.


> >  interpreter packages maintainer¹ (pythonX.Y packages) and encourage
> >  both of them to find someone who cares about Debian first (so without
> >  @ubuntu.com or @canonical.com email address) - make it an requirement
> >  if bug submitters or CTTE will not be happy 3 months after releasing
> >  Squeeze (i.e. when 2.7 transition should be in advanced stage),
> 
> ...but it's not enough. Python is a delicate "beast" that I think it
> requires a group of people. (and again, as a personal idea, only
> accepting people which doko is fine with will reduce a lot the
> candidates, for sure a huge part of the most skilled ones, guess why.)

For the interpreter packages, I think some fluency with upstream is
required. Which people with that skill are there who are rejected by
Matthias? (I doubt we have too many such people anyways in Debian.)


> > Yes, I do realize that it's not possible to have a working Python
> > without these two teams co-operating... and that's the point!
> > If it will not work, we can ask CTTE for a decision about specific
> > problems (like 2.7 upload to unstable, adding a 2.7 to
> > supported, adding/dropping a patch in interpreter package, adding a
> > feature in helper tool(s), etc.)
> 
> ehm, I think that's exactly what the CTTE wants to avoid: being asked
> of any decisions like this; instead, if I got it right, they want to
> find a self-sustainable solution, that will work out by itself without
> a continue appeal to CTTE.

For questions like "when do we add $foo to supported" and "when do we
do transitions" the release team should be in the loop IMHO (but well,
see which hats I'm wearing). Looking back at the recent upload of
python-defaults, I think the release team is also in an position to
ensure things are moving forward there. 

Of course, I agree with you that the teams should be on speaking
terms. ;)


Andi