Blitz Bounty System ᴮᴱᵀᴬ

Members can pledge money for tasks using micropayment services that open source software developers can pick up and solve to earn the money.

It also allows small to large-scale fundraising/pledges for enhancements and improvements on Blitz related and other projects.

All source code will be released as Open Source or Public Domain and CC0 for assets where applicable.

Pledged bounties will be stickied for visibility and promotion.

How Bounties work

1. Users fund bounties on open issues or feature requests they want to see addressed.
2. Developers create solutions which closes the issues and claim the corresponding bounties here.
3. Screenshot or preferably video can be submitted as preview of completed work or task.
4. Backers can accept or reject the claims.
5. If accepted, the Bounty System pays the bounties to the developer.

More Options

Bounty Offers - Developers can also suggest bounties and offer minimum pledges for interesting features or projects.

Blitz Bounty System will be mostly, but not limited to following the BountySource System and Terms. https://app.bountysource.com/terms

To be Updated

Hi RonTek,

I think it would be better to have a simple contract template as a guarantee for anyone considering a bounty. I've found a fairly simple example here software development contract template which clarifies the main points needed.

1. Scope of work - this is the expectations of the work, this is specifics of what the client expects the developer to do. The original post would cover this.
2. Payment terms - this is defining the amount to pay, milestones (part-complete stages), additional expenses and estimated completion dates. To keep it simple we would set a fixed-price contract where payment is a single sum made upon completion with an estimated date offered by the developer. Failure to pay by the client after completion should also be clarified so that the developer has some legal insurance before starting.
3. Non-disclosure - is there any confidential information. This would define how to send payment details over email and what payment service to use, probably Paypal but a good alternative is Wise. Also the developer would need to initially post on the bounty topic that they intend to work on it and then disclose their identity and any previous experience they have over email, so that you won't have several people working on the same bounty.
4. Intellectual property rights - it needs to be clear who will own the copyright of the source code after completion. Since it will always be open source then the developer will probably want to retain their ownership with one of the permissive OS licenses like MIT original, BSD 3-clause or Zlib. And as you say the Creative Commons Zero is the simplest way for developers to include assets.

I think that would cover everything. So now an actual contract template should be made.

Thanks Mark, but for this Bounty System I actually got the idea and following most from the BountySource model.

So basically..

1. Yes, same for both ways either the one that post the issue or developer offers.
2. I have to elaborate and circle back on this one, there will be Bounties and Fundraisers.
3. Similar to BountySource as well and I will have to post more details about this. Payment service to use is up to developer preferably the most widely and safely used platforms.
4. Something along those lines.

A terms page will just be posted and updated when or if as needed.

cheers.

OK, well it sounds like you have a plan, let's see how it goes then.

Great, yes and since I will be offering some ideas and work as well, perhaps you can be the moderator if that would be fine with you.

Also updated the post with the link to BountySource Terms page for a general or overall idea.