Bug#573745: Please decide on Python interpreter packages maintainership
* Russ Allbery (rra@debian.org) [120319 06:00]:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573745#335
>
> B. The Technical Committee have been petitioned to decide on the
> maintainership of the python packes. We agree with the substance of
> the complaint, but do not feel able to directly select the replacement
> maintainers. Therefore:
>
> We declare that the python packages (full list below) are now orphaned,
> exercising our power in s2 of the Constitution.
>
> Please would those interested in taking over Python maintenance form an
> appropriate team and take over the package. If competing teams should
> come forward, the package should be taken over by the largest.
> C. The Technical Committee exercises our power under 6.1.2 of the
> Constitution to remove the current maintainer of the Python interpretor
> packages. It delegates the task of choosing a new maintenance team for
> the Python packages to the DPL.
I don't think orphaning makes sense, unless we know for sure that a
better (in whatever terms) group of people picks the packages up. And
I somehow doubt it makes sense.
How about:
BC. The Technical Committee have been petitioned to decide on the
maintainership of the python packes. We agree with the substance of
the complaint, but do not feel able to directly select the replacement
maintainers. Therefore:
We require the current python package manager to hand over the
package to a team of at least three maintainers (where he may be
one of the maintainers but without veto power) who are actually
active within the debian python community. This needs to be done
latest 6 weeks after the vote has ended. Failing that, the
Tech Ctte exercises our power under 6.1.2 of the Constitution to
remove the current maintainer of the Python interpretor packages.
It delegates the task of choosing a new maintenance team for the
Python packages to the DPL.
Andi
Reply to: