[License-discuss] Developing a new open source license
van.lindberg at gmail.com
Thu Jan 31 18:49:06 UTC 2019
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.
On Thu, Jan 31, 2019 at 11:41 AM Stephen Michael Kellat via License-discuss
<license-discuss at lists.opensource.org> wrote:
> 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 public comment. After the public comment period, we will be
> > the license to the OSI for certification.
> > I will also be discussing this license in my presentation at CopyleftConf
> > on Monday.
> > In the meantime, some of the underlying reasoning for why we need a
> > different open source license is being presented on Holo's blog. The
> > post is up now, and the second will be up in a couple days:
> > Comments are welcome.
> > Thanks,
> > Van
> From that description it seems as if you're looking for an AGPL-like
> equivalent to LGPL. Is that a fair reading?
> Stephen Michael Kellat
> License-discuss mailing list
> License-discuss at lists.opensource.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the License-discuss