Thank you for sharing your code with the rbokeh. We appreciate your contribution!
If you’re not already on the Bokeh mailing list, take a minute to join.
Before you write too much code, check the open issues in the rbokeh issue tracker to see if someone else has already filed an issue related to your work or is already working on it. If not, go ahead and open a new issue.
Shoot us a quick email on the mailing list or note on the issue tracker letting us know what you’re working on. There will likely be people on the list who can give you tips about where to find relevant source or alert you to other planned changes that might effect your work.
If the work you’re proposing makes substantive changes to rbokeh, you may be asked to attach a design document to your issue in the issue tracker. This document should provide a high-level explanation of your design, clearly define the goal of the new design, etc. This document is meant to save you time as it allows the team a chance to provide feedback on the proposes changes. The document also allows the team to prepare for large changes to the code base. We welcome change but also want to ensure that code quality is kept high.
Github provides a nice overview on how to create a pull request.
Some general rules to follow: