[15137] in athena10
Re: moving config-package-dev to GitHub (or elsewhere)
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Wed Oct 11 23:53:13 2017
Date: Wed, 11 Oct 2017 23:53:01 -0400 (EDT)
From: Geoffrey Thomas <geofft@ldpreload.com>
To: Lizhou Sha <slz@mit.edu>
cc: Debathena Trac <debathena@mit.edu>
In-Reply-To: <CALGpz7_rFDkyoiOXbdYbY5TSJD4wYatcubMbFV0CL=7nPzDPwg@mail.gmail.com>
Message-ID: <alpine.DEB.2.11.1710112341330.16375@titan.ldpreload.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Hmm, are we comfortable encouraging people to make pull requests against
github.com/mit-athena/config-package-dev?
I sort of suspect that the reasonable way to do that is to have the GitHub
default branch (i.e., the remote HEAD) be debian/master instead of master,
but that probably makes everything confusing on the Debathena build side.
But if we don't do that, people visiting the GitHub repo will fork from
the wrong thing / submit PRs to the wrong branch.
(Maybe a CONTRIBUTING.md or something would help...)
--
Geoffrey Thomas
https://ldpreload.com
geofft@ldpreload.com
On Wed, 11 Oct 2017, Lizhou Sha wrote:
> 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
>
