Re: [License-discuss] On dual-licensing

2020-01-05 Thread John Cowan
On Sun, Jan 5, 2020 at 10:43 AM Henrik Ingo wrote: Btw, one point I left out of my first email: While we all agree that > the community-style, aka "multi-vendor" way of developing FOSS > software is the ideal form of open source, I think it's also important > to give these single vendor efforts t

Re: [License-discuss] On dual-licensing

2020-01-05 Thread Henrik Ingo
On Sun, Jan 5, 2020 at 3:35 PM Dirk Riehle wrote: > > On 02.01.20 15:30, Henrik Ingo wrote: > > I wanted to make some general notes on the term and practice of > > "dual-licensing". This is related to the ongoing review of the CAL license, > > Thanks for taking the plunge! > > In my book, dual lic

Re: [License-discuss] On dual-licensing

2020-01-05 Thread Dirk Riehle
On 02.01.20 15:30, Henrik Ingo wrote: > I wanted to make some general notes on the term and practice of > "dual-licensing". This is related to the ongoing review of the CAL license, Thanks for taking the plunge! In my book, dual licensing is an IP licensing strategy and open core is an IP modular

Re: [License-discuss] On dual-licensing

2020-01-03 Thread Kevin P. Fleming
I'd only make one small change. Centralizing copyright *licensing* in a single entity enables those (and additional) business models. I haven't come across many instances outside of the FSF where contributors are asked to assign their copyrights to the single entity, generally they are only asked

[License-discuss] On dual-licensing

2020-01-02 Thread Henrik Ingo
I wanted to make some general notes on the term and practice of "dual-licensing". This is related to the ongoing review of the CAL license, but this is general enough that license-discuss seemed more appropriate. Terminology: Nowadays I often see "dual licensing" used broadly, essentially referrin