Why was octokit.js forked from michael/github?

[cirosantilli]

Are there different design goals / principles? If yes, which?

[philschatz]

Thanks for the interest (and the contributions)!

My original goal was to add support for Promises and have it run in the browser or as a NodeJS package. I also converted the code to coffeescript (for conciseness) and submitted a Pull Request. It took a month or so before getting a response so I just kept adding features and by the time the Pull Req was rejected I had already made significant changes.

If I recall correctly, you were interested in github-tools#68 . Rather than refactor this API it may be easier to use philschatz/octokat.js since it is less hard-coded to GitHub's API. I posted some thoughts on octokat.js at http://philschatz.com

Hope that helps!

[cirosantilli]

@philschatz Thanks a lot for the explanation.

I am very interested in adding GitLab to a Js GitHub API wrapper so as to implement the largest possible intersection of both with the same interface, and if Shuttleworth or the Catalyst Grant takes me I will put 4 weeks into it.

So you are focusing more on Octokat development now is that it?

I saw GitHub bookeditor is still currently using Octokit, are there plans to shift to Octokat?

Which project would it benefit OER the most to add GitLab support to?

I recommend the octokit vs octokat question be commented in their README to help focus development on the preferred one.