Bug#573745: Please decide on Python interpreter packages maintainership

2012-04-27 Thread Stefano Zacchiroli
On Tue, Mar 20, 2012 at 02:46:58PM -0700, Russ Allbery wrote:
 Stefano Zacchiroli lea...@debian.org writes:
  If the Technical Committee welcome that, I'll be happy to take the
  burden of verifying (publicly, and on -python) who would be willing, at
  present, to be part of an alternative Python maintenance team.
 
 Personally, I would be much more comfortable with that than any of the
 delegate the decision to other people options.  I think that would also
 make the vote somewhat more concrete so that the TC can consider a
 fully-formed alternative.
 
 I don't speak for the TC, but I personally would appreciate that.

Not having heard other options, I've proceed with the verification
mentioned above. Everything has happened publicly and is hence available
for your review starting from [1].  My own conclusions on the potential
teams, based on that thread have been posted on list [2] and also
attached to this mail for your convenience.

According to the thread, the amount of volunteers willing to help has
changed but not diminished, although it seems to be more scattered now.

To conclude, let me remind that the purpose of this exercise was only to
verify the availability of the team that volunteered 2 years ago, in
order to give more data to the tech-ctte for deciding what team (if any)
should go in the vote ballots.

I hope this could help and that the tech-ctte have now all the input
needed to quickly come to a conclusion on this issue, one way or
another.

Good luck!

[1] https://lists.debian.org/debian-python/2012/04/msg8.html
[2] https://lists.debian.org/debian-python/2012/04/msg00101.html
-- 
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 »
---BeginMessage---
On Tue, Apr 03, 2012 at 10:36:58AM +0200, Stefano Zacchiroli wrote:
 Allow me be blunt then: do we have volunteers to maintain the pythonX.Y
 packages? Can those volunteers manifest themselves on this list?
snip
 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 :)

3 weeks into this, it seems we have reached a peek in the amount of
people who volunteer to maintain pythonX.Y. I've go not more candidacy
in private mail than what you saw on list, which is a good sign.

Considering the potential incompatibilities, it seems that the possible
maintenance teams boil down to:

- a maintenance team formed by Sandro
- a maintenance team formed by Matthias and Barry
- a maintenance team formed by Jakub

Then there is the availability to help by Luca to do grunt work, with
no strong requirement of doing so as a declared co-maintainer.

It should also be noted that Jakub, in spite of his availability, has
made clear that he does not support removing the current maintainer by
the means of a tech-ctte vote.  Barry clarified in mail to me (asking me
to mention it here) that he does not support removing the current
maintainer either, which is why I've listed Barry in co-maintenance with
Matthias, but not with Sandro.

Having not heard from Matthias either, I had to pick some defaults for
his conflicts, which I'll be happy to refine as soon as he comments on
this (but quite frankly, I don't see that coming). I've assumed he would
be fine working with Barry, and that he would not be fine working with
Sandro. The rationale is a simple principle: I have witnessed in the
past conflicts between Matthias and Sandro, but no conflicts between
Matthias and Barry. It seems fair to assume that the status quo
(positive or negative) continues, until the contrary is proven.

If there are no further comments or candidacies, I'll proceed forwarding
the above possibilities to the tech-ctte, Cc:-ing this list, before the
end of the week.

I recall that the purpose of this exercise was simply to do a reality
check of the team who 2 years ago volunteered in the tech-ctte buglog.
No endorsement of any of the tech-ctte option is implied in the results
of the exercise.

Cheers.
-- 
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 »


signature.asc
Description: Digital signature
---End Message---


signature.asc
Description: Digital signature


Bug#573745: Please decide on Python interpreter packages maintainership

2012-04-27 Thread Russ Allbery
Stefano Zacchiroli lea...@debian.org writes:

 Not having heard other options, I've proceed with the verification
 mentioned above. Everything has happened publicly and is hence available
 for your review starting from [1].  My own conclusions on the potential
 teams, based on that thread have been posted on list [2] and also
 attached to this mail for your convenience.

 According to the thread, the amount of volunteers willing to help has
 changed but not diminished, although it seems to be more scattered now.

This was very helpful.  Thank you!

 To conclude, let me remind that the purpose of this exercise was only to
 verify the availability of the team that volunteered 2 years ago, in
 order to give more data to the tech-ctte for deciding what team (if any)
 should go in the vote ballots.

 I hope this could help and that the tech-ctte have now all the input
 needed to quickly come to a conclusion on this issue, one way or
 another.

[...]

 Considering the potential incompatibilities, it seems that the possible
 maintenance teams boil down to:

 - a maintenance team formed by Sandro
 - a maintenance team formed by Matthias and Barry
 - a maintenance team formed by Jakub

So, for moving forward with this, these seem like three obvious voting
options to me.  I will assume that the Matthias and Barry team would be
the decline to change anything option.

 It should also be noted that Jakub, in spite of his availability, has
 made clear that he does not support removing the current maintainer by
 the means of a tech-ctte vote.  Barry clarified in mail to me (asking me
 to mention it here) that he does not support removing the current
 maintainer either, which is why I've listed Barry in co-maintenance with
 Matthias, but not with Sandro.

This does, to me, raise the question of whether Jakub should be listed as
a separate option, or whether there's no meaningful distinction between a
maintenance team formed by Jakub and a maintenance team formed by Matthias
and Barry.  I suppose they're distinct in the sense that the tech-ctte
could decide that Matthias should not have a position of authority over
the package at all, but that doesn't seem particularly sensible to me in
that it's rather difficult for us to make it stick going forward while
still appointing someone who doesn't think that Matthias should be
replaced.

(Also, why is Jakub listed as a separate option but not Barry?)

-- 
Russ Allbery (r...@debian.org)   http://www.eyrie.org/~eagle/



-- 
To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ty0435ku@windlord.stanford.edu