The archive · Developer & Business Tools · Product decision · 2011
GitHacking, born at Startup Weekend, bets paid matching fixes open source
Four founders built GitHacking in 54 hours at Startup Weekend and won first prize — betting open source needed a matching layer that companies would pay for.
GitHacking
What the business is
GitHacking connects developers to open-source projects they would enjoy contributing to, helps maintainers recruit contributors, and planned a paid platform for businesses to get support and issue fixes.
How it started
GitHacking was born over 54 hours at Philadelphia Startup Weekend in January 2011 to four founders: Chris, John, Josiah and Aaron. Their premise was that open-source discovery ran on word of mouth, leaving developers on the outer rings unable to find projects that wanted their help and maintainers unable to recruit contributors. The team posted the site to Hacker News before the final demo and went on to win first prize.
What happened
The Hacker News launch on 2011-01-30 drew 185 points and 47 comments. Commenters liked the idea — one called it 'OkCupid for code' — but immediately probed the paid business model: what stops a company from copying a posted solution instead of paying for it? Others flagged the logo, which mixed GitHub's octocat with Apple's Terminal icon. The founders said the logo and an about page were coming, and that a paid platform for businesses would follow once the free matching work was useful.
No ending yet — it is still running.
Background
GitHacking was a matchmaking service for open source, built at Philadelphia Startup Weekend in January 2011. The founders' pitch: developers could not find projects worth contributing to — most repository discovery was word of mouth — while maintainers had no good way to recruit the help their projects needed.
The team of four built the site in 54 hours, posted it to Hacker News before the final demo, and then won first prize at the weekend. Their roadmap ran from free matching between developers and projects to a paid platform where businesses that relied on open source could pay for support and issue resolution, with contributors and maintainers rewarded for their work.
The launch thread drew 185 points and 47 comments. The strongest reaction was the business-model question: what stops a company from inspecting a developer's solution and copying it into its own repository instead of paying? Commenters also flagged a logo that borrowed GitHub's octocat, which the founders promised to fix quickly.
As of the launch thread the site was live with an email signup, the founders were still polishing mobile rendering and adding an about page, and the paid platform had not been built. The team's stated order was to make the free service useful to open-source projects first and worry about the company-facing marketplace later.
What has to be true
- The founders bet that GitHub's discovery gap was real: projects were found by word of mouth, so developers outside the inner circles had no way to find where their help was wanted.
- A 54-hour Startup Weekend forced a demo-first build, so the team launched publicly before the product or business model was finished.
- The copy-paste objection to paid bounties surfaced within hours of launch, showing that the monetization's enforcement problem was unsolved from day one.
- Winning first prize gave the project momentum and a public pitch before there was any evidence of demand beyond the launch thread.
What can be applied
A paid layer on free work lives or dies on enforcement: if customers can copy a solution instead of paying, they will say so at launch — answer that objection before pricing the work.
Aftermath
As of 30 January 2011 GitHacking had a live landing page collecting emails, a first-place Startup Weekend finish, and a front-page Hacker News launch behind it. The founders were iterating on the site, planned to open to the public soon, and said the paid platform for businesses would come after the free matching service proved useful to open-source projects.
Sources
spotted an error? The archive wants to know.
Your turn
You just read one. Describe what you are building, and see who is betting on the same thing.
Free account · 3 free questions · no card