Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions docs/BOUNTY_GUIDELINES.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# Fix for Issue #95: Frantic bounty #44: Audit Frantic bounty copy for worker clarity

# Frantic Bounty Guidelines

## For Workers: Understanding Bounties

### What is a Bounty?
A bounty is a funded task with a fixed price. When you complete the work successfully, you receive the listed payment.

### Bounty Structure
Each bounty includes:
- **Title**: A brief description of the task
- **Worker Price**: The amount you'll be paid upon successful completion
- **Slots**: Number of workers who can claim this bounty (usually 1)
- **Claim Link**: Where to officially claim the bounty
- **Funding Receipt**: Proof that the bounty is funded and legitimate

### How to Claim a Bounty
1. Review the bounty requirements thoroughly
2. Click the "Claim" link to reserve your slot
3. Complete the work as specified
4. Submit your solution via pull request
5. Once approved, payment is processed

### Key Terms
- **Funded**: The bounty has money allocated and is ready to be worked on
- **Available**: The bounty is open for claims
- **Slots**: How many workers can work on this bounty simultaneously
- **Effort**: Estimated time/complexity (when provided)

### Tips for Success
- Read the entire bounty description before claiming
- Ask clarifying questions if requirements are unclear
- Submit complete, production-ready solutions
- Follow the repository's contribution guidelines

## Questions?
If any bounty copy is unclear, please open an issue for clarification before starting work.
57 changes: 57 additions & 0 deletions docs/WORKER_GUIDE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
# Fix for Issue #95: Frantic bounty #44: Audit Frantic bounty copy for worker clarity

# Worker Guide for Frantic Bounties

## Quick Start

### Step 1: Find a Bounty
Browse available bounties in the GitHub Issues labeled `bounty` + `available`.

### Step 2: Understand the Requirements
Each bounty issue contains:
- A clear task description
- The payment amount (Worker price)
- Links to claim and verify funding

### Step 3: Claim Your Spot
Click the **Claim** link in the bounty to reserve it. This prevents others from working on the same task.

### Step 4: Do the Work
- Fork the repository
- Create a feature branch
- Implement the solution completely
- Test your changes

### Step 5: Submit
Open a Pull Request referencing the bounty number (e.g., "Closes #44").

### Step 6: Get Paid
Once your PR is reviewed and merged, payment is processed through Frantic.

---

## Common Questions

**Q: What does "Slots: 1" mean?**
A: Only one person can claim and complete this bounty.

**Q: How do I know a bounty is legitimate?**
A: Check the Funding Receipt link - it confirms money is allocated.

**Q: What if requirements are unclear?**
A: Comment on the GitHub issue asking for clarification before claiming.

**Q: What's the source of truth?**
A: Frantic (gofrantic.com) is authoritative. GitHub issues mirror bounty information.

---

## Glossary

| Term | Meaning |
|------|---------|
| Worker price | Amount paid to you upon completion |
| Slots | Number of available claims |
| Funded | Money is allocated for this bounty |
| Available | Bounty can be claimed now |
| Claim | Reserve the bounty to work on it |