BEP 0: Bokeh Enhancement Proposals
Changes to major architectural features, development process, or release management require wide discussion and consensus. The documents that record the results of these discussions are "Bokeh Enhancement Proposals", abbreviated BEPs.
BEPs live on the GitHub wiki for the Bokeh project (i.e., right here). All BEPs should have a standard header at the top (except this one, which has the header below). This header must include the authors, the current status (WIP or Implemented), and a link to a corresponding GitHub issue for discussion. When appropriate a link to a PR implementing the BEP should also be included. For example:
| BEP 0 | Bokeh Enhancement Proposals |
|---|---|
| Authors | Bryan Van de Ven |
| Status | Implemented |
| Discussion | https://github.com/bokeh/bokeh/issues/1498 |
Acceptance or rejection of new proposed BEPs happens according to to the process codified in BEP 7: Decision Making.
BEP is to be pronounced /biːp/ (i.e., "beep")
If you have doubts about how to actually pronounce it, here you have a reference (we accept UK and US pronunciations): http://dictionary.cambridge.org/pronunciation/british/beep
Changes to this document shall be recorded below:
| Date | Change |
|---|---|
| 2014-12-02 | Implemented |
| 2020-08-19 | Update to reflect adopted decision making process |