Blockly welcomes your contributions. Want to add a new feature? Want to fix a bug that's annoying you? Want to add hooks needed for your own application? Want to improve our unit test coverage?
A pull request on GitHub is the preferred way to handle contributions. Alternatively you can send us a patch.
Some rules:
- All code must conform to Google's JavaScript Style Guide. We are pedantic about consistency.
- Any new code files must be prefixed with the Apache License, Version 2.0. We won't mix licenses.
- User-visible strings must be in the
/msg
directory so they may be translated. Less than 6% of the world speaks English natively. - Text on blocks should generally be all lowercase (just like the keywords in most programming languages).
- Maintain backwards compatability. There are a lot of Blockly apps out there, don't break everyone else.
- Spell "colour" correctly.
Tell Us!
Blockly has an active newsgroup for developers. Please drop by and say hello. Show us your prototypes early; collectively we have a lot of experience and can offer hints which will save you time. It is always disappointing when we first learn about some large Blockly user from reading a news article and their app has issues that could have easily been avoided.