From: Jeff Hobbs <jeffh@ac...> - 2009-05-12 19:29:52
I've had a couple of questions regarding how to deal with source code
for GSOC students this year which I want to answer for all.
All students are expected to create a source base that is then presented
as a patch (or whole, if new project) to Google as part of the final
Tcl core sources are currently hosted by SourceForge at
http://tcl.sourceforge.net/ in CVS. CVS isn't ideal for independent
branch development, that is where DVCSs such as git prevail.
For those of you that are dealing with the core, you might find it
easiest to clone off of Daniel Steffen's git mirror repository of the
Tcl source base.
Github Home: http://github.com/das/tcl/tree/master
Clone URL: git://github.com/das/tcl.git
You will not need write access to the github repository, as you will
clone and work on your own version.
I recommend this method for Daniel Kloeck and Łukasz in particular, as
it will allow you to commit in pieces independently while tracking the
updated (mirrored) head with git.
Let us know if you have any other questions regarding code management.
Tuesday 12 of May 2009 21:28:44 Jeff Hobbs napisał(/a):
> For those of you that are dealing with the core, you might find it
> easiest to clone off of Daniel Steffen's git mirror repository of the
> Tcl source base.
> Github Home: http://github.com/das/tcl/tree/master
> Clone URL: git://github.com/das/tcl.git
And for those who are creating new code:
I used Trac to communicate with DAS and it worked really well. But you might
be interested in having all that functionality in DVCS. So I suggest looking
at Fossil (http://fossil-scm.org/) - it's nice and easy. If it doesn't cut
your needs, then a good alternative is Trac+GIT, but that's a whole lot more
work to set up.
Remigiusz 'lRem' Modrzejewski
Prezes Koła Naukowego Sfera