Imagine a user comes along and submits a feature request to your project. After approval and clarification from someone with the appropriate user role in your project’s development team, that task will become part of the project’s Version Map.
That user, as well as any other user of the Bounty Source system, could then proceed to place a monetary bounty on that task. All bounty amounts are publicly viewable and the total adds up with every posted bounty. When a developer shows interest in writing the solution, they can create a “Solution In Progress” and keep a developer’s journal that will be open for all to view/comment upon.
After a solution has been submitted and approved, the funds will be released to the developer — but not until a “Disputable” period has passed in which any user can raise concerns with the solution, should they have any.
bountysource.com

Today, I found bountysource.com by way of digg.com. The quote above describes the site and the services they provide. Recently, folks have started grumbling about the usefulness and relevance of SourceForge.net; long the 800 lb. gorilla of FOSS project management. However, many think it is simply used as a loss leader for the VA Software’s commercial application, SourceForge Enterprise Edition.
Along comes bountysource.com. These folks offer similar services and they have great valueadd … bounties. As someone whose core business depends on FOSS technologies, I’ve often wondered how to get the attention of the devs of particular projects. Also, as someone who has developed against four different FOSS applications, I know how thankless the job can be and how hard it can be to find time to meet the demands of the user base. Until bountysource.com, there was no way I knew to address the competing demands of both sides of this sticky problem.
Bug and feature bounties are the ideal solution for everyone. By placing a bounty on a particular feature, the end user puts his money where his mouth is. This should really help FOSS devs separate the wheat from the chaff when it comes to bug hunting and feature requests. Moreover, this concept provides two important processes which can further expand the FOSS infrastructure/agenda:
- First, it provides a business model that should allow motivated FOSS devs a realistic way to make a living from their efforts (or at least a profitable side business) and eventually leave the corporate ghetto behind.
- Second, it provides folks who are building FOSS-based enterprises a concrete way to invest their money into their busniess and feel confident they will see a meaningful ROI.
To be certain, bountysource.com seems raw and still very beta. They are marrying commerce and FOSS in new and innovative way. I wish them well. Their success gives me another tool to build my business by responding to market demands more quickly. Should they stumble or fall, someone should grab this BIG IDEA and run with it.