Add become a committer doc.

Author: csyonghe

community/become-a-committer.md

@@ -1,3 +1,52 @@
 # Become a Slang Committer
 
-[//]: # (TODO: link more internal documentation about how to become a slang committer.)
+Becoming a committer is a significant step, as it gives you direct access to the repository, enabling you to merge changes, review code, and help shape the future of the project. Below are the expectations and process for becoming a committer in Slang.
+
+## Show Consistent Contribution Quality
+Your journey to becoming a committer starts with consistent, high-quality contributions to the Slang codebase. This typically includes:
+
+Frequent, Meaningful Contributions: Regularly submit contributions, whether they are features, bug fixes, or performance improvements. Each contribution should align with Slang’s goals and maintain the bar of code quality.
+High-Impact Contributions: Aim to contribute changes that significantly benefit the project, such as optimizations, core feature enhancements, or critical bug fixes. Contributions that demonstrate a deep understanding of Slang’s architecture and design are highly valued.
+
+## Engage in Code Reviews
+In open-source projects, reviewing others’ code is as important as submitting your own. Before becoming a committer, you should:
+
+*Participate in Code Reviews:* Actively participate in code reviews by providing insightful feedback. Look for issues in logic, style, performance, and alignment with Slang’s objectives.
+
+*Help Raise the Code Quality:* Encourage adherence to Slang’s standards and practices by providing constructive feedback. The ability to review others’ code with a critical yet supportive approach is essential for committers.
+
+## Build Trust and Collaboration
+Committer status is granted based on the trust that you are deeply committed to Slang’s success. You can demonstrate this by:
+
+*Being Reliable and Responsive:* Maintain a regular and responsive presence in the project, whether in pull requests, discussions, or reviews.
+
+*Work Well with Others:* Slang is a community effort, so committers are expected to work well with other contributors, listen to feedback, and adapt where needed.
+
+*Take Ownership of Work:* Show a sense of responsibility by following up on contributions and addressing issues that arise in areas of the code you’ve worked on.
+
+## Demonstrate Technical Understanding of Slang
+To maintain and develop the Slang codebase, committers need a comprehensive understanding of its internals. Demonstrate that you:
+
+*Understand Slang’s Architecture:* Learn and follow Slang’s core architecture, coding patterns, and design principles.
+
+*Know the Shading Language and Compiler Space:* Familiarize yourself with shading languages and compilers in general. This domain knowledge helps you contribute effectively and make informed decisions as a committer.
+
+## Maintain a Record of High-Quality Contributions
+Consistent quality and dedication are key criteria. Committers typically have:
+
+*A History of Reviewed Contributions:* Have at least 10 high-quality patches merged, with a record of thorough and constructive review feedback.
+
+*Positive Reviewer Feedback:* Accumulate reviews from existing committers that acknowledge your contribution quality and readiness.
+
+## The Committer Nomination Process
+
+Once you meet the criteria above, you can nominate yourself to become a committer. This process includes:
+
+*Nomination:* You can nominate yourself to become a committer by creating a discussion thread on GitHub discussions. 
+
+*Internal Review:* Existing committers will review your contributions, code review feedback, and responsiveness to determine your readiness.
+
+*Final Approval:* Upon a positive consensus, you will be granted committer status along with write access to the Slang repository.
+
+Becoming a committer is a meaningful responsibility, and we value contributors who are invested in maintaining and advancing Slang. Thank you for your continued contributions, and we look forward to welcoming you as a committer!
+

community/index.md

@@ -19,11 +19,11 @@ report issues, start discussion threads, or submit pull requests.
 
 #### Committer
 
-A committer is a community member who can review and approve pull requests. This is a status that can be earned by maintaining a track record of submiting and landing code changes to the Slang project. All community members can review code submitted by other community members, but for a pull request to be considered approved and ready for merging, at least one **owner** (more info below) of each file you are touching must provide an approving review. Ideally a committer should choose reviewers who are familiar with the area of code you are touching. If you have doubts, look at the git blame for the file and the OWNERS files.
+A committer is a community member who has write access to the Slang repository and can approve pull requests. This is a status that can be earned by maintaining a track record of submiting and landing code changes to the Slang project. All community members can review code submitted by other community members, but for a pull request to be considered approved and ready for merging, at least one **owner** (more info below) of each file you are touching must provide an approving review. Ideally a committer should choose reviewers who are familiar with the area of code you are touching. If you have doubts, look at the git blame for the file and the OWNERS files.
 
 Submissions to a repository by a change contributor who is not a Slang committer require two committers to approve the submission. If the author of the pull request is already a committer, then only one other committer is needed to review.
 
-If you think you might be ready to be a committer, ask one of the reviewers of your pull request or another committer familiar with your work to see if they will nominate you. They will discuss that in #slang-committers discord — two others in that will need to second the nomination. See the [detailed document](/community/become-a-committer) for this process.
+If you think you might be ready to be a committer, ask one of the reviewers of your pull request or another committer familiar with your work to see if they will nominate you. They will discuss that in #slang-committers discord — two others in that will need to second the nomination. See [how to become a committer here](/community/become-a-committer).
 
 #### Owner
 
@@ -36,13 +36,12 @@ A language owner is the owner of the [`/docs/proposals/`](https://github.com/sha
 ## Processes for Code Changes
 
 #### Process for Bug Fixes
-A bug fix starts with an GitHub issue describing the bug. Any community member can submit a pull request coming from your personal fork of Slang containing fixes for the bug. Such pull requests needs to be reviewed and approved by two committers who are owners of the files being changed by the pull request. Once the pull request is approved and passed all CI tests, it can be merged to the main branch. All pull requests are expected to meet
-our [bar of code quality](/community/code-quality).
+A bug fix starts with an GitHub issue describing the bug. Any community member can submit a pull request coming from your personal fork of Slang containing fixes for the bug. Such pull requests needs to be reviewed and approved by two committers who are owners of the files being changed by the pull request. Once the pull request is approved and passed all CI tests, it can be merged to the main branch. 
 
 #### Process for Slang Feature Changes
 
 Changes that add or modify syntax, language feature, Slang's core module, or the compilation and reflection API must go through our process for language changes. The full process is [documented here](/community/language-change-process).
 
 ## Submitting a Pull Request
 
-If you are ready to start contributing, please follow our [guide for creating a pull request](https://github.com/shader-slang/slang/blob/master/CONTRIBUTION.md).
+If you are ready to start contributing, please follow our [guide for creating a pull request](https://github.com/shader-slang/slang/blob/master/CONTRIBUTION.md). All pull requests are expected to meet our [bar of code quality](/community/code-quality).