- From: heather vescent <heathervescent@gmail.com>
- Date: Thu, 18 Oct 2018 08:55:05 -0700
- To: Adam Lake <alake@digitalbazaar.com>
- Cc: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
- Message-ID: <CA+C6qMx2OPzT-v8m=ND+kYrBuKrHWc0XPkN_EL14tQS6Fso=SA@mail.gmail.com>
Have you successfully crowd-funded before? Because I have, and I have coached people through it. It's not pretty or easy and there is no way I am ever doing that kind of fundraising again. On Thu, Oct 18, 2018 at 8:51 AM Adam Lake <alake@digitalbazaar.com> wrote: > HI Heather, > > One way to approach this could be to produce a proposal for the work > product and put a bounty on it to be prefunded. Otherwise know as > crowdfunding, :) > > It might be a good idea to circulate the proposal prior to the funding > phase to get feedback from the community as to how the proposal could be > modified to attract the bounty being requested. > > This could reduce your, and others, risk, as well as increase the value to > the community. Just a thought. > > Adam > > On 10/17/2018 6:24 PM, heather vescent wrote: > > While I applaud this concept, it is extremely problematic, specifically in > putting all the risk onto the content creator. Maybe that is not too much > of a risk for a developer building code, but it is significantly different > for a film producer. > > On Wed, Oct 17, 2018 at 3:19 PM Melvin Carvalho <melvincarvalho@gmail.com> > wrote: > >> >> >> On Wed, 17 Oct 2018 at 23:22, Manu Sporny <msporny@digitalbazaar.com> >> wrote: >> >>> Following up with an idea on "how can we fund things in this ecosystem". >>> The concept of bounties came up. >>> >>> Here's a simple concept: >>> >>> Release software, documentation, and specifications under a "Bounty >>> License". >>> >>> The license states that the content is free for non-commercial use and >>> sets a bounty price to transition the license into a FOSS license. >>> >>> For example, libvc is a Verifiable Credentials library in C++. It is >>> under a bounty license of $50K, if the bounty is paid, it moves to BSD >>> 3-clause license. I can imagine three companies joining in and paying >>> that bounty because it reduces implementation risk for them, and they >>> get the software at a fraction of the cost of developing and maintaining >>> it themselves. The upside is that the developer is paid for their effort >>> vs. what happens today (leeching). >>> >>> This is easiest for software... harder for things like documentation, >>> videos, etc. Information that once it's out, it's out, is more >>> difficult. So, for those items, previews are released and the full >>> version is only released once the bounty is paid. >>> >>> Bounty prices would have to be above market rates... because the content >>> creator took on considerable risk in creating the content. >>> >>> -- manu >>> >>> PS: I know there are some things that may be better paid for up front, >>> and we can still do that in parallel to the suggestion above. >>> >> >> love it! >> >> >>> >>> -- >>> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) >>> Founder/CEO - Digital Bazaar, Inc. >>> blog: Veres One Decentralized Identifier Blockchain Launches >>> https://tinyurl.com/veres-one-launches >>> >>> > > -- > Heather Vescent <http://www.heathervescent.com/> > President, The Purple Tornado, Inc > Author, A Comprehensive Guide to Self Sovereign Identity > <https://ssiscoop.com/> > Author, The Cyber Attack Survival Manual <http://amzn.to/2i2Jz5K> > > @heathervescent <https://twitter.com/heathervescent> | Film Futures > <https://vimeo.com/heathervescent> | Medium > <https://medium.com/@heathervescent/> | LinkedIn > <https://www.linkedin.com/in/heathervescent/> | Future of Security Updates > <https://app.convertkit.com/landing_pages/325779/> > > > -- > Adam Lake > Director, Business Development > Digital Bazaar > Veres.io > 540-285-0083 > > -- Heather Vescent <http://www.heathervescent.com/> President, The Purple Tornado, Inc Author, A Comprehensive Guide to Self Sovereign Identity <https://ssiscoop.com/> Author, The Cyber Attack Survival Manual <http://amzn.to/2i2Jz5K> @heathervescent <https://twitter.com/heathervescent> | Film Futures <https://vimeo.com/heathervescent> | Medium <https://medium.com/@heathervescent/> | LinkedIn <https://www.linkedin.com/in/heathervescent/> | Future of Security Updates <https://app.convertkit.com/landing_pages/325779/>
Received on Thursday, 18 October 2018 15:55:39 UTC