Bounty Program
Our bounty program is designed to encourage community contributions to OM1. It's also a great way to build a relationship with the OpenMind team if you're interested in deeper involvement with the project.
Bounties are open to everyone.
Individual Work
- Anyone can work on any issue.
- Multiple people can independently work on the same issue and each raise their own PR.
Team Work (Hard & Extreme Only)
- On Hard and Extreme level issues, participants are allowed to form teams.
- A team submits one PR together and must list all contributors.
Final acceptance is based on the quality and completeness of the submission, as decided by the OpenMind team.
You can find currently available bounties on our issue tracker. Each issue may have different requirements and scope, but the process to participate is consistent.
- All contributions must be submitted via GitHub Issues/PRs. If there are any changes you will be informed.
- Communication and support occur on GitHub Discussions, Discord and Telegram. You are free to join any of these channels or ask questions on concerned GitHub issues.
- Every new account is offered 50 OMCU to kick start your journey with OM1.
- Join the Telegram group
- Comment on the issue you're interested to work on.
- If you run into any issues, just ping us either on Discord/Telegram or the issue itself.
- Head over to OpenMind Portal, to create an account and generate your API key. Please create your OM1 account with the same email you used for your GitHub and Google form — this helps us verify your participation easily!
- When your work is complete, submit a PR and follow the instructions and submission guidelines mentioned on the Issue. We’ll review it and reach out if we need additional details before we merge it.
While using LLMs for assistance is acceptable, solutions that heavily rely on LLM-generated content without proper review and understanding are not acceptable. Contributors must:
- Understand and be able to explain their code
- Review and verify LLM outputs for accuracy
- Ensure code quality and maintainability
- Add appropriate documentation and tests
- Code must be well-organized, maintainable, and properly tested
- Clear commit messages explaining your thought process are essential
- Follow the instructions and deliverables mentioned on the issue you are working on
| Criteria | Description | Weight |
|---|---|---|
| Functionality | Does the submission work as intended? | 40% |
| Innovation | Novelty and creativity of the solution | 15% |
| Usability & Documentation | Ease of use, clear instructions | 20% |
| Impact & Reusability | Contribution’s value to the OM1 ecosystem | 15% |
| Presentation | Quality of demo, screenshots, or video | 10% |
We deeply value our contributors. To celebrate community effort, we’ll be introducing a contributor leaderboard to highlight those making an impact. In addition to visibility within the community, active contributors can also expect exclusive perks and rewards. We’re keeping the details under wraps for now, but early participants will be the first to benefit as the program evolves.
Contributors will be assigned a developer badge with 4 different levels, based on their contribution. Here's a glimpse of it.
Badges are a recognition mechanism based on impactful contributions, not the number of merged PRs. A merged PR does not automatically guarantee a badge.
The evaluation process and specific metrics remain proprietary to prevent system exploitation and are adjusted at OpenMind’s discretion to ensure long-term fairness across various contribution types.
All contributions must be licensed under the MIT License, consistent with the project's licensing terms. For reference, see our LICENSE file.
- Read our Developer Guide before starting
- Make sure you read Contribution Guidelines and Code of Conduct
- Follow our coding standards and documentation practices
- Test your code thoroughly
- Engage with maintainers if you have questions
- Keep your PR focused and well-documented