> For the complete documentation index, see [llms.txt](https://handbook.chaoss.community/community-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.chaoss.community/community-handbook/badging/roles-and-responsibility/reviewer.md). # Reviewer ## Responsibilities The reviewer role would belong to people who would be responsible for reviewing the details submitted by an applicant. Reviewers will have access to the review checklist. The review checklist is a reviewing guide, which is a list written in Markdown, detailing the criteria a submission has to be measured against. ## GitHub Permissions {% hint style="info" %} Repository permission level: Write {% endhint %} Reviewers will be able to: * Edit their own comments. * Edit the Review Checklist. Reviewers will explicitly not be able to: * Edit an applicant's comment. ## FAQ `Q` What kind of commitment is reviewing for Event Badging?\ `A` We see a lot of variables affecting this time commitment, including our number of reviewers and the number of applicants. We expect, at the highest load, for the project to require about 20 minutes every few days from each reviewer. At lowest, we'd expect 20 minutes or so every few weeks. `Q` We are looking forward to answering more questions! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://handbook.chaoss.community/community-handbook/badging/roles-and-responsibility/reviewer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.