Stefano Zacchiroli <firstname.lastname@example.org> writes:
> If the CTTE agrees, I will proceed as follow. I will propose, at my
> discretion, a maintenance team that I hope could be accepted by all
> involved parties. I'll ask for extra volunteers and for (motivated)
> objections, trying to mediate in the discussion and reaching
> consensus. All discussions will be public and happen on the
> debian-python mailing list. Ultimately, I'll make a judgement call and
> decide. People will be free to override it with the mechanisms we have
> in place for that.
I think, and have for some time, that the ideal situation would be a
maintenance team that includes Matthias (assuming that Matthias still
cares deeply about the Python packaging and wants to continue to
participate). If such a team could be found that would work well, it
would allow us to continue to make use of Matthias's passion for the work
while hopefully having a team that can fill in for and make up for the
shortfalls in skills and abilities of all the members, particularly
including communication and public planning.
The problem that I have with the curent situation is that kicking Matthias
to the curb seems to be a requirement for a resolution, and that makes me
really uncomfortable. I'm not, to note, saying I'm flatly opposed to
that, just that it makes me really uncomfortable and isn't something I
want to advocate given the information that's available to date.
For a maintainer team to work, though, just to be clear, it would need to
be a team of equals, not people who are just interpreting Matthias for
other people without the ability to make independent decisions.
I'm not sure delegating the decision is a good idea, but if you (or anyone
else) could come up with such a team, I think it would be a slam duck
solution to this, and I doubt there'd be much difficulty in getting CTTE
approval (assuming that it was even required, since if Matthias is happy
with the result, there's no need for the CTTE to take formal action).
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>