-
-
Notifications
You must be signed in to change notification settings - Fork 107
Collaboration process
hbt edited this page Apr 7, 2012
·
3 revisions
Quick workflow to keep in mind when contributing
- search tickets + check code to make sure feature doesn't already exist
- log a ticket and explain what you want to work on, fix, discuss etc. This step is important. Otherwise, we end up with a network of forks with duplicated code
- fork the project
- get submodules
git submodule init
git submodule update
- create a branch
e.g
git checkout -b dev/122
- hack away
- run JS formatter
rake format_js
- when committing your code; mention the issue number e.g
-#122 fixes alignment in text editor
This way your progress appears on the ticket page. - send us a pull request
Feel free to add yourself in the Thanks file. Looking forward to your work
Notes
- latest dev version will be in stable-dev
- dev/XXX refers to issues in progress or in need of review before being merged to stable-dev
- master is used for releases only