[15133] in athena10
moving config-package-dev to GitHub (or elsewhere)
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Wed Oct 11 22:47:24 2017
Date: Wed, 11 Oct 2017 22:47:12 -0400 (EDT)
From: Geoffrey Thomas <geofft@ldpreload.com>
To: debathena@mit.edu
Message-ID: <alpine.DEB.2.11.1710112211580.16375@titan.ldpreload.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
I think we should move config-package-dev to somewhere that's more
friendly for people to send patches to than
git://debathena.mit.edu/config-package-dev.git and more friendly to browse
than the Trac browser. Is github.com/mit-athena a good place for this? Or
github.com/sipb?
If we're worried about conflicts with Debathena backports or something if
we use mit-athena, I'm more than happy to find some branch-naming scheme
that will let "upstream" and "Debathena" config-package-dev not conflict
with each other (probably using debian/master instead of master, per
DEP-14).
I don't think I am too concerned about too many people having push access,
since what really matters is upload access to the Debian package.
Or somewhere else? I'm also fine with making a new GitHub or GitLab org
for config-package-dev.
--
Geoffrey Thomas
https://ldpreload.com
geofft@ldpreload.com
