skwpspace yan pritzker’s home on the web

skwpspace is Yan Pritzker's home on the web

Blog :: Photography :: About Me

TwitterCounter for @skwp

Get the news feed
Get updates by email
Follow me on twitter

hello, i'm yan

This blog is about startups, blogging, Ruby On Rails, virtualization and cloud computing, photography, customer service, marketing, ux and design, git, and lots more.

Top Posts

planypus

I'm the founder of Planypus, the place to share your plans!

cohesiveft

Accessible, manageable, virtualized application stacks ready to download or deploy to the cloud!

flickr

PorstiluxwiresKeri JohnsrudMichelleConcerttributeherekittyapartment story (color)

Archives

Contact

Reach me at yan at pritzker.ws

Posted
3 June 2008 @ 2am

Tagged
git, startups, thoughts

GitHub is leading us to an opensource renaissance

Before GitHub, if you had something to contribute to an open source project, you basically had to worry about tracking your changes against someone else’s remote repo, which was usually svn or similar, which was difficult and cumbersome. And even if you did manage to have enough motivation to properly track, format, and email the author your patches, he then had to go and integrate your patches which was also difficult and cumbersome.

What’s nice about GitHub is that first, it gives you an easy way to fork anyone’s codebase. The key feature of GitHub is fork network tracking, which lets you see everyone else who’s cloned a particular repo, and what changes they have made. The big benefit is that this prevents you from re-inventing the wheel when you see that someone is already working on the same feature you’re trying to submit. Instead of going and doing your own thing, you fork off of them and work with them. You might even fork off of a grandchild of the original project just because it has some feature that you need. It’s like the long tail of open source..you no longer have to wait for the original author to implement your obscure changes. Just find what you want out there and work with it.

The reciprocal benefit of this, of course, is that the original author can actually watch your changes as you’re making them. Instead of some disjointed patches, he sees your commits as you add them to your own line and can follow your progress visually. At some point, if the author likes your work he can merge your branch back into his code. And GitHub will show this on the network, so everyone else who is following the project can benefit. They’ve made it easy to notify the author that you have some good changes as well, with the pull request.

This very simple idea of tracking the forking network of a particular project, and doing it well, is why GitHub has made a radically cool contribution to the opensource community. Every day, more and more projects are added to the hub. And it’s viral…people who want to contribute to projects request that the project be put on GitHub because it’s the easiest way to track your contributions. Kudos to GitHub!


7 Comments

Posted by
Thomas
3 June 2008 @ 12pm

github is definitely great thing for git but I’m not sure if its impact on open source in general will be that big. It’s still too ruby-centric and for a bigger impact it’s necessary that other languages are strongly represented as well.

Maybe if one of the linux window managers or graphics programs like scribus oder inkscape with move to GitHub then I’d call it a breakthrough.


Posted by
Matt Todd
3 June 2008 @ 3pm

@Thomas: a breakthrough isn’t defined by who uses it but what it allows those that do use it to do. In this light, GitHub is a breakthrough for creating a central, social mechanism for distributed Git development.

Also, numerous non-Ruby projects are already hosted at GitHub. Look around. But really, it doesn’t matter what languages and projects are using it but that it’s being used well by anybody.


Posted by
yan
3 June 2008 @ 5pm

I agree with Matt, there are plenty of non-Ruby projects and there will be more as the Ruby/Rails community has shown itself to be a bleeding edge early adopter, and that effect will rub off on others around them including communities like Erlang.

What I thought was really great was the development of gitjour (a git over bonjour client/server) during RailsConf. Practically overnight it sprung 15 forks on GitHub with everyone contributing patches. This would not have been possible or as easy prior to GitHub.


Posted by
Gabe da Silveira
4 June 2008 @ 4am

Couldn’t help but agree with the headline before I clicked through. I’m not sure what is the most killer feature in the stack, but coming from svn recently, this whole thing is almost too good to be true. Offline development, proper merges, easy branching, fast performance, centrally hosted for free, developer social network aspect, forking, fork network viewer, etc.

All I know for sure is that this is waayyyy more exciting than SourceForge ever was, and I was a lot more excitable back then. Git by itself should be compelling to ANYONE using svn, but github is the secret sauce that could pull it over the hump.


[...] I’m finally beginning to grok Git. [...]


[...] etc), to the sheer joy of being able to easily contribute to your favorite projects, to even more people realizing its importance, GitHub has reinvigorated the OSS development world like nothing else in the past almost ten years, [...]


Posted by
Robby Mcgee
12 November 2008 @ 9pm

hbm5gs4j82ww916o


Leave a Comment

Virtualization slides featured on SlideShare homepage Good customer service means replying to email immediately