Bhavesh of Vinsol forking on a cycle rickshaw in New Delhi, India!
Please take a few minutes to fill out the 2008 Git User’s Survey.
The Git community values this annual survey. By filling it out, you’re contributing to the superb open source tool we all use and love.
All questions are optional. You can skip questions and submit at any time.
The official announcement is on the Git mailing list. We’ll post about the results once the survey ends (around October 10th).
(Also: tell your friends.)
Update: Explained all the questions are optional.
At my workplace, a Microsoft ISA authenticating web proxy server is in place, restricting most outbound traffic. Specifically, port 22, the ssh port, is not allowed and that means I can’t pull or push to my repositories on GitHub.
Update: I got Justin’s username wrong. Whoops! Fixed.
Thanks Zach – time for the Lispers, Pythonistas, and Java beans to step up!
(On a related note, we have cool project statistics, activity, and language features coming soon.)
Two nights ago, jnunemaker headed on a motorcycle ride to the Mackinac bridge in northern Michigan. GitHub led the way.
From the post:
If I had to boil down the benefits of Github into one quick point, it’s basically this: hosting with Github increases the frequency with which others contribute code to you. It does this by making it dead simple.
Let’s say you’ve got a cool Gist you want to share, but don’t love the boring URL. No problem. Just use bit.ly.
bit.ly also tracks click throughs, for that extra bit of ego boost.
Update: Fixed link.
The flogic guys have a great write up detailing their setup. They go into detail on how to setup a local mirror to use when deploying your app.
Here’s a summary, in their own words:
Here’s how we’re doing the mirroring… In the discussion that follows there are three machines involved: (1) a local workstation (or laptop, as the case actually is) where I’m doing development work, I’ll refer to it as “local”; (2) a git repository host under our control, which will be running gitosis, to which we push, and which then mirrors to github, called “internal”; and (3) github.com.
Update: I forgot to link to the blog post outside of the image. Thanks Matt.
Blueprint CSS, everyone’s favorite CSS framework, has moved to GitHub.
Straight from the horse’s mouth:
Blueprint is a CSS framework, which aims to cut down on your CSS development time. It gives you a solid CSS foundation to build your project on top of, with an easy-to-use grid, sensible typography, and even a stylesheet for printing.
The Haskell guys got together, evaluated the options, and decided Git was the best choice.
It came down to two things: the degree of support available, and
flexibility of the tools (git is much happier to let you modify the history
than Mercurial). Speed ruled out bzr, and Windows support is less of an
issue: git appears to work reasonably well on Windows these days.
Check out the GHC mirror on GitHub to follow along. Score one more for the good guys.