emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tycho garen <tychoish@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Emacs-orgmode@gnu.org
Subject: Re: GitHub
Date: Sat, 22 May 2010 08:54:36 -0400	[thread overview]
Message-ID: <20100522125436.GC4551@deleuze.linlan> (raw)
In-Reply-To: <B88C1A26-43B0-493D-8AEF-B39923E073E8@gmail.com>

As a brief prelude, I'd like to say that while I think github is a
great service, for development communities, and provides a number of
very enticing features, there are some aspects that make it less than
ideal: 

Projects are owned by individual developer's "personal" accounts and
it's sometimes less than intuitive to figure out which fork of the
repository is the "right" one for users not involved in the community.

There's some degree of lock-in, particularly with the features that
repo.or.cz doesn't have. Having said that, git's distributed nature
makes this much less relevant than it would be otherwise.

Having said that the "killer" feature of github is the ease of
creating forks. Repo.or.cz has that, so at least from my perspective,
it's not as big of a draw, but I'm not an active org-mode-code
contributor so I think my opinion here isn't terribly relevant. 

But specific questions and answers.

On Sat, May 22, 2010 at 08:24:30AM +0200, Carsten Dominik wrote:

> - How do I get the entire current repo onto GitHub?

This is the easiest. Get a github account. Create a project, and begin
pushing to this repository. Fundamentally github exists for people who
don't want to manage the infrastructure for hosting remote git
repositories. 

> - Can I set up repo.or.cz in a way that it will become an
>   automatic mirror, so that old clones will continue to be updated when
>   pulling?

Yes. I'd need to talk to pasky to make sure there's not another way,
but I think the thing to do is get a repo.or.cz admin (like me) to
re/move the existing org-mode repo out of the way, and then recreate a
new project that clones the git-hub repository. 

> - Bastien - I guess on the web server, we would simply make a
>   new clone from the new location, right?

Almost certainly but I'll defer here. 

Cheers!

-- 
tycho(ish) @
garen@tychoish.com
http://www.tychoish.com/
http://www.cyborginstitute.com/
"don't get it right, get it written" -- james thurber

  parent reply	other threads:[~2010-05-22 12:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-22  6:24 GitHub Carsten Dominik
2010-05-22  7:34 ` GitHub Carsten Dominik
2010-05-22 10:45   ` GitHub Ian Barton
2010-05-22 19:22   ` Nick Dokos
2010-05-23  5:14     ` Carsten Dominik
2010-05-22 12:52 ` GitHub Matt Lundin
2010-05-22 14:22   ` GitHub Eric Schulte
2010-05-22 12:54 ` tycho garen [this message]
2010-05-22 17:14 ` GitHub Matthew Jones
2010-05-31  7:20   ` GitHub Carsten Dominik
2010-06-02 19:46     ` GitHub Daniel Martins
2010-06-03 10:29       ` GitHub Ian Barton
2010-05-24 16:24 ` GitHub Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100522125436.GC4551@deleuze.linlan \
    --to=tychoish@gmail.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=carsten.dominik@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).