Project Members
The YuniKorn community is open, diverse, and collaborative. It is not owned by any entity. Project members share the responsibility to manage, and maintain the project. People in the community include Project Management Committee (PMC) members and committers.
PMC
| Public Name | ApacheID | Organization | Timezone (UTC) |
|---|---|---|---|
| Akhil PB | akhilpb | Cloudera | +5.5 |
| Arun Suresh | asuresh | Oracle | -8 |
| Carlo Curino | curino | Microsoft | -8 |
| Chaoran Yu | yuchaoran | Apple | -8 |
| Chenya Zhang | chenya | Apple | -8 |
| Craig Condit | ccondit | Cloudera | -6 |
| DB Tsai | dbtsai | Apple | -8 |
| Felix Cheung | felixcheung | SafeGraph | -8 |
| Holden Karau | holden | Netflix | -8 |
| Jason Lowe | jlowe | NVIDIA | -6 |
| Jonathan Hung | jhung | -8 | |
| Junping Du | junping_du | Huawei | 0 |
| Kinga Marton | kmarton | Cloudera | +1 |
| Konstantinos Karanasos | kkaranasos | Microsoft | -8 |
| Luciano Resende | lresende | Apple | -8 |
| Manikandan R | mani | Cloudera | +5.5 |
| Peter Bacsko | pbacsko | Cloudera | +1 |
| Subramaniam Krishnan | subru | Microsoft | -8 |
| Sunil Govindan | sunilg | Cloudera | -8 |
| Tao Yang | taoyang | Alibaba | +8 |
| Tingyao Huang | tingyao | TrendMicro | +8 |
| Vinod Kumar Vavilapalli | vinodkv | Cloudera | +5.5 |
| Wangda Tan | wangda | Snowflake | -8 |
| Wei-Chiu Chuang | weichiu | Cloudera | -8 |
| Weiwei Yang | wwei | Apple | -8 |
| Wilfred Spiegelenburg | wilfreds | Cloudera | +11 |
Committer
The listing below excludes the PMC members
| Name | ApacheID | Organization | Timezone (UTC) |
|---|---|---|---|
| Chia-Ping Tsai | chia7712 | Is-Land | +8 |
| Li Gao | ligao | Databricks | -8 |
| Rainie Li | rainieli | -8 | |
| Ted Lin | steinsgateted | NCKU | +8 |
| Yu Teng Chen | yuteng | NTCU | +8 |
Become a Committer
Committers are the community members who have the write access to the project's repositories, i.e they can modify the code by themselves and accept others contributions to all YuniKorn repos. There is no strict rules about the qualification of a candidate. The PMC votes for a candidate based on various considerations:
Code contributions
- Consistent code contributions
- Optimize the CI/CD pipeline
- Help with the code reviews
- Test and verify release candidates
- Performance tuning and related tools development
- Propose improvement proposals
Non-code contributions
- Involvement in the community activities, such as meetings, meetups, etc.
- Provide feedback, report issues, and participate in roadmap discussions
- Help on project releases
- Improve project documentation
- Help the project adoption
- Integrate with other projects, extend the use cases
Contributor or non-contributor can both make their paths to committer, the community deeply appreciates both code or non-code contributions.
Become a PMC member
PMC stands for the Project Management Committee. It is responsible for project management, governance and ensures the project can be operated under the Apache Way. The committee makes decisions based on the PMC members' votes. A PMC member has the authority to cast a binding vote on various things, such as project releases, adding new committer or PMC member, etc.
A contributor must become a committer first before becoming a PMC member. There is no strict rules of when a committer will be qualified for being added to PMC. The management committee makes a decision based on the involvement and impact of each committer. In general, a committer who makes consistent code or non-code contributions to the project should be considered as a PMC candidate.