[15134] in athena10
Re: moving config-package-dev to GitHub (or elsewhere)
daemon@ATHENA.MIT.EDU (jdreed@gmail.com)
Wed Oct 11 23:01:16 2017
Content-Type: text/plain;
charset=us-ascii
Mime-Version: 1.0 (1.0)
From: jdreed@gmail.com
In-Reply-To: <alpine.DEB.2.11.1710112211580.16375@titan.ldpreload.com>
Date: Wed, 11 Oct 2017 23:01:08 -0400
Cc: debathena@mit.edu
Message-Id: <43042C95-9CC5-4744-A303-2BB4B2230B6A@gmail.com>
To: Geoffrey Thomas <geofft@ldpreload.com>
Content-Transfer-Encoding: 8bit
+1
> On Oct 11, 2017, at 10:47 PM, Geoffrey Thomas <geofft@ldpreload.com> wrote:
>
> 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
