Re: The Bounty License

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
>
>