Re: Bug#573745: Please decide on Python interpreter packages maintainership
Hello Michael,
On Sat, May 12, 2012 at 3:34 AM, Michael Gilbert <mgilbert@debian.org> wrote:
> I wonder if the core issue at hand here is simply that the python VCSs
> are on a resource writable by only one person (meaning no one else can
> contribute)? See:
> https://code.launchpad.net/~doko/python/pkg2.7-debian
> https://code.launchpad.net/~doko/python/pkg3.2-debian
It's not (or not only), at least not for me, but it states quite
clearly the level of collaboration he expects from other fellow DDs -
none.
> If that's the case, then perhaps a simple voteable option would be a
> request to re-home the VCS somewhere that can support multiple
> contributors (possibly stating preferably on a Debian resource like
> alioth)?
sadly a shared/writable VCS doesn't make a team, when someone doesn't
play team. I don't know what TC thinks about adding that option, maybe
it might be merged in a "soft" option (proposing a shared workflow
with shared tools).
> Perhaps, the alternative team could start the alioth VCS on their own
> anyway, and use that to sort of NMU maintain the package (while it
> appears to be somewhat ignored now). Sort of like we're doing for
> wine:
> http://lists.alioth.debian.org/pipermail/pkg-wine-party/2012-May/thread.html
We could have done that, but we thought that appealing to TC would
have been the right way to resolve the issue.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Reply to: