| | 1 | == Developer bounties == |
| | 2 | |
| | 3 | Should we have a bounty system for writing missing features? Similar systems are in use by several other projects, e.g. freeswitch, pfSense and Funambol. This idea originated from ''ecrist''. |
| | 4 | |
| | 5 | * '''Rationale''' |
| | 6 | * Would allow users to prioritize feature additions through compensation. |
| | 7 | * Would help achieve greater interest of developers in users' requests and needs. |
| | 8 | |
| | 9 | * '''Implementation ideas''' |
| | 10 | * Bounty funds would be setup and maintained by a non-developer (ecrist?) and held. This assures payment upon completion and assures feature is completed before bounty is paid. |
| | 11 | * Multiple users could fund a bounty for intensive feature additions which may warrant higher payouts. |
| | 12 | * Developers setup up accounts and 'claim' tasks |
| | 13 | * After a specific timeout a task becomes available to another user, unless progress can be shown |
| | 14 | * Payment could be divided into multiple phases to motivate developers to maintain the code they've written. For example: |
| | 15 | * 50% payout for a commit to main tree |
| | 16 | * 25% upon release in production (provided bugs are fixed/etc) |
| | 17 | * 25% 6 months after release (provided bugs are fixed/etc) |
| | 18 | * The above would also guarantee the quality of the code |
| | 19 | * Handling monetary transactions |
| | 20 | * Could be handled through an external foundation / organization (e.g. http://www.spi-inc.org/projects) |
| | 21 | * We could establish our own foundation for the purpose |
| | 22 | * Licensing and copyright |
