Proof of concept GitHub repo

I decided to import CruiseControl to a GitHub repository, so we could
discuss something concrete.

It was pretty straight forward:
1) install git and git-svn
2) run 'git svn clone
https://cruisecontrol.svn.sourceforge.net/svnroot/cruisecontrol/trunk'

That's not a complete clone: I'll have to experiment with the options to
bring the branches and tags in.

Also, I need to map SVN usernames[1] to GitHub usernames:

alden -> https://github.com/alden(?)
pauljulius -> https://github.com/PaulJulius(?)
jfredrick -> https://github.com/JeffreyFredrick
jchyip -> https://github.com/jchyip
jkuipers -> https://github.com/jkuipers
bahmail -> https://github.com/bhamail
sl4mmy -> https://github.com/sl4mmy
robertdw -> unknown
gurun -> unknown
Niklas Olofsson -> unknown
Hack Kampbjørn -> unknown

It's not mandatory to do this, but as committers would need a GitHub
account to participate, it seems sensible to get this done when an import
would happen. Besides, I think it's this social element (being able to
easily discover the work of others) that is valuable.

Anyway, feel free to have a look:

https://github.com/builddoctor/cruisecontrol

Best,

Julian.


[1] taken from http://cruisecontrol.sourceforge.net/developers.html, and by
grepping 'svn log' entries
-- 
Julian Simpson
The Build Doctor Ltd.
http://www.build-doctor.com
[email protected]
(+44) 207 183 0323

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/

_______________________________________________
Cruisecontrol-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-devel