The drop is always movingYou know that saying about standing on the shoulders of giants? Drupal is standing on a huge pile of midgetsAll content management systems suck, Drupal just happens to suck less.Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]Drupal makes sandwiches happen.There is a module for that

Eating my words on github

Submitted by nk on Mon, 2012-02-06 23:36

Two years ago I wrote a blog post about why not to use github. I simply was wrong. As jQuery won the JS framework war so did git won the DVCS war and one of the reasons is actually github. I have been using github to host private projects for my clients and the service / workflow is really top notch -- fork from the UI, hack, send a pull request, comment the diff line-by-line, do the minor fixes in the online editor on spot, click the merge button, done. Nicely done.

Commenting on this Story is closed.

Submitted by Anonymous on Tue, 2012-02-07 09:30.

I'm still looking for an "in the cloud" source control solution. Can't exactly run a server from my place (dynamic IP and electricity that sometimes has been shut off and back on while at work), but using email for source control isn't exactly good either.

Github sounds perfect for me, judging from what you just said you can do with it. But... from what I've seen of it, anybody can browse anybody's projects. Is there a way to hide projects from prying eyes? It's a necessity for those projects that should stay a secret until they're done and ready to be released.

Submitted by Anonymous on Tue, 2012-02-07 09:43.

Hi, github provides everyone with certain number of public repos, but you have to pay for private repos. Have a look at their site for more info.

Submitted by Anonymous on Tue, 2012-02-07 10:36.

I run mine's off my own VPS. It's not too hard to get git setup over SSH to do basically what github does; but cheaper. If you are a bit crafty you can even set it up so that other people with their own keys can have at the repo. Any VPS will do; and for a single user it takes maybe 5 minutes if you can google the right howto.

Submitted by Anonymous on Tue, 2012-02-07 12:34.

I tried this, but to get the same features as github on your own server it'll take a bit longer than 5 min. Pull-requests, users can upload new ssh-keys, wiki, discussions with requests, ... That stuff is what makes github more than just a DVCS host. Although it might not be needed for every project, some things can be helpful in nearly all projects.

Submitted by Anonymous on Tue, 2012-02-07 17:06.

You should look at GitlabHQ. They're doing an amazing job on their product - it does not currently have a wiki, but they're planning on implementing it with Gollum (the same wiki engine that Github uses). It also has the idea of a pull request (sort of). It's based on Gitolite and it's not very difficult to set up.

Submitted by Anonymous on Mon, 2012-06-11 09:07.

Thanks so very much for taking your time to create this very useful and informative site. I have learned a lot from your site.


Submitted by Anonymous on Tue, 2012-02-07 20:14. provides free private repos (git or mercurial)

Submitted by Anonymous on Tue, 2012-02-07 20:23.

Does that mean you believe Drupal took the wrong path with their custom Git hosting and integration? To me, it feels half-assed in comparison to the tools and community that GitHub has.

// @tobiassjosten

Submitted by nk on Wed, 2012-02-08 06:47.

Drupal likes to have everything under one roof. However, this requires serious resources. So: I am not sure. What we have on is nice, though. github doesn't support the patch workflow.

Submitted by Anonymous on Wed, 2012-02-15 23:20.

You can send a patch, and you can apply and push. But nobody use it cloning and pull request are habitually way more efficient.

I think I'm not the only want than dream to be be able to use a github style workflow...

For me it was a mistake losing so much resources in infrastructure.

Submitted by Anonymous on Sun, 2012-02-19 11:07.

The patch workflow is rather dated, IMO. Instead of downloading a patch and then manually applying it you could just simply pull and checkout the feature branch. Not to speak about the vast simplification of contributing code.

Plus with Travis CI ( you could probably cover continuously running the test suites.

That's a lot of time and effort that could be spent elsewhere. For a superior result.

// @tobiassjosten

Submitted by Anonymous on Tue, 2012-02-14 06:31.

I really loved reading your blog. It was very well authored and easy to understand.
web designing vizag