Written by Table of contents
- Write fundable issues
- A template for defining the task
- Prefer acceptance criteria over assumptions
- Track progress in the repo
- Where to go next
- Example acceptance criteria
- If the work already exists
- Ownership and changes
To fund a task, paste the link to an existing GitHub issue and set a bounty. The issue itself is still where the work gets defined and discussed — Gitpay doesn’t replace that, it adds a bounty and a payment flow on top of it.
Write fundable issues
Good funded issues are:
- Small enough to deliver
- Unambiguous and testable
- Clear about what is in/out of scope
A template for defining the task
Issues that are easy to fund — and easy for a contributor to pick up without back-and-forth — usually answer the same handful of questions:
- Why this task. What’s the motivation? What happens once it’s done?
- Level. Is this beginner, intermediate, or advanced? This helps the right contributor claim it.
- Current behavior. What’s happening now, and how can someone reproduce it?
- Expected behavior. What should happen instead once the change ships?
- Useful links. Related issues, discussions, or references that add context.
Prefer acceptance criteria over assumptions
Add explicit criteria (bullet list), plus example inputs/outputs when possible.
Track progress in the repo
Ask contributors to submit work via Pull Request so you can review changes and see automated checks.
Where to go next
- Read Fund an Issue for the full sponsor workflow.
- Once a contributor delivers, see How our payment works and Releasing bounties.
Example acceptance criteria
For a login bug, useful criteria might be: reproduce the failure with a test, make login succeed for the affected case, preserve existing valid login behavior, and document how the reviewer can verify it. The issue should state any browser or environment constraints.
If the work already exists
A project may want to pay for a contribution that began through normal collaboration. Discuss the value, amount, and payment route with the contributor. Do not add a bounty and assume an earlier contribution is automatically assigned or payable. See What is Gitpay? for this broader vision.
Ownership and changes
Name the reviewer and funding owner. If the scope changes, update the issue and confirm the payment expectation before asking for more work. Continue with Validating work and Releasing bounties.
