How We Made GitHub Fast - GitHub Translations: Беларускі, Polski, Русский. Now that things have settled down from the move to Rackspace, I wanted to take some time to go over the architectural changes that we’ve made in order to bring you a speedier, more scalable GitHub. In my first draft of this article I spent a lot of time explaining why we made each of the technology choices that we did.
I spent a few evenings last week working on a contest that GitHub is running to create a recommender engine for their site. Think Netflix Prize but much smaller scale. Their description: The 2009 GitHub contest is a simple recommendation engine contest. Ryan Cox - AsciiArmor - Lessons Learned from the GitHub Recommen
probability distribution relationships Probability distributions have a surprising number inter-connections. A dashed line in the chart below indicates an approximate (limit) relationship between two distribution families. A solid line indicates an exact relationship: special case, sum, or transformation. Click on a distribution for the parameterization of that distribution. Click on an arrow for details on the relationship represented by the arrow.
I would like to introduce you to the Fork Queue, the first of two big features that rolled out today. As of a few minutes ago, everybody should now have a ‘Fork Queue’ tab on each of their projects. When you click on that, you’ll see something like this: This is a list of all the commits that exist in your projects fork network. If a couple of people have forked your project and then committed to their fork, you will now see a list of each of those commits, grouped by user, under this tab. What’s more, you can click on a checkbox next to each one and then choose ‘Apply’ from the dropdown menu to cherry-pick those commits onto one of your branches. The Fork Queue — GitHub
3. You can tell that by what's public and what's private right? Yes. Chris Wanstrath on GitHub