> 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/applicant.md).

# Applicant

## Responsibilities

Applicants would be the primary stakeholders for any CHAOSS Badging review. They will be responsible for:

* Applying for a CHAOSS D\&I Badge.
* Improving their application according to reviewer feedback.
* Provide a point of contact between their own community and CHAOSS.

## GitHub Permissions

{% hint style="info" %}
Repository permission level: Read
{% endhint %}

Applicants will be able to:

* Submit an application for a Badging review.
* Edit details and make improvements in their application.

Applicants will explicitly not be able to:

* Edit the Review Checklist.

## FAQ

`Q` What kind of commitment is the application process for an Event Badge?\
`A` The initial form will likely take about 15 minutes to fill out. After submitting your application, you are required to communicate, at least a few times, to ensure that the information is accurate and confusion is resolved. You must also confirm that the badge your event receives is clear.

`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/applicant.md?ask=<question>&goal=<endgoal>
```

`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.