HotDrink moving to GitHub
John Freeman
collaboration on GitHub. It has further been split into a main project
and two extensions: Dijit bindings and an Adam parser.
hotdrink: https://github.com/thejohnfreeman/hotdrink
hotdrink-dijit: https://github.com/thejohnfreeman/hotdrink-dijit
hotdrink-parser: https://github.com/thejohnfreeman/hotdrink-parser
For the extensions, no outside dependencies need be installed:
Prototype, jQuery, es5-shim, etc., if used, are downloaded by clients
from CDNs. However, in order to run their tests or examples, the main
HotDrink library must be linked in their test/js directories.
The mailing lists will stick around, and remaining issues in the Google
Code tracker will be resolved or ported. All future issues should be
reported on GitHub.
Documentation sources (including tutorials) should go into the
repository under a top-level "docs" directory. They will be compiled and
uploaded to hotdrinkjs.com periodically.
- John
John Freeman
> The HotDrink project will now continue all future development and
> collaboration on GitHub.
The jarvigit repository should receive no more contributions for the
JavaScript library. All such work should be directed to GitHub.
I should note that I cleaned up the repositories some before pushing
them to GitHub, so their layout will differ slightly from jarvigit. If
you have work-in-progress, then you will need to port it over manually.
I'm sorry; I wanted a clean start.
- John
neonstalwart
Did you consider hosting the code in an organization account on github? If you think you might eventually move to an organization account it might be good to do it from the start. It could help give the project it's own identity.
John Freeman
> I'm looking forward to seeing how this project advances.
I'm excited, too, and working as fast as I can!
> Did you consider hosting the code in an organization account on github?
No, I don't think we will move to an organization account.
- John