Up till now I have been using source.o2js.com as a repository for the source code of o2.js. Though I believe o2.js has matured enough to be collaborated with a larger community. So, from now on, I will be pushing the code of o2.js to github.
Why git?
Because git is awesome!
Literally. I am in the awe of git‘s elegance, power and simplicity.
It’s so awesome that it deserves a separate blog post in an of itself (… umm adding to my to-do-list
)
It’s not just the distributed nature of it. There’s more:
- Your local git repository is self-contained and complete, which will allow you to work off-line.
Creating a git project is as easy as “git init”. - And git is “damn fast”. I’m sure you’ve heard it before, but you have to see it to believe it
So Why github?
Git is awesome, and github makes it even more awesome!
Git is an excellent VCS standing alone, and with github being packed on top of it — an extremely powerful tuple.
github is not merely a “web-based repo”. It, at it’s core, is a public place to store your repositories and for other people (and yourself) to navigate the contents, history, etc.
One of the most fantastic things about github is something that encourages projects to get more contributors by making it extremely easy to contribute: forking.
If you have a project and you want contributors, github is the place to be.
So here I am, on github:
You can follow my github profile or fork o2.js on github.
p.s.
I’m kinda new to “github”.
So, any pointers, comments and suggestions are welcome ![]()
Also feel free to share your github profiles, ideas and opinions.

