Skip to content

Commit 4857389

Browse files
committed
add governance and contributors
1 parent 4d88c3e commit 4857389

File tree

2 files changed

+68
-0
lines changed

2 files changed

+68
-0
lines changed

Contributors.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Maintainers
2+
| Name | GH ID | Expertise | Affiliation | Location |
3+
|---|---|---|---|---|
4+
| Huamin Chen | rootfs | Kepler Core | Red Hat | USA |
5+
| Marcelo Carneiro do Amaral | marceloamaral | Kepler Core | IBM | Japan |
6+
| Sunyanan Choochotkaew (Pang) | sunya-ch | Kepler Core | IBM | Japn |
7+
| Ji Chen | jichenjc | Testing | IBM | China |
8+
| Sam Yang | SamYuan1990 | CI | IBM | China |
9+
| William Caban Babilonia | williamcaban | Kepler Deployment | Red Hat | USA |
10+
| Kayi Liu | KaiyiLiu1234 | Kepler Model Server | Red Hat | Cananda |
11+
| Parul Singh | husky-parul | Kepler Deployment and Documentation | Red Hat | USA |
12+
| Chen Wang | wangchen615 | Kepler Core | IBM | USA |
13+
14+
# Reviewers
15+
| Name | GH ID | Expertise | Affiliation | Location |
16+
|---|---|---|---|---|
17+
| Huo Qi Feng | huoqifeng | Kepler Deployment | IBM | China |
18+
| Filip Skirtun | Feelas | Kepler Deployment | Intel | Poland |
19+
| Lu Ken | kenplusplus | Kepler Deployment | Intel | China |
20+
| Sally O'Malley | sallyom | Kepler Deployment | Red Hat | USA |
21+
| Ruomeng Hao | ruomengh | Kepler Deployment | Intel | China |

GOVERNANCE.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
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

Comments
 (0)