[CCC DEV] Repository question
Matt Jadud
matt at jadud.com
Mon May 28 15:27:56 BST 2012
On Mon, May 21, 2012 at 5:57 AM, Adam Sampson <ats at offog.org> wrote:
> Matt Jadud <matt at jadud.com> writes:
>
>> In truth, we're not so much asking for a move to a particular place as
>> suggesting we move to a distributed version control system. We would
>> suggest either Git or Mercurial.
Hi all,
We haven't had any additional discussion on this thread for 7 days.
I'd like to know if Fred is on-board with a move. Fred: if we migrate
this repository to Github, are you OK with that?
Christian, would you be willing to do a dump and import so that
everyone can see what it would look like? This may very well become
"the" import, but my assumption is that it should be a
straight-forward process.
Cheers,
Matt
SUMMARY
=======
[ATS, CLJ, MCJ] Git is preferred for DVCS technology. No objections to Github.
[CARL] Who will create/hold the KRoC account on whichever service (and
presumably do the initial import)?
[CLJ] We currently (as of yesterday) have a "concurrency" organisation[1] on
GitHub which we are currently using for the concurrency.cc website. We
could use this organisation to host the master repository, in which
case members of that organisation would probably own the repository.
Somebody would have to do the initial import, and if nobody else is
jumping up and down screaming "me, me, pick me" then I'm happy to do
it.
[CARL] What about the (small) set of content on the Trac instance?
[MCJ] I can certainly aid with content migration (tickets, wiki, etc.)
[CARL] What about the private sources in the KRoC repository, leave these
on projects.cs.kent.ac.uk?
[CLJ] Yes, those will have to be filtered out and kept elsewhere I guess,
unless somebody wants to fork out (excuse the pun) for a paid GitHub
account. Since those things are largely Kent specific it would seem
sensible to keep them on projects.cs.kent.ac.uk.
[MCJ] Agreed---we leave the private things where they are. If we need to
move them to a private repository elsewhere in the future, that can be
managed when that time comes.
More information about the developers
mailing list