[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#573745: Please decide on Python interpreter packages maintainership



* Bdale Garbee (bdale@gag.com) [100318 00:00]:
> I'm adding the DPL to this reply because it seems possible that the only
> way to achieve this objective might be an in-person Debian Python Summit
> meeting, moderated by members of the TC, where we can work through all
> the issues and come to consensus.  Perhaps we can resolve our problems
> by email and/or IRC, but the mere existence of this petition to the TC
> and what it implies about communication disconnects makes me doubt that. 

I agree. I tried to get one such meeting done some time ago (see
below). I can understand if people are so frustrated now that they
escalate to the tech ctte. However, at least at this time I don't
think I'll vote for a new maintainer (team) if we didn't at least try
to resolve the basic issues before.


Andi


From: Andreas Barth
To: doko, joss, zack, bzed, piotr, dktrkranz, scottk
Cc: leader, release team
Subject: status of python / face2face-meeting?
Date: Sun, 27 Sep 2009 13:32:47 +0200
Message-ID: <20090927113247.GH9745@mails.so.argh.org>
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.5.18 (2008-05-17)

[ mail adresses removed -- Andi, 18.3.2010 ]
[ second sidenote - the recipient list of the mail is not necessarily
complete - please feel free to suggest additional recipients, I'm happy to
include more people ]
                                                                                                                                                                                                            Hi,
                                                                                                                                                                                                            as part of the recent release mails, we got some - well, "complaints" is
the wrong word, but definitly in that direction - mails about python2.6 (or
rather its inexistence in unstable). Also there doesn't seem to be a
common mindset how to place files etc etc, see e.g.
http://bugs.debian.org/474630 (this is an example, not a "there needs to be
some action now").

As you might know, I'm not a member of the Debian Python Community, but I'm
a member of the Release Community, and I'm a frequent python user/code writer
(actually the language of my choice for many tasks). For this reason, it
might be that I didn't pick up all the necessary/recommended people for
this mail - sorry if I have, I don't want to step up on anybodys toes.

>From my discussions on IRC, I have the impression that all involved people
are unhappy with the current situation, that there are still some issues
lingering around for quite some time, and this combination makes it
impossible to resolve the (real) issues we have.

On the other hand, it seems to me that overall python packaging has
progressed in Debian quite much since I last looked at it, and I think we
should try to build up on our experiences since 2006.


For this reason, I'm proposing to meet us all for a weekend in real, and
try to get the root issues resolved then and there. This of course means
getting an agenda in time before the meeting. This also means that we
definitly need to meet us on Friday evening latest so that we have really
the full Saturday to understand the reasons people have for their wishes
and needs. Also, we need to have at least half of Sunday available, so that
we can re-consider our ideas over night, and don't need to make decisions
in a rush. In case we are going to do that, I'd look if I can get some
Debian-friendly "upstream" person who is not involved yet for a second
opinion.

If I should follow on that, please tell me. I already spoke with Steve, we
can use Debian ressources (i.e. money) for that. (If you think this
wouldn't help please say as well - that'd save us all the effort of the
meeting.)


Cheers,
Andi



Reply to: