This post outlines the review and reassignment process for code bounties. For general information about how our bounty program works, compensation tiers, and how to get started, see the Midnight Content Bounty Program announcement.
Submission Process
Before you start, check the issue description for full details on deliverables.
Content Categories:
| Type | What to do |
|---|---|
| Video | Share a link to your draft (Google Drive, unlisted YouTube, etc.) for review before publishing |
| Blog post | Share your draft in this issue thread for review before publishing |
| Documentation | Submit a PR to the docs repo and share the link here for review |
| Code | Submit a PR to the relevant repo and share the link in the issue thread for review |
Important: When you’re ready for formal review, explicitly state “Ready for review” in your comment. Progress updates are encouraged, but only submissions marked as ready will count toward your two review rounds.
Do not publish or merge anything without sign-off from a reviewer. We’ll provide feedback and let you know when it’s approved.
Review Process
Every code submission goes through a technical review before approval. We use a structured feedback cycle:
- Round 1: Initial review with specific, actionable feedback on what needs to change.
- Round 2: Follow-up review after your revisions. If issues remain, you’ll receive final guidance on what’s needed for approval.
- Round 3: If the submission still doesn’t meet requirements, the bounty will be reassigned to another contributor.
Two review cycles give you a fair opportunity to address feedback while keeping the program moving for everyone.
Reassignment Criteria
A bounty will be reassigned when:
- No weekly update has been posted for 7+ days
- Requirements not met after two rounds of review
- Feedback is not addressed — revisions must demonstrate understanding of the feedback provided
- Non-functional submissions — empty files, placeholder code, or code that doesn’t run will not be accepted
- Unresponsive contributor — no reply to reviewer comments within a reasonable timeframe
After Reassignment
When a bounty is reassigned, you’re welcome to request assignment on other open issues. Reassignment isn’t personal; it’s about keeping the program fair and efficient for all contributors.
Questions
If you’re unsure about feedback or requirements, ask in the issue thread before submitting. We’d rather clarify upfront than go through unnecessary review cycles.