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

[Daniel Kahn Gillmor]

[dropping the bug report from the cc list]

On 05/17/2013 11:49 AM, Scott Kitterman 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!

It's hard to make an overarching, universal, and complete transition
plan without at least some pilot work being done.  Maybe my recent work
on the trac package can be helpful to the team for this kind of
consideration.

I see 199 packages in PAPT
(svn+ssh://svn.debian.org:/svn/python-apps/packages) and 616 in DPMT
(svn+ssh://svn.debian.org:/svn/python-modules/packages).

It sounds to me like PAPT is the simpler place to start.  If the
packaging is generally uniform in nature (it looks like it is from the
poking around i've done), I would be willing to write some conversion
scripts that breaks that 200-package SVN repo into 200 separate git
repositories.

I note that the svn repo only appears to contain the debian/
directories, and does not contain the upstream sources as well.  I think
it is easier to work from a revision control system that directly tracks
upstream source packages too, so part of my conversion scripts would be
to fetch the appropriate upstream files for the latest versions and
import them (unpacked) as well, along with a pristine-tar delta so that
the original tarball can be reconstructed from the git repo.

I do not currently expect to be able to import all the old upstream
tarballs for each package, so the history for the upstream tarballs
would "begin" at the present (if there are specific cases we care about,

does this sound like a reasonable workplan?  are people interested in
working on it with me?

> The shorter answer is that there are no PAPT maintained git repositories 
> because the team uses svn.

would the team be interested in using the git repositories if the above
workplan is successful?

If you're not sure how to answer because you're not sure how a converted
repository looks, feel free to take a look at
git://anonscm.debian.org/collab-maint/trac.git

Regards,

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1027 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/python-apps-team/attachments/20130517/df76a835/attachment.pgp>