Asking for Help

Our support channels and team interaction are open to all levels of users, even and especially those new to using Bokeh! Support is provided on a volunteer basis by our core team of maintainers, as well as by interested members of our user community. For the best outcome, we offer the following guidelines when posting a request for support:

For usage questions, we primarily encourage visiting the Bokeh Discourse. This forum is monitored by members of the core team, includes Showcase examples of projects using Bokeh for inspiration, and is a great way to get feedback from other users on how to approach a problem.

Questions involving pandas or other libraries may find a wider audience by posting on Stack Overflow, using the tag bokeh.

We appreciate if you do not cross post questions on both Stack Overflow and Discourse. However, if you do, please include a link to the other topic.

If you think you've found a bug, or would like to request a feature, the appropriate place is the GitHub issue tracker. Core team members will review and either offer an explanation or workaround, or confirm the issue and add to the backlog of planned development to fix.

Do not contact team members privately for support. In order to provide benefit for the entire community, all questions are answered only on public, archived, searchable forums.

It's best to post a new question on support forums, even if you think it may be redundant. The speed of Bokeh development means that the answer or best practice for your situation may have changed.

Creating a minimal reproducing example of issues is the best way to get a meaningful answer specific to your question. Code examples should be runnable as-is, without dependencies on data sources or other files that someone reviewing the issue cannot access.


If you're an experienced Bokeh user who wants to give back, a great place to start is supporting your fellow users on the Bokeh Discourse. Questions of all levels are posted daily, and you may find that there are some for which your experience is very valuable!

Similarly, the Documentation is a great way to start as a Bokeh contributor. The docs are a living, changing body of work, improving all the time, and contributing here will also help you get accustomed to Bokeh's review and release process. For information on how to contribute to Bokeh's documentation, refer to the Documentation section of the Developers Guide.

Bokeh users (and maintainers!) appreciate seeing examples of Bokeh at work. If your organization has a project using Bokeh that you're willing to share, consider adding it to our Showcase! These projects serve as inspiration and examples to other users, and give meaningful insight to maintainers as to how people are using the library, which drives future development priorities.

For development on the Bokeh library itself, there is a Bokeh Developer Slack. The dev channels here are helpful when getting feedback on development ideas or insight into planned directions for future development. For usage questions, please use the Discourse instead of Slack.

If you're interested in working on bugfixes or feature development in Bokeh, take a look at our GitHub issue tracker to see what we could use help on. The issue tracker includes a "Good First Issue" label to identify entry points for someone new to developing for the project.

A weekly developer meeting happens every Wednesday at 10:00 US Central Time. Notes from previous meetings can be found on GitHub.

Finally, as an open source project, Bokeh is funded by donations from both individuals and organizations who recognize the importance of the project to their work. Financial contributions