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

pythonX.Y maintenance team

Dear all,
  I'm pretty sure tech-ctte bug #573745 does not need any introduction
on this mailing list. The recent news [1] on it is that the tech-ctte
seems to be inclined to have a vote on the matter, after having observed
that the issue is pretty "stable" now and further spontaneous evolutions
are unlikely.

Given the long time frame since bug submission, however, some things
might have changed. For one thing and according to Scott [2], the issue
seems now settled for the python*-defaults packages. As an external
observer I tend to agree with that.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573745#390
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573745#415

OTOH, the Maintainer field of the pythonX.Y packages is unchanged since
when the tech-ctte bug has been reported. While the tech-ctte has not
decided anything yet (that's what the vote will be for), they need to
decide what to put on the ballot. In particular, there are questions
about which alternative team should be put in it, for at least one of
the ballot options.

Back then, the following team has been proposed:

> - Luca Falavigna <dktrkranz@debian.org>
> - Josselin Mouette <joss@debian.org>
> - Sandro Tosi <morph@debian.org>
> - Bernd Zeimetz <bzed@debian.org>
> - anyone else willing to help, including of course the current
>   maintainer, provided the above points are met.

I'd like to help the tech-ctte in finding a team to put on the ballot
(!= finding the team who will maintain the packages, as that would be
tech-ctte decision, via vote). And I'd like to do so on this list,
because I believe that a maintenance team that does not have consensus
on this list would hardly be able to solve past issues.

Allow me be blunt then: do we have volunteers to maintain the pythonX.Y
packages? Can those volunteers manifest themselves on this list?

If you volunteered in #573745 already, and you're still available,
please reiterate your availability here. 2 years is quite a long time
and the tech-ctte should better be sure of the availability of its
members before picking a team.

I understand there might be incompatibilities that make impossible for
potential volunteers to work with other such volunteers. Nonetheless, I
suggest first to have a public volunteering round, even if you have
conditions attached to your availability. One concern at a time :)

Note that, in the absence of a team of people volunteering to maintain
the pythonX.Y packages, the tech-ctte would probably have to exclude a
"we hereby appoint $team" option from their decision ballot.

Thanks in advance for your help,
Stefano Zacchiroli     zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences   ......   http://upsilon.cc/zack   ......   . . o
Debian Project Leader    .......   @zack on identi.ca   .......    o o o
« the first rule of tautology club is the first rule of tautology club »

Attachment: signature.asc
Description: Digital signature

Reply to: