Skip to content

Internal docs for planning / logging etc, now open sourced

Notifications You must be signed in to change notification settings

BountyHour/bounty-hour-docs

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Bounty Hour

What is it?

Bounty Hour is a micro-contracting marketplace, loosely based on the "bug bounty" system. Development teams who are unable to solve an issue (bug / issue / feature) and require a specialist can submit a bounty, that specialists can pick up. The bounty is only paid out when (or if) the work is completed, and may be attempted by multiple specialists. Each specialist only has 24hr to complete a bounty, after which it is freed up for another.

This system ensures development teams only pay when their problem is solved, whilst also providing an incentive for bounty hunters to complete tasks as efficiently as possible.

Hunting bounties is not intended as a full time job, or even a major income, but as a side hustle for software engineers with extra capacity. It is also not intended for full feature development, but for the occasional seemingly unsolvable problem.

Targeted vision

Developers

The vast majority of your job is probably building large new features or tidying up code. You might go entire weeks without actually doing anything new or challenging yourself.

Why not spend an hour of your time to do something challenging, and get paid extra for it?

Managers

Got a problem that's been plaguing you for months, and nobody on the team seems able to solve it? Instead of hiring a contractor for a week and hoping you get lucky, put out a BountyHour. Review verified experts, choose your requirements, and post. No fix, no fee.

Investors / employees

Low risk, as BH is just a middleman. Low overheads, high scalability. Ability to cross-sell / upsell easily to high-wealth individuals.

USP

What makes BountyHour different to all the other programming bounty sites?

  1. Scope: BountyHour is only for solving bugs, crashes, and problems. It's not for general software development.
  2. Private: Bounties have public metadata, but any detailed data is only shown to potential hunters, and code is only shown to an assigned hunter.
  3. All in one: Code management, communications, and payments all within the platform.
  4. Hunters: Instead of independent freelancers trying to earn a living, BountyHour mostly uses already employed people looking for an extra challenge.

Dictionary

  • Bounty: A micro-contract to solve a problem.
    • Draft: Partially prepared, but not listed yet.
    • Open: Listed, and able to be picked up.
    • In progress: Currently being worked on, nobody else can pick it up.
    • Submitted: Specialist has submitted their solution, it has not been accepted yet.
    • Completed: Submitter has accepted the solution, contract is complete. Optionally give bonus.
    • Failed: Specialist ran out of time, or manually gave up. Can now go back into "Open".
  • Users: Anyone who is taking part in Bounty Hour.
    • Moderators: Support, help handle any disputes, disagreements, etc.
    • Hunters: Those currently seeking out bounties.
    • Posters: Those posting bounties to be completed.

About

Internal docs for planning / logging etc, now open sourced

Resources

Stars

Watchers

Forks