Re: [License-discuss] Developing a new open source license

2019-01-31 Thread VanL
Hi Bruce, I welcome feedback and criticism. No need to apologize. Heaven knows, I have given criticism and feedback in the past, and I hope it was taken as constructive. I think that approaching this whole process with some humility is definitely warranted. Let me address a couple of your points.

Re: [License-discuss] Developing a new open source license

2019-01-31 Thread VanL
31, 2019 9:52 AM > *To:* license-discuss@lists.opensource.org > *Subject:* Re: [License-discuss] Developing a new open source license > > > > Van, > > With all respect and understanding of the motivations of the group behind > this, I have a really big problem with this part:

Re: [License-discuss] Developing a new open source license

2019-01-31 Thread VanL
Hello Stephen, Close. The effect would be AGPL-ish by default, but have an LGPL/classpath type clause that people could invoke simply by adding "with the Combined Works Exception" to the end of the license string. Thanks, Van On Thu, Jan 31, 2019 at 11:41 AM Stephen Michael Kellat via License-d

Re: [License-discuss] Developing a new open source license

2019-01-31 Thread Smith, McCoy
: Thursday, January 31, 2019 9:52 AM To: license-discuss@lists.opensource.org Subject: Re: [License-discuss] Developing a new open source license Van, With all respect and understanding of the motivations of the group behind this, I have a really big problem with this part: Unlike other current

Re: [License-discuss] Developing a new open source license

2019-01-31 Thread Bruce Perens
Van, With all respect and understanding of the motivations of the group behind this, I have a really big problem with this part: Unlike other current open source licenses, the Autonomous Agent License will require software that implements a compatible API or publicly performs the API to also be o

Re: [License-discuss] Developing a new open source license

2019-01-31 Thread Stephen Michael Kellat via License-discuss
On Thu, Jan 31, 2019 at 11:16:04AM -0600, VanL wrote: > Hello all, > > I have been retained to help develop a new, strong copyleft open source > license for a client, Holo Ltd. We have been going back and forth > internally for a little while and we will shortly be putting out a draft > for publi

[License-discuss] Developing a new open source license

2019-01-31 Thread VanL
Hello all, I have been retained to help develop a new, strong copyleft open source license for a client, Holo Ltd. We have been going back and forth internally for a little while and we will shortly be putting out a draft for public comment. After the public comment period, we will be submitting