The package is developed and used by the community.
TVM Contributors
================
TVM adopts the Apache style model and governs by merit. We believe that it is important to create an inclusive community where everyone can use,
contribute to, and influence the direction of the project. We actively invite contributors who have earned the merit to be part of the development community.
We actively seek committers that come from community contributors who:
- Made substantial contributions to the project.
- All forms of contributions are valued (see detail in next section).
- Maintain quality standards in contributions
- e.g. consistently made contributions without requiring extensive
rewrites prior to being merged.
- Willing to spend time on maintaining and lead the project.
See the [community structure document](http://tvm.ai/contribute/community.html) for the explanation of community structure and contribution guidelines.
Contributions
-------------
We value all forms of contributions, here is a non-comprehensive
list of contributions that are welcomed
- Documentation and usage examples
- Community participation, answering questions and issues.
- Code readability and developer guide
- We welcome contributions that add code comments
to improve readability
- We also welcome contributions to docs to explain the
design choices of the internal.
- Test cases to make the codebase more robust
- Tutorials, blog posts, talks that promote the project.
How to Contribute
-----------------
See [Contributor guide](http://tvm.ai/contribute/) on tips for contributions.
Committers
----------
Committers are people who have made substantial contribution to the project and granted write access to the project.
-[Tianqi Chen](https://github.com/tqchen), University of Washington
## Committers
-[Tianqi Chen](https://github.com/tqchen)(PMC), University of Washington
-[Thierry Moreau](http://homes.cs.washington.edu/~moreau/), University of Washington
-[Haichen Shen](http://homes.cs.washington.edu/~haichen/), University of Washington
-[Ziheng Jiang](https://github.com/ZihengJiang), Fudan University
-[Haichen Shen](http://homes.cs.washington.edu/~haichen/), University of Washington
Code Owners
-----------
[Code owners](CODEOWNERS) are people who make substantial contribution to a module
and are qualified to lead development and review changes of the owned module.
TVM adopts the Apache style model and governs by merit. We believe that it is important to create an inclusive community where everyone can use, contribute to, and influence the direction of the project. We actively invite contributors who have earned the merit to be part of the development community. There are several roles in the community:
- Project Management Committee(PMC) Small group of active committers that moderate the discussion, RFC, manage project releases.
- Committer Individual who has made substantial contributions to the project and is granted write access to the project and oversees the general direction of the projects.
- Code Owner Individual who is responsible for a specific area of the codebase.
- Reviewer Individual who is qualified to review for a specific area of the codebase.
- Contributor Anyone who contributes to the project.
This document explains responsibility and criteria for each role.
See [CONTRIBUTORS.md](https://github.com/dmlc/tvm/blob/master/CONTRIBUTORS.md) for the current list of contributors and their roles.
## Project Management Committee
The PMC consists of a small group of active committers that moderate the discussion, provide mentorship to committers and code owners and manage the project release. PMC members need to actively manage the general project directions. Note that most major design choices and proposed changes should reach consensus among committers.
## Committer
Committers are individuals who are granted the write access to the project. Committers oversee the general project directions and participates in the evaluation of the RFCs involving major design changes. We look for the following traits from potential comitters
Own at least one module in the project
Good understanding of general project structure, demonstrated by discussion over RFCs, code reviews and proposals of new features
Active history of code reviews that demonstrate a good technical ability
Contribution history of high-quality documentation and tutorials to the promote project
History of creating clean, maintainable code and including good test cases.
New committers are nominated by current committers from current code owners by providing evidence of these perspectives.
## Code Owner
A code owner is an individual who is responsible for a specific area of the code-base. Code owners are responsible for the areas they are in charge of and oversee the code review process of the corresponding module. Changes to a specific area need to be approved by one of its owners in order to be merged. Once a pull request is approved by the designated code owner, the code can be directly merged into the repo.
Code owners are promoted from contributors. In order to become code owner, one needs to make substantial contributions to a module. A candidate for code owner also needs to demonstrate good code quality, testing, and documentation in specific areas. These traits of code owners are essential for a high quality and healthy codebase. These traits are evaluated by the contributor’s participation in the project, including, but not limited to:
High-quality, readable code contributions indicated by pull requests that can be merged without a substantial code review
Good coverage of tests and documentation in the contributions
Informative code reviews to help other contributors that adhere to a good standard, spot problems in contributions etc.
Active participation in the discussion forum
## Reviewer
A reviewer is an individual who actively contributed to the project and is willing to participate in the code review of new contributions. We invite reviewers from active contributors. The reviewer invitation will be sent to the potential reviewer’s email, so please log in to the discussion forum so that we can know which email address we could send an invitation to. Code owners should actively seek reviews from reviewers. High-quality code reviews prevent technical debt for long-term and are crucial to the success of the project. A pull request to the project has to be reviewed by a reviewer in order to be merged. The contributor and code owner can request code reviews from multiple reviewers. Code owner can decide if the code can be merged in case by case if some of the reviewers did not respond in time(e.g. a week) and existing reviews are sufficient. A good way to get quick reviews from others in the community is to also help to review other’s code -- so they can do the same in return.
