|
| 1 | +# Governance |
| 2 | + |
| 3 | +## Technical Committee |
| 4 | + |
| 5 | +Technical committee provides technical oversight for the overall architectural design and project development. |
| 6 | + |
| 7 | +Responsibilities include: |
| 8 | + |
| 9 | +* Oversee the overall direction of the Kepler project |
| 10 | +* Provide guidance for the project maintainers and the onboarding process for new maintainers |
| 11 | +* Actively engage in the technical committee meetings |
| 12 | + |
| 13 | +The current list of technical committee members is published and updated in [Contributors.md](Contributors.md). |
| 14 | + |
| 15 | +### Becoming a Technical Committee Member |
| 16 | + |
| 17 | +Proficient in one or more of the following areas: |
| 18 | +* Developing and maintaining Kepler core |
| 19 | +* Developing and maintaining Kepler deployment and integration (including Operator) |
| 20 | +* Developing and maintaining Kepler model server and models |
| 21 | +* Developing and maintaining test suites |
| 22 | +* Developing and maintaining CI infra |
| 23 | +* Maintaining documentation. |
| 24 | + |
| 25 | +# Responsibilities |
| 26 | + |
| 27 | +## Maintainer's Responsibilities |
| 28 | + |
| 29 | +Responsibilities include: |
| 30 | + |
| 31 | +* Strong commitment to the project |
| 32 | +* Participate in design and technical discussions |
| 33 | +* Contribute non-trivial pull requests |
| 34 | +* Actively attend the community meetings |
| 35 | +* Perform code reviews on other's pull requests |
| 36 | +* Regularly triage GitHub issues. |
| 37 | +* Make sure that ongoing PRs are moving forward at the right pace or closing them |
| 38 | +* Monitor Kepler Slack (delayed response is perfectly acceptable), particularly for the area of your expertise |
| 39 | + |
| 40 | +## Reviewer's Responsibilities |
| 41 | + |
| 42 | +Responsibilities include: |
| 43 | + |
| 44 | +* Perform code reviews on other's pull requests |
| 45 | +* Regularly triage GitHub issues. |
| 46 | +* Make sure that ongoing PRs are moving forward at the right pace or closing them |
| 47 | +* Monitor Kepler Slack (delayed response is perfectly acceptable), particularly for the area of your expertise |
0 commit comments