Qualified new maintainers are approved via consensus by the group of existing maintainers.
Technical committee provides technical oversight for the overall architectural design and project development.
Responsibilities include:
- Oversee the overall direction of the Kepler 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.
Proficient in one or more of the following areas:
- Developing and maintaining Kepler core
- Developing and maintaining Kepler deployment and integration (including Operator)
- Developing and maintaining Kepler model server and models
- Developing and maintaining test suites
- Developing and maintaining CI infra
- Maintaining documentation.
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
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