Skip to content

BOUNTY.md

Latest commit

 

History

History
160 lines (108 loc) · 6.15 KB

BOUNTY.md

File metadata and controls

160 lines (108 loc) · 6.15 KB

💰 AutoBot Bounty Program

The AutoBot bounty program enables contributors to earn rewards for implementing features, fixing bugs, and improving the platform.

🎯 How the Bounty Program Works

All bounties are managed through Polar.sh, a platform that streamlines funding for open source projects.

Bounty-Eligible Issues

Issues marked with the bounty label are eligible for rewards. These typically include:

  • Feature Implementation — New functionality with clear requirements
  • Bug Fixes — Well-documented bugs affecting functionality or performance
  • Documentation — Technical guides, API docs, deployment guides
  • Infrastructure — CI/CD improvements, deployment automation, monitoring
  • Testing — Test coverage improvements, integration tests
  • Performance — Optimization work with measurable impact

Issues are tagged by difficulty:

  • good-first-issue — Ideal for new contributors, simpler scope
  • intermediate — Some experience required, moderate complexity
  • advanced — Deep system knowledge required, significant impact

Example Bounty Issues

Recent bounties include:

  • Implementing Kubernetes support for fleet management
  • Adding multi-user authentication and RBAC
  • Building advanced analytics dashboards
  • Improving documentation for enterprise deployments
  • Creating integration templates for third-party services

✅ Eligibility Criteria

To claim a bounty:

  1. Ownership — Post a comment on the GitHub issue claiming it (first come, first served)
  2. Approval — Wait for maintainers to confirm eligibility
  3. Implementation — Complete the work according to the issue requirements
  4. PR — Submit a pull request with the implementation
  5. Review & Merge — Work with maintainers on code review
  6. Payment — Payment is processed via Polar.sh after PR merge

Requirements for Contributors

  • All work must follow the CONTRIBUTORS.md guidelines
  • Code must meet AutoBot's quality standards (tests, documentation, linting)
  • PRs must be opened from your own fork
  • One bounty per contributor per issue (no team claims)
  • You retain copyright; AutoBot gets a perpetual license

💳 Payment Process

  1. Claim Issue — Comment on a bounty issue you want to work on
  2. Get Approved — Maintainers confirm your participation
  3. Do the Work — Implement the feature or fix per the requirements
  4. Submit PR — Open a pull request to the Dev_new_gui branch
  5. Code Review — Collaborate with maintainers on feedback
  6. Merged! — Once merged, your bounty is locked in
  7. Get Paid — Polar.sh processes payment within 7 days (typically)

Payment Options

Polar.sh supports multiple payment methods:

  • Direct Transfer — Bank transfer (varies by country)
  • PayPal — Direct to your PayPal account
  • Cryptocurrency — Bitcoin, Ethereum, USDC (if enabled)

You can configure your preferred payment method in your Polar.sh account dashboard.

📋 Claiming a Bounty: Step-by-Step

Step 1: Browse Available Bounties

Visit Polar.sh AutoBot Bounties to see all available rewards and their amounts.

Step 2: Comment on the GitHub Issue

Find the corresponding issue on GitHub and post a comment:

I'd like to claim this bounty. I have experience with [relevant skill] and can have a PR ready by [realistic date].

Step 3: Wait for Approval

A maintainer will confirm your participation. This typically happens within 24 hours.

Step 4: Implement the Feature

Follow the issue requirements and CONTRIBUTORS.md guidelines:

  • Use the feature/, fix/, or docs/ branch prefix
  • Write tests for your changes
  • Include documentation or docstrings
  • Follow the existing code style and patterns

Step 5: Open a Pull Request

Open your PR against the Dev_new_gui branch, not main:

git push origin feature/your-feature
# Then open PR on GitHub targeting Dev_new_gui

Include in your PR description:

  • Closes #issue-number
  • Description of changes
  • Any testing you've done

Step 6: Code Review

Work with maintainers on feedback:

  • Respond to comments promptly
  • Make requested changes in new commits (don't force-push)
  • Ask clarifying questions if needed

Step 7: Celebration 🎉

Once merged, your bounty payment is confirmed via Polar.sh. You'll receive payment in your preferred method within a week.

🤔 FAQ

Q: Can I work on a bounty if I'm already employed at a company?
A: Yes! Bounties are personal contributions. Just ensure there are no conflicts with your employment agreement.

Q: What if I claim a bounty but can't complete it?
A: Comment on the issue to let us know. We'll open it for other contributors. No penalty—just let us know early so others can help.

Q: How long do I have to complete a bounty?
A: There's no hard deadline, but most bounties expect completion within 2-4 weeks. Complex bounties may have longer expectations—check the issue for details.

Q: Are bounties only for code?
A: No! Bounties include documentation, infrastructure, testing, and more. Check the issue labels to see what types are available.

Q: How much do bounties pay?
A: Amounts vary based on complexity and scope. Check Polar.sh for specific bounty amounts.

Q: Can I claim multiple bounties?
A: Yes! But you can only work on one bounty per issue. You can participate in different issues.

Q: What if I disagree with feedback?
A: Code review discussions are collaborative. Please engage respectfully. If you have concerns, start a discussion with maintainers.

🚀 Getting Started

  1. Read CONTRIBUTORS.md for contribution guidelines
  2. Explore bounty opportunities
  3. Check the GitHub issue for requirements
  4. Comment to claim the bounty
  5. Get coding!

Questions? Open an issue in GitHub Discussions or reach out to maintainers.

Ready to earn? View all bounties →