defunkt

Me too! Well, not Gravatar. But GitHub.

I'm a big Black Maple Hill fan. Will have to try Rittenhouse - thanks!

Free? If you win, you get a lifetime GitHub account and a tasty bottle of bourbon.

We're trading you the prizes for a commercial license.

Video of the talk: http://blip.tv/file/2400597

Oh, so I wasn't reading it right :P

If I'm reading this right, they predicted 25m users by the end of 2009?

As of July, they apparently have 40m. Cool.

Link to the actual offer: http://groups.google.com/group/erlang-programming/browse_thr...

Hiring Evan is one of the best decisions Twitter has made. I hope he continues writing posts in this fashion.

GitHub Pages is for hosting documentation: http://defunkt.github.com/ambition/

Sourceforge and Rubyforge both provide similar services. This is nothing new.

It's also for hosting static blogs: http://tom.preston-werner.com/

It's also for hosting personal sites: http://defunkt.github.com/

I love seeing creative uses of Pages. If we spent all our time worrying "what if," we wouldn't have a brand to dilute nor a team's attention to divert.

After long sessions of UniWar my EDGE would get super hot.

Have not noticed the same with my 3GS.

I feel as though adding new syntax to JSON is antithetical to the whole idea.

    { json: [ my stuff... ]}

Isn't that sufficient? Use that when returning sensitive data, just normal arrays when not dealing with sensitive info.

I bet at least some people outside SF have no idea what "muni" means.

Totally agree... I know many people who pay for music but not movies.

There's no support for this currently, but maybe we should introduce syntax in the .rip file?

`latest` or `rip-latest` or some such?

I got back from Railsconf and couldn't start the GitHub Rails app because of some dependency issues caused by a random gem I had installed at the conference.

I feel your pain. That's where it all began.

That's true, I do use virtualenvwrapper and was inspired by it as well. I'm adding it to the README now.

Sorry in advance if you run into problems installing this.

It's not the most simple problem and I was limited during development to my own setup and the setup of a few peers.

I'd love to get it rock solid and take it where it needs to go.

Sorry, I didn't mean to call you out for being anti-anything. Was just curious why you said RoR-heavy when I only saw one developer :)

Isn't DHH the only RoR developer on this list?

I'm not gonna defend git, but it's pretty damn hard to google for libraries or code written in Io.

Luckily the documentation explains clearly those heuristics and provides examples so you can appease them yourself :)

Why?

Gem publishing is opt-in. Even for forks.

We were talking tonight about CPAN modules, Python eggs, and PEAR... pears?

We'd love to take what we've learned serving Rubygems and apply the knowledge to any other languages that have a solid packaging system.

We exclude certain paths, especially popular JavaScript libraries.

That's the direction we want to take it.

That blog post is no longer accurate. We don't count LOC for language popularity, we count the number of non-fork projects that include a language.

If your project includes both Ruby and Perl, Ruby and Perl each get a +1.

Some JavaScript implementations can't handle keywords as property names.

e.g. in Safari:

var a = { new: 'Monkey' }

fails. Thus the required quotes in the JSON spec.

The Fork Queue is a replacement for email patch management, not a merge tool. It is for cherry picking changes from contributors, not merging branches.

This is why the author information is retained and --signoff is used.

As Hongli Lai says in the comments: Most of the time, people who fork my projects make a bunch of changes, some which I want and some which I do not want. Cherry-picking instead of pulling totally makes sense in these situations.

This is the situation it was designed for - reviewing and signing off on individual commits, not merging branches.

I think the takeaway from this article is that we need to do a better job explaining the feature and what it's for. I understand now how someone new to the site would have no concept of email patch management or git cherry-pick and assume this is a nice interface for `git merge`.

As a first step, I've improved the text in the help dialogue to be more clear and link to the blog post + intro video more prominently. Maybe a next step would be making the actual help link itself (it's a small question mark next to Your <project> Fork Queue) more visible.

Also we could detect if it was your first time using the Fork Queue and offer help - that seems to be a popular idiom for web apps these days.

Perhaps in the future we can even offer a first class merge tool as the author suggests, but for now I've been extremely happy with how the Fork Queue compliments (but doesn't replace) my offline workflow.

If you're building apps with Cocoa, it's very easy to embed and drive WebKit.

=)

edit: To elaborate, we view the growth of DVCS in general as a good thing. (Also we have a big surprise coming soon for hg users.)