- Patrick Stadler · @pstadler · [email protected]
- Michael Weibel · @weibelm · [email protected]
- Mailing list
- yes, non-gmail users can signup as well
- FAQ
You want to help us? Awesome!
A few hopefully helpful hints to contributing to Candy
- Fork Candy
- Install Vagrant
- Follow instructions for Candy Vagrant
- Change the remote in the
candy
andcandy-plugins
repos:git remote set-url origin git://github.com/YOURNAME/candy
(or candy-plugins) - Create a branch based on the
dev
branch (git checkout -B my-awesome-feature
) - Run
grunt watch
to automatically run jshint (syntax checker) and the build ofcandy.bundle.js
andcandy.min.js
while developing. - Make your changes, fix eventual jshint errors & push them back to your fork
- Create a pull request
Please note that you should have a working XMPP server to test your changes (the vagrant way does already have a working XMPP server).
- Fork Candy
- Clone your fork
- Checkout out
dev
branch (git checkout dev
) & Update git submodulesgit submodule update --init
- Install Node.js
- Install Grunt (
npm install -g grunt-cli
) - Install npm dependencies (
npm install
in candy root directory) - Create a branch based on the
dev
branch (git checkout -B my-awesome-feature
) - Run
grunt watch
to automatically run jshint (syntax checker) and the build ofcandy.bundle.js
andcandy.min.js
while developing. - Make your changes, fix eventual jshint errors & push them back to your fork
- Create a pull request
In case you have any questions, don't hesitate to ask on the Mailing list.