BEP 4: Project Roles

Bryan Van de Ven edited this page Feb 13, 2019 · 8 revisions
BEP 4 Project Roles
Authors Bryan Van de Ven
Status Implemented
Discussion https://github.com/bokeh/bokeh/issues/8308

This document serves to define various roles within the Bokeh project.

Roles

Core Team

The Core Team is represented in the GitHub team @bokeh/core. The members of this team are responsible for the ongoing organizational maintenance and direction of the Bokeh project. Generally speaking, this includes:

  • Reviewing and merging Pull Requests from other contributors
  • Making and implementing decisions about project infrastrucure
  • Protecting and managing confidential project information such as service passwords
  • Handling all project financial matters (through NumFOCUS or otherwise)
  • Addressing reports related to the Community Code

It is desirable that at least one half of the NumFOCUS Bokeh project committee should be members of @bokeh/core at all times.

The current Core Team comprises:

Additionally, the service account bokeh-integrations which is used to allow external services to integrate with the Bokeh GitHub organization, is a permanent member of @bokeh/core.

Any member of @bokeh/core may request that they be removed, at any time, at which point they will be removed without discussion. All other changes to Core Team membership are decided by agreement of the current members.

Changes to Core Team membership should be recorded under the Revisions section at the bottom of this document.

Development Team

The Development Team is represented in the GitHub team @bokeh/dev. Due to the external circumstances, the Bokeh continuous integration infrastructure performs optimally only on branches directly on the main repository. The Development Team comprises active contributors who may submit pull requests from branches directly on the main repository. Development Team members are encouraged to:

  • Participate in GitHub discussions on issues and pull requests
  • Join occasional video conference meetings with other project members
  • Make at least one pull request to a Bokeh project annually

The minimum criteria for joining @bokeh/dev is acceptance of two substantive pull requests to a Bokeh project. Anyone meeting this threshold who also agrees to join, may be added to @bokeh/dev by any member of the core team, without discussion. Generally a core team members will try to extend an invitations when new contributors first become active, however users may also self-nominate themselves to any core team member.

Any member of @bokeh/dev may request that they be removed, at any time, at which point they will be removed by a core team member at the first opportunity. Additionally, if a user is inactive (defined as no submitted PRs or discussion participation) for more than one year, they may be removed by any member of the core team, without discussion.

Maintainers

Maintainers are members of the Development Team who are authorized to use the release deployment scripts to make "dev", "rc", or full releases of Bokeh. The membership of this team is defined by the MAINTAINERS file, which is checked whenever the release deployment scripts are run.

Membership is decided by agreement of the core team.

If a Maintainer leaves the Development Team, they will also be removed from the MAINTAINERS file. A Maintainer may also request to step down at any time, with or without leaving the development team.

Any changes to the MAINTAINERS file should occur in a dedicated Pull Request that includes any relevant discussion or information.

Revisions

Changes to this document, including updates to the Core Team membership, shall be recorded below:

  • 2019-02-12 Philipp Rudiger added to the Core Team
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.