The basic requirements of the document are
1) Encourage Collaboration Competition rather than Cut-Throat Competition
---check2) Reward speed by offering advantage to 'first to market'
--check3) Prevent theft of work by building on others without their compensation
--check4) Unambiguous allocation and division of bounties
--check5) Handle rules for different types of deliverables (code, writing, graphics, videos, etc)
--check6) Encourage referrals of people to the bounties, people who refer winners get a cut
--not included as there are OPEN bounties for that already7) Perhaps a time window after submission during which competitors may make a submission
--check Encourage reinvestment back into the community
--how to do so?9) Encourage post-bounty support of products
--check10) Discourage submission of half-baked code with bugs and coding violations
--check11) Dispute resolution process
--check12) Process states PENDING, ACTIVE, EVALUATING, CLOSED
--check13) Bounties to help in the evaluation phase... ie: finding bugs, coding violations, security holes
--check14) Ways to organize team bounties where a 'project manager' can organize many others to help build a larger deliverable. --
should we not leave this part since we cannot dictate how a team decides to come together?15) Bounties double as marketing / giveaways and thus should be priced to entice heavy competition and multiple bids rather than attempt to get a deal for minimal effort or expense.
-- that's not really rules and procedure, more like description16) Have a commission system for the bounty operator/organizer. The goal is to motivate rapid question/answer/evaluation cycles and divide up the task of running the bounty in addition to completing the bounty.
17) Voting systems are a big negative, we strongly prefer solutions that do not involve voting of any type.
I'd like to find a way to put 16 into the document