I think depending upon a single, proprietary web service for everything is foolish. When Github is down, you're out of luck. If Github changes in a way you don't like, you're out of luck.

This isn't what I thought it would be. I think "Github for everything" is something everyone should be looking for in their lives. Version control is useful for so many things.

I think the understand this already though. With the release of stuff like 3d diffs now it's the "GitHub of CAD", I could imagine a useful future for the "GitHub of legal documents", "GitHub of _____"....

Although maybe this blog post was already in the pipeline, unfortunate juxtaposition with yesterday's GitHub outage.

Although I truly do love GitHub, it's not unconditional love. My love's uptime closely tracks GitHub's.

Idea: Github should allow "plugin repositories" that can be shared or private.

The first iteration would have some way to provide file type viewers. A file under filetype/viewer.js.js would replace github's default JavaScript viewer (itself simply published as a repository that just happens to be the top node). You could start your own customizations by forking that repository. If you develop a viewer/editor/future plugin component that you think the world should use, send it in as a pull request to the canonical repo.

The other thing I think github should do is go the JetBrains Upstream / Google Grok (if it ever happens) route and provide syntactic / semantic analysis as a service, from which all these visualizers, editors, and other tools are built.

It great, but I concern about exporting data out from GitHub for whatever a reason. Is there a backup anything or we just have to dig data out from API?

Although it's nice that everything is in one place I don't think Github would be my first choice. It's made primarily for managing code and everything surrounding that. I do think the issue tracking translates very well over to "real life" issues.

Why are the legal documents not on GitHub though? That would be perfect for github.

Github goes down far too frequently to consider using the non-enterprise version for everything.

The realtime collaboration on Google docs is also mega useful for weekly meetings and something that Github's wikis doesn't match.

I'm still bracing myself for the Github for Writers; http://madebyloren.com/github-for-writers

This is exactly what we do at our team too -- we're developer centric and as developers, we love using Github and Github issues (+ pull-requests) for everything (including PM and HR)

One thing we do miss are certain features from Trello-like tools that give a nice overview of your issues and facilitate PM, so we built a Chrome/FF extension to fill in those gaps (http://zenhub.io)

Disclaimer: I work at Axiom Zen

Everyone love and use wikipedia but i do not see 10k posts per day saying that wikipedia is the new god.

This idea is awesome. Thanks for sharing!

Are your internal wiki, recruitment process, Day-to-day operations, etc. on a private repository? Do you have only one repository or do you have multiple repositories for your internal work?

I expect with a few custom front end UIs, even the poor fits could at least use github as a backing store. This could give other company tools one data layer to inspect.

Like this way of getting things done. Geeky! I may translate the post into Chinese later.