Bounty hunting

A bounty consists of a piece of work that I would like to see done. A bounty can be claimed so that no one else will start working on it in the meantime. When you complete the work, you earn the bounty. If you would like to become a bounty hunter, please contact me to go over the details.

Hunting is open to anyone who would like to practice (Haskell) programming. Bounty hunters will be mentored and their work reviewed. This is your chance to make money while learning Haskell.

Topics

Most of the work is open-source and it is mostly Haskell programming. There is work suitable for a variety of experience with Haskell. There is work on different topics as well:

• Command-line tools
• Front-end (Reflex, GHCJS)
• Back-end
• Web

Open bounties

Zifter

• Fix the hindent version on a per-commit basis

Hindent changes a lot, and on a per-project basis, the user should be able to stick to a specific hindent version.

Genfile

• Get the project ready for public use. This involves: a zift script, a travis setup using that zift script and fixing the dependency bounds.

Smos

• Standard reports

Hastory

• Bug: working directory is gathered after commands are run

The ‘current working directory’ is gathered after a command is run, instead of before, which means that it is wrong in the case of cd.

Super User Spark

• SUS: bug: non-injective homotopy warning
• SUS: bug: deployment is possible, even though it is not.

Other bounties

There are some other bounties available on projets that are not yet open-source:

• An API-first, CLI second, GUI last Intray (cf GTD)
• An API-first, CLI second, GUI last automated tickler system (cf GTD)
• A command-line habit tracker

Completed bounties

• Intray: authentication
• Workflow: next actions
• Validity: genvalidity-hspec-hashable