Bounties
There are a few different takes on how to use bounties to encourage work on specific projects, or to share support from specific organizations.
Specific ideas:
- Bounties for awesome (highlighting specific projects/problems)
- Summer of Content (projects and mentors)
- Bounties for coding projects needed
Background
Past project experiences
Sources for bounty info: Google for trac bounties
- Tinymail Bounties (none currently)
- Dr Queue Bounties (Wiki-based none currently)
bughunting
Need to establish rules, eligibility, how long project might take, what we could offer for that.
mako - mixing paid employees and volunteers
tinymail pidgin
This is something that's been done by CodeWeavers' for the wine project, mostly by corporations who wanted certain features. Legal Aid Manitoba had codeweavers make Childview work on wine for $2,000. Walt Disney paid
Software/feature bounties as a open source software funding tool - extend this to trac - pay $5, 10, 20, 50, 100 for development of a software feature, bugfix, etc that you want done - closed source - each person pays for the same software, collectively paying for a fixed amount of development - open source with bounties - each person gets the current software, if they want it to be better, they pay for what extra tool they want in it. it's like donating extra features to a project.
for developers, this would both attract volunteers and help current volunteers turn work into OSS contribution, beer, and lowering the cost for the OLPC.
go half and half, dev and donation