Core Development w/ Github
April 13th, 2008 by Ted KulpAs you all know by now, CMSMS 2.0 development is now if full swing. Both calguy and myself have been hitting the code pretty hard over the last couple of weeks trying to finish it up and get a beta ready to go. While there is still a lot to do, I’m starting to see the end in sight.
A few random folks have asked about helping out with development of 2.0, which I love. However, being the control freak that I am, I’m a bit worried still about giving the world free reign on subversion commit access. A few months ago, I discussed using git for core development. Yes, I still use this model for my 2.0 work and can’t imagine switching back to pure subversion. I can be as A.D.D. as usual by having scattered branches of the various things I’m working on, and only commit them back when I feel stuff is ready.
Anyhoo, github has gone live. This is pretty much the ultimate geek social network. It allows you to setup your git respoistories to the world. Better yet, it allows anyone else to essentially “fork” that repository, make their changes at will, and easily alert the original person to take a look at your changes. It’s terribly brilliant and REALLY useful.
I push the CMSMS code up to git every day or so from my personal mirror of the current svn repository. It’ll usually be up to date. If I know people are working from it, I’ll make sure it’s always up to date within a few hours. The main repository is located here. Fork to your hearts content, people.
So, do yourself a favor. Learn git. Use git. Love git. And once you wrap your head around it, use github to make those wild and crazy changes to the CMSMS 2.0 code and tell me about them. The proof is in the code, my friends. Get coding!
Want to seriously be amazed at the power of git? Read this account. For some good links (even though there is a ruby spin), look here.
Enjoy!
April 13th, 2008 at 8:22 pm
cool blog, and thanks your share, I will share a good experience with you, I have a lot of friends on equestriancupid.com/i/sabrina, I think they must love you very much, you can be their teacher, you really a expert.
welcome you join!~
April 14th, 2008 at 4:14 pm
Hehe. Great:)) I’m the one who proposed help on 2.0 development. Good advice! I’ll check it.
April 14th, 2008 at 4:21 pm
But also i think that it’s hard to enter development of the new project(e.g. for me), even using separate repository, without any TODO lists, or requests list:(
April 16th, 2008 at 9:16 pm
How do other successful open source projects do it?
I was checking out the TODO/Project Openings list on the blender.org site.
http://www.blender.org/development/current-projects/project-openings/
Quite cool, they organise their TODO list in terms of how familiar a person is with the code…
Plus there is a lot of documentation as to the objectives of the application, coding guidelines, how to submit patches, etc.
eg http://www.blender.org/community/get-involved/
IRC Meeting Minutes!:
http://www.blender.org/development/coding-guides/irc-meeting-minutes/
but most noteable:
a detailed introduction as to how the application works! with pictures!
http://www.blender.org/development/architecture/
The more documentation provided, the easier it is for a developer to come in and help…and many hands make light work.
April 16th, 2008 at 10:05 pm
Additionally, API documentation needs examples.
Check out the mootools docs:
http://docs.mootools.net/
April 18th, 2008 at 2:40 am
I think we found some more volunteers for the documentation.. Get involved, your forum account will give you access to edit the wiki!
May 10th, 2008 at 9:27 am
Thanks for the git push!