discuss@lists.openscad.org

OpenSCAD general discussion Mailing-list

View all threads

bottle with cut design

P
pproj@posteo.de
Fri, Sep 22, 2023 3:17 PM

Thanks a lot Thorsten!
as always hepful.

On 21.09.23 21:23, Torsten Paul wrote:

Disclaimer first... no legal advice...

On 20.09.23 00:44, pproj@posteo.de wrote:

if it can be dual licensed under OHL-S (v2). It is now under GPL2 (just
because i have known it and its principles for very many years)

I'm pretty sure you can license your works as you like under as many
licenses as you wish.

If OHL-S works for source code, I don't know. I'm not even sure it's
really clear how licenses work in this context. Specifically if the
resulting object, or even the STL is somehow related license wise.

So how to license it, so it will stay compatible with Openscad's
licensing and enable most people to use it?

My expectation here is that there is no relation to the OpenSCAD
application license. The OpenSCAD source code is GPL-2+ (mostly,
with some MIT bits), the binaries we ship (due to CGAL) are GPL-3+.

I don't know if we should add an explicit disclaimer, but I don't
see any reason why the application license should in any way infect
the data it's processing.

ciao,
  Torsten.


OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org

Thanks a lot Thorsten! as always hepful. On 21.09.23 21:23, Torsten Paul wrote: > Disclaimer first... no legal advice... > > On 20.09.23 00:44, pproj@posteo.de wrote: > >> if it can be dual licensed under OHL-S (v2). It is now under GPL2 (just >> because i have known it and its principles for very many years) > > I'm pretty sure you can license your works as you like under as many > licenses as you wish. > > If OHL-S works for source code, I don't know. I'm not even sure it's > really clear how licenses work in this context. Specifically if the > resulting object, or even the STL is somehow related license wise. > > >> So how to license it, so it will stay compatible with Openscad's >> licensing and enable most people to use it? > > My expectation here is that there is no relation to the OpenSCAD > application license. The OpenSCAD source code is GPL-2+ (mostly, > with some MIT bits), the binaries we ship (due to CGAL) are GPL-3+. > > I don't know if we should add an explicit disclaimer, but I don't > see any reason why the application license should in any way infect > the data it's processing. > > ciao, >   Torsten. > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org