* Russ Allbery <r...@debian.org>, 2012-04-27, 20:20:
Stefano Zacchiroli <lea...@debian.org> writes:
[...]
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
Did Matthias even express his willingness to collaborate with 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.
How so? TTBOMK Barry is not a maintainer of any Python interpreter
package.
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.
[...]
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'm confused. Those "teams" are not only distinct but also disjoint.
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.
I don't find it difficult at all. If, for example:
1) ctte believed that Matthias cannot keeping his maintainer position no
matter what, and
2) both jwilk and ctte believed that the [jwilk] team is strictly better
than the [morph] team,
it would be bizarre to choose [morph] rather than [jwilk] just because
jwilk prefers status quo.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
