> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/community.md).

# Community

Join the MOSIP community!

MOSIP thrives on the collective efforts of its global community. Contributions from developers, designers, researchers, and organizations play a vital role in enhancing the platform’s capabilities and ensuring scalability, security, and interoperability.

### 🙌 Ways The Community Contributes

* Direct code contributions.
* Design and architecture reviews.
* Bug identification and fixes.
* Technology evaluation support.
* UI/UX design improvements.
* Documentation.

### 🤝 How Do I Contribute?

* **Getting Started**: Follow the [Contributor Wiki Guide](https://github.com/mosip/mosip/wiki) to learn how to get started with MOSIP contributions.
* **Explore MOSIP**: Browse the [MOSIP Docs](https://docs.mosip.io/1.2.0) and [GitHub Repositories](https://github.com/orgs/mosip/repositories) to understand the platform and identify where you can contribute.
* **Pick a Contribution**: Explore the [GitHub Issues and Feature Boards](https://github.com/orgs/mosip/projects?query=is%3Aopen) to find tickets you can pick up and contribute to, or pick from any existing feature list from our [Roadmap](https://docs.mosip.io/1.2.0/roadmap-and-releases/roadmap) or feel free to suggest a new one via GitHub [Issues](https://github.com/orgs/mosip/projects/8). You can contribute across code, design, documentation, testing, and community engagement.
* **Review Contribution Guidelines**: Refer to the [Code Contribution Guide](https://github.com/mosip/mosip/wiki/Code-Contribution-Guidelines) for contribution standards, branching, development, and PR guidelines.
* **Submit, Collaborate & Refine**:
  * Fork the repository → Implement your changes → Submit a PR using the [PR Template](https://github.com/mosip/mosip/wiki/PR-Template) → Respond to reviewer feedback and refine your contribution.
  * Follow MOSIP's [Branching Strategy](https://github.com/mosip/mosip/wiki/Branching-Strategy) and get your development workflow right. For a sample workflow, [click here](https://github.com/mosip/mosip/wiki/Workflow-for-a-Project).
  * Ensure alignment with the [Checklists for Community Contributors](https://github.com/mosip/mosip/wiki/Checklists-for-Community-Contributors).
* **Understand the Release Process**: Learn how approved contributions move through release preparation, testing, stakeholder review, and final release, by referring [here](https://github.com/mosip/mosip/wiki/MOSIP-Release-Process).
* **Become a Contributor**: Once your contribution is approved and merged, you're officially a MOSIP contributor. Track your contributions on the [Contributor's Leaderboard](https://github.com/mosip/mosip/wiki/Contributor's-Leaderboard).
* **Need Help?**: Engage with us on our [Community Forum](https://community.mosip.io/) and collaborate with fellow contributors.

### 👉 Explore More

* [Contributors](https://docs.mosip.io/1.2.0/community/contributions) - See the organizations and community members contributing to MOSIP.
* [Documentation Credits](/1.2.0/community/documentation-credits.md) - View acknowledgements for contributors who have helped create and improve MOSIP documentation.
* [Code of Conduct](https://docs.mosip.io/1.2.0/community/code-contributions/code-of-conduct) - Understand the principles and expectations for participating in the MOSIP community.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mosip.io/1.2.0/community.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.