[Python-apps-team] Bug#708573: trac-accountmanager: Please remove Python Applications Packaging Team as maintainer

[Thomas Kluyver]

On 17 May 2013 17:52, Daniel Kahn Gillmor <dkg at fifthhorseman.net> wrote:

> > We've been through this a number of times for both PAPT and DPMT.  We
> want a
> > common repository for each team (not split between different VCSs).
>  There's
> > been discussion about what would be needed to migrate from SVN to
> something
> > else and about what work would need to be done to do that.  So far no
> one has
> > done the work.
>
> Perhaps this should be documented someplace so that when it comes up in
> the future, there is a clear document to refer to.  I haven't heard any
> of these discussions, and i don't know where they took place or who took
> part in them.  sorry for my ignorance!
>

This came up recently on debian-python. It's a very long thread, but the
basic outcome was that, while quite a few people wanted to move away from
svn, there was very little consensus on which VCS to migrate to, whether to
include full source tarballs, and how to do any migration. It was suggested
that if someone was willing to put the time in to drive a migration, that
might be OK, but by then the discussion had pretty much killed all
enthusiasm for it.

My memory is that there was also disagreement over whether the team could
live with packages split across two difference VCSs. Some people argued
that the teams packages should be unified, others that a migration would be
easier if it didn't need to be all-at-once. Some other packaging teams
(e.g. Games) do have packages in two VCSs.

Here's the start of that thread, if you've got time to read through it all:
http://lists.debian.org/debian-python/2013/02/msg00032.html

Best wishes,
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/python-apps-team/attachments/20130517/2a5b9f53/attachment.html>