[15135] in athena10
Re: moving config-package-dev to GitHub (or elsewhere)
daemon@ATHENA.MIT.EDU (Lizhou Sha)
Wed Oct 11 23:10:10 2017
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.11.1710112211580.16375@titan.ldpreload.com>
From: Lizhou Sha <slz@mit.edu>
Date: Wed, 11 Oct 2017 23:09:42 -0400
Message-ID: <CALGpz7_rFDkyoiOXbdYbY5TSJD4wYatcubMbFV0CL=7nPzDPwg@mail.gmail.com>
To: Geoffrey Thomas <geofft@ldpreload.com>
Cc: Debathena Trac <debathena@mit.edu>
Content-Type: text/plain; charset="UTF-8"
I think hosting it as a repo under github.com/mit-athena is great, as
the org members are all debathena-root. We can certainly work out the
technical details that makes it not conflict with Debathena's
packaging.
Best,
Lizhou
On Wed, 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
--
Lizhou Sha
Massachusetts Institute of Technology
Department of Physics
