-
Notifications
You must be signed in to change notification settings - Fork 15
Update Editorial Process #103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Adding a CONTRIBUTING.md file that outlines the editorial process for adding new content or modifying the existing Matter Handbook content.
|
Preview deployed at https://d2doqw88td69eq.cloudfront.net/pr-103 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a comprehensive CONTRIBUTING.md file, which is a great addition for clarifying the contribution process. The document is well-structured and covers all the essential aspects of the workflow. My review includes a few suggestions to correct some typos, improve grammatical correctness, and enhance overall clarity and consistency, which will help make the guide even more effective for contributors.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
Preview deployed at https://d2doqw88td69eq.cloudfront.net/pr-103 |
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
Preview deployed at https://d2doqw88td69eq.cloudfront.net/pr-103 |
📖 Description
This pull request adds a comprehensive
CONTRIBUTING.mdguide for the Matter Handbook, outlining the contribution process, workflow, and merge conditions. The new documentation clarifies how contributors should submit changes, how reviews and approvals work, and the roles involved in maintaining quality and domain expertise.Contribution Process and Workflow
Labels and Merge Conditions
editorial,tooling, domain labels,do not merge) and the gates required for each, including the requirement for subject-matter expert approval on domain changes.Roles and Review Discipline
📋 TODO
After the SC approves the process, the following tasks still need to be completed in follow-up PRs or as administrative work on GitHub: