Skip to content

📣⚠️ Lux Framework Bounty Program Guidelines ⚠️📣 #104

@rparcus

Description

@rparcus

Lux Framework Bounty Program

Overview

The Lux Framework bounty program is designed to incentivize and reward developers for contributing to specific features and improvements. This guide outlines the process, expectations, and guidelines for participating in the program.

Bounty Process

1. Finding Bounties

  • Bounties are marked with specific amounts in issue titles (e.g., 'Feature X $500')
  • Initial bounty amounts are indicative and subject to adjustment based on final scope
  • Check the 'bounty' label in our issue tracker for available opportunities

2. Before Starting Work

  1. Express Interest

    • Comment on the issue you're interested in
    • Join our Discord community and come hangout in the #dev-chat
    • Reach out to the team in the here or via that server/channel
  2. Scope Discussion

    • Schedule a brief chat with the team to discuss:
      • Your experience and approach
      • Detailed requirements and expectations
      • Timeline and milestones
      • Final bounty amount confirmation
  3. Assignment

    • Wait for official assignment from the team
    • The team will update the issue with your username
    • A 'in-progress' label will be added

3. During Development

  • Provide regular updates (at least weekly) on the issue
  • Raise any questions or blockers early
  • Follow our contribution guidelines
  • Create draft PRs early to get feedback

4. Completion & Payment

  • Submit your final PR for review
  • Address any feedback from the team
  • Once approved and merged, payment will be processed
  • Payments are typically made within 5 business days of merge

Important Guidelines

🚫 What to Avoid

  • Starting work without official assignment
  • Working on an issue already assigned
  • Making significant scope changes without discussion
  • Long periods without updates

✅ Best Practices

  • Read all documentation thoroughly
  • Ask questions if requirements are unclear
  • Follow code style and testing guidelines
  • Keep communication open and professional

Bounty Adjustments

  • Initial bounty amounts are estimates
  • Final amounts may be adjusted based on:
    • Actual scope of work
    • Quality of implementation
    • Additional features/improvements
    • These adjustments will be discussed and agreed upon before work begins

Support

  • Technical questions: Use issue comments
  • Process questions: Here, github discussions page or Discord
  • Urgent matters: Tag maintainers in the issue

Legal Notes

  • All contributions must follow our license terms
  • Payments are subject to applicable laws and regulations

FAQ

Q: Can I work on multiple bounties?
A: Yes, but excluding special cases you should complete one before we can assign you another.

Q: What if someone else starts working on my assigned issue?
A: Only officially assigned developers should work on an issue and will be eligible to bounties. Others' PRs will not be accepted.

Q: How are bounties paid?
A: Payment details will be discussed during the initial scope chat.

Q: What if the scope changes during development?
A: Significant scope changes will be discussed and may result in bounty adjustments.


By participating in the bounty program, you agree to these guidelines. The Spectral team reserves the right to modify these guidelines as needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions