Preference for Keeping Saved Empty Button Scripts Empty

Mike Kerner MikeKerner at roadrunner.com
Tue Jun 20 12:48:31 EDT 2017


Which is exactly why this is a better idea.  Kickstarter releases the funds
when the funding goal is achieved, not when the product is finished.  This
idea is the reverse.
1. We set up the account
2. We fund the account
3. We administer the account
4. We decide which projects we want to fund at what amount
5. We, in effect, put out a bid sheet for the work.
6. We test and pay out once someone has developed a solution that we accept.

I see two different ways of setting this up, and we could do both.
Way 1 - the "Buy in to get access" way:
Idea proposed
Everyone who "buys in" gets the end product - similar to the LC Global Open
API product
Folks send in their funds
The funds are held in escrow
If the product is built and accepted, the funds are released.  If not, the
funds are returned.

Way 2 - the "shareholder" way:
I envision this being for more widespread release projects, e.g.
the dictionary redo
Folks buy shares.  Let's say each share costs $10.
Shareholders prioritize projects and put a price on each, via votes.  Each
share gets a vote, as you would expect.
Someone goes after one of the projects.
The project is completed and accepted by the shareholders on behalf of the
community.
The funds are released.

We can do this with bitcoin, or dollars, or whatever.



More information about the use-livecode mailing list