World: r3wp

Or export into Git and put it on your server or on Github.

Or export into Subversion and put it on Github, or Google Code, or 
....

I think using Git is the way to god for a new project.   every big 
project I see that is changing VCS is goint Git.  it seems to be 
the most powerfull VCS right now.  do you agree Andreas?

god... hahaha 
obviously I meant  "go"

Absolutely.

And I personally would suggest Git, put that'll take time and effort 
to get started with.

So it's probably quicker to get things going by using whatever Carl 
is familiar with.

are there free Git servers?

(Let's switch this to "Source control".)

good idea.

Any one of them is fine with me.

So, A110 will be released soon.

(Meaning in a day or so.)

For this release, i'll be making fixes to the posix files, and most 
of what Steve Solie posted on CureCode.

Just to explain, my part has to remain focused on R3 development, 
mainly at the kernel level.


That means we need someone to take charge of what we've talked about 
above, using Git or whatever.

I'd be willing to do that.

Ok, very good.

What do you think about soliciting a few inputs from other developers 
regarding choice of rev control and related issues... because we'll 
want them to use it?

Fine with me, but not really a necessity.

As long as it is in _any_ version control we can easily bridge to 
almost any other VCS.

Well, I want to make sure that Brian, Cyphre, Henrik, Maxim, and 
a few others have a chance to say something... since they're going 
to be some of the primary users.

There are a few side issues around it too. Eg. do we need web access.

BTW, the reason I suggested Google was simply to gain greater visibility.

We only need to source for starters :)

The greatest visibility these days is to be had on Github.

+1 for github

Ok, so this weekend, I'll put the new A110 source on it, to start 
there.

I'll post a blog to make sure everyone is tuned in on it.

From there Andreas can lead the way on how it should go.

Note that I already maintain a mirror of the R3 hostkit sources on 
Github:
http://github.com/rebolsource/r3-hostkit

Like various scripts to make the automation side of it work.

Maybe a good place to start if you want to play around a bit.

Ah, ok...

Should we just use that?

Fine with me.

The most important part is how to automatically get your commits 
to whatever place we use. Not which place we use.

Ok, great... saves some steps.

Are there already some scripts for accessing github r3-hostkit?

Also, can you point us to a concise summary of Git usage?  I've used 
CSV and SVN, but not Git.

Also, would be good to recommend a Git client for people to start 
with.

Git's primary UI is a CLI.

Use msysgit on Win32 and the packages provided with your system (or 
build from source) on everything else.

Great! Because all of my main distro systems here are Linux or BSD, 
those clients will be needed.

Alternatively, Github also has SVN access to their repos (in beta).

For SVN write access you'll need to create an account on Github, 
though. For Git write access, I can just add SSH keys which are allowed 
to write to a particular repos.

When installing git from distro packages, just make sure you get 
a Git newer than 1.6.0.

(That means on Debian Lenny, you better get the version from the 
lenny-packports.)

A "concise summary" may be a bit problematic, as distributed version 
control really is a bit of a paradigm shift compared to CVS or SVN.

http://gitref.org/has what many consider a very good tutorial. Concise 
it is not.

I found this helpful - http://www.eecs.harvard.edu/~cduan/technical/git/

One of the more concise tutorials is the one coming with Git itself, 
which you can also read at:
http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html