Skip to content

Latest commit

 

History

History
45 lines (31 loc) · 1.6 KB

GOVERNANCE.md

File metadata and controls

45 lines (31 loc) · 1.6 KB

Governance

Technical Committee

Technical committee provides technical oversight for the overall architectural design and project development.

Responsibilities include:

  • Oversee the overall direction of the Kepler Operator project
  • Provide guidance for the project maintainers and the onboarding process for new maintainers
  • Actively engage in the technical committee meetings

The current list of technical committee members is published and updated in Contributors.md.

Becoming a Technical Committee Member

Proficient in one or more of the following areas:

  • Developing and maintaining Kepler Operator deployment and integration
  • Developing and maintaining test suites
  • Developing and maintaining CI infra
  • Maintaining documentation.

Responsibilities

Maintainer's Responsibilities

Responsibilities include:

  • Strong commitment to the project
  • Participate in design and technical discussions
  • Contribute non-trivial pull requests
  • Actively attend the community meetings
  • Perform code reviews on other's pull requests
  • Regularly triage GitHub issues.
  • Make sure that ongoing PRs are moving forward at the right pace or closing them
  • Monitor Kepler Slack (delayed response is perfectly acceptable), particularly for the area of your expertise

Reviewer's Responsibilities

Responsibilities include:

  • Perform code reviews on other's pull requests
  • Regularly triage GitHub issues.
  • Make sure that ongoing PRs are moving forward at the right pace or closing them
  • Monitor Kepler Slack (delayed response is perfectly acceptable), particularly for the area of your expertise