Page History

...

Basically, an SVN commit hook updates the official ASF git clone. http://github.com/apache^{Image Removed} pulls from the official ASF git clone. The official git clone should be more or less instantly updated, less is known about the exact replication frequency of the github fork, but with git this is not really important.

...

As example, we use maven-3, located at http://github.com/apache/maven-3^{Image Removed}.

1. Go to that URL an choose "fork" in github to create a read/write copy under your own user. There are several reasons to do this:

• You can keep your own changes before you commit back to SVN, with backup.
• You can use full version control features like committing, without actually committing to svn.
• Seasoned git users sometimes commit & push in wildly inconsistent states when compared to what SVN users do. Get this extra freedom of choice.
• Forking from the official github node also makes your project visible within the github project graph, allowing collaborators to see you. If you haven't read about github's collaborative network visualizer, you might want to read up on this here http://github.com/blog/39-say-hello-to-the-network-graph-visualizer^{Image Removed}
• Moving between your laptop and your desktop becomes trivial; the author of this guide frequently finds himself moving between 3 different computers in a 3 hour session; it's how I manage to code with kids.

...