Tern.js and some other projects I've seen was crow-founded in a similar way
http://www.indiegogo.com/projects/tern-intelligent-javascript-editing

The author says "I am going to do this anyway, but if I reach X amount
before some date it will be opensource, otherwise will be a paid-product
forever", kickstarter kind of thing




2013/5/7 Isaac Schlueter <[email protected]>

> (IANAL.  I'm fantasizing.  Please ignore.)
>
> I've often thought it would be worthwhile to have some kind of "free
> once I make some money" license.  Like, if you're a not-for-profit
> entity, you can use this code under BSD today.  If you are a
> for-profit enterprise, you can use this code freely for profit as long
> as you pay me $100.  Once I've made $100,000 from this code, it'll be
> released for all under the BSD license.
>
> Neat idea for a startup or something :)
>
>
> On Tue, May 7, 2013 at 9:06 AM, Martin Cooper <[email protected]> wrote:
> >
> >
> >
> > On Tue, May 7, 2013 at 8:39 AM, Alex Kocharin <[email protected]> wrote:
> >>
> >>
> >> You can use dual-licensing. Let people choose GPL or commercial license,
> >> so anyone who can't use infectious type will be forced to pay...
> >
> >
> > ... or simply choose a different package. It's open source; if people
> don't
> > like the terms, and there's a need, someone else will write one with more
> > acceptable terms. You won't "force" anyone to pay.
> >
> > --
> > Martin Cooper
> >
> >
> >>  --
> >> // alex
> >>
> >>
> >> 07.05.2013, 16:51, "Saleem Abdul Hamid" <[email protected]>:
> >>
> >> Is there a license that says most people can do whatever you want with
> my
> >> stuff but if Microsoft (example) uses it to make 100 million dollars, I
> want
> >> to negotiate for a piece of it? That's really the question everyone is
> >> asking, although they're too shy to say it, because wanting to make
> money
> >> off of your stuff is considered bad form in certain quarters.
> >>
> >> Personally, even if a huge company with a lot of money was using one of
> my
> >> projects as an integral part of a moneymaker, I'd be happy with a very,
> very
> >> fair (for them) royalty that they would probably not even consider
> >> significant. But if you use the MIT, the question of negotiating
> anything
> >> doesn't even come up.
> >>
> >> To be clear, I want a license that is not infectious at all. That lets
> >> people use, modify, redistribute, all that good stuff. But just leaves
> open
> >> the door that if someone gets really rich using my project, I can
> benefit
> >> from coming up with the idea and doing the work.
> >>
> >> Is there a license that represents this?
> >>
> >> On Friday, December 14, 2012 10:38:05 PM UTC-5, Forrest L Norvell wrote:
> >>
> >> On Fri, Dec 14, 2012 at 7:29 PM, David Herron <[email protected]>
> >> wrote:
> >>
> >> I'm curious about the preferred license for modules that are distributed
> >> through the npmjs.org repository
> >>
> >>
> >> We discussed this a bit at NodeConf summer camp this year, and the
> >> consensus was pretty strongly in favor of BSD or MIT licenses, or at
> least
> >> pretty liberal, commercial-use friendly licenses (including the Perl and
> >> Apache licenses).
> >>
> >>
> >> In particular is there any legal barrier to using GPL in such modules?
> >>
> >> As far as I understand it, the legal barrier would be whether a module
> >> which uses a GPL'd module is derivative of that module.  I don't think
> that
> >> it would be, but then the LGPL license does exist for a reason.
> >>
> >>
> >> Isaac can speak to this more authoritatively than I can, but npm itself
> >> prescribes / proscribes no particular licenses. You could attach GPL3
> >> licenses to your modules if you wanted, but uptake would probably be
> >> hampered, especially if there were some kind of associated
> Canonical-style
> >> contributor's agreement. Node is still pretty much the wild west, and
> it's
> >> tough to say if today's random hack project might not become tomorrow's
> >> startup idea, and I think most devs want to keep their options open.
> >>
> >> F
> >>
> >>
> >>
> >> --
> >> --
> >> Job Board: http://jobs.nodejs.org/
> >> Posting guidelines:
> >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> >> You received this message because you are subscribed to the Google
> >> Groups "nodejs" group.
> >> To post to this group, send email to [email protected]
> >> To unsubscribe from this group, send email to
> >> [email protected]
> >> For more options, visit this group at
> >> http://groups.google.com/group/nodejs?hl=en?hl=en
> >>
> >> ---
> >> You received this message because you are subscribed to the Google
> Groups
> >> "nodejs" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to [email protected].
> >> For more options, visit https://groups.google.com/groups/opt_out.
> >>
> >>
> >>
> >> --
> >> --
> >> Job Board: http://jobs.nodejs.org/
> >> Posting guidelines:
> >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> >> You received this message because you are subscribed to the Google
> >> Groups "nodejs" group.
> >> To post to this group, send email to [email protected]
> >> To unsubscribe from this group, send email to
> >> [email protected]
> >> For more options, visit this group at
> >> http://groups.google.com/group/nodejs?hl=en?hl=en
> >>
> >> ---
> >> You received this message because you are subscribed to the Google
> Groups
> >> "nodejs" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to [email protected].
> >> For more options, visit https://groups.google.com/groups/opt_out.
> >>
> >>
> >
> >
> > --
> > --
> > Job Board: http://jobs.nodejs.org/
> > Posting guidelines:
> > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> > You received this message because you are subscribed to the Google
> > Groups "nodejs" group.
> > To post to this group, send email to [email protected]
> > To unsubscribe from this group, send email to
> > [email protected]
> > For more options, visit this group at
> > http://groups.google.com/group/nodejs?hl=en?hl=en
> >
> > ---
> > You received this message because you are subscribed to the Google Groups
> > "nodejs" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [email protected].
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
>
> --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to