parse-community / parse-community/parse-dashboard
🏆 Parse Bounty Program
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
Parse Bounty Program
The goal of the program is to facilitate product development by recycling community donations back into the contributor community and making paid contribution more accessible.
How does it work?
- Pick a GitHub issue with a bounty label, for example:

- Open a PR and get it merged
- Submit your expense claim directly to our Open Collective
Read the full program details here.
Which issues will have a bounty?
The program will start as a trial and be available in select repositories for select issues. Which issues will be selected depends on various factors, such as urgency, strategic importance, community demand, or to revive stale issues. Initially, the Project Management Committee will select issues for bounties, but in the long-term we envision a mechanism based on community feedback that applies bounties to issues automatically.
Can I quit my daily job?
Rather not; the purpose of the program is to give a small incentive to contributors to look at issues that need attention. The amount of compensation is not intended to reach a market-level salary. Think of the bounty to be a token of gratitude, or a way of saying:
Thanks for tackling this issue, enjoy a coffee paid for by the community!
Won't that hurt voluntary contribution?
We do not expect the program to discourage contributors from tackling issues that do not have a bounty. If however issues with a bounty get slightly more attention than issues without a bounty, that is exactly the effect the program aims to achieve.
Can I open an issue and receive a bounty?
Yes, you can receive a bounty if you submit a pull request for your own issue. However, whether a bounty is applied to your issue depends on various factors, see above.
Can I suggest issues for a bounty?
If you want to show your support for an issue, please do so by upvoting the issue on GitHub with a 👍, ❤️, 🚀 or 🎉 instead of posting a "+1" comment to suggest a bounty. We will consider these reactions when looking for issues that should have a bounty.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading Governance/BOUNTY.md, which contains the full program details linked from this issue. The issue names no implementation files or tests and has no concrete change or acceptance criterion, so the work is not ready to begin without defining the desired documentation or process update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100