License for scad files

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

License for scad files

Johannes Reinhardt
Hi everybody,

while working on BOLTS, I started to think about licensing and scad
code and realised that this is a quite complicated topic. I am not a
lawyer, so I struggled quite a bit with that. Licenses are of some
importance to BOLTS, because I want to make sure, that existing code
can be incorporated with little effort, and for that I have to make
sure that this is legally possible.

I reached a state where I think I understood and then tried to write it
up:

http://jreinhardt.github.io/BOLTS/doc/general/licensing.html

However, today I thought about it from another perspective and
struggled again, so I decided to ask for your expertise, maybe you can
point out if I misunderstood something.

The main problem for me is that scad code is somehow both code and
content. On the one hand one can see a scad file as something that is
a description of an object, just like a stl file. If you look at it
like that, then a CC license makes perfect sense.

On the other hand, scad code is very much code. You can have a scad
library that is not a description of an object. For that, I feel, a
license tailored towards code, like the GPL or LGPL is better suited.
MCAD for example is LGPL.

But CC and (L)GPL are incompatible, which means that one cannot use them
together. Unfortunately, a lot of the scad code that is around is CC
licensed, because the standard license on thingiverse is CC. I find
this very unsatisfactory that the available scad code is fragmented
into legally incompatible subsets.

Greetings

Johannes


--

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Fwd: License for scad files

Bryan Bishop

From: Johannes Reinhardt <[hidden email]>
Date: Tue, Oct 29, 2013 at 4:55 PM
Subject: [OpenSCAD] License for scad files
To: "[hidden email]" <[hidden email]>


Hi everybody,

while working on BOLTS, I started to think about licensing and scad
code and realised that this is a quite complicated topic. I am not a
lawyer, so I struggled quite a bit with that. Licenses are of some
importance to BOLTS, because I want to make sure, that existing code
can be incorporated with little effort, and for that I have to make
sure that this is legally possible.

I reached a state where I think I understood and then tried to write it
up:

http://jreinhardt.github.io/BOLTS/doc/general/licensing.html

However, today I thought about it from another perspective and
struggled again, so I decided to ask for your expertise, maybe you can
point out if I misunderstood something.

The main problem for me is that scad code is somehow both code and
content. On the one hand one can see a scad file as something that is
a description of an object, just like a stl file. If you look at it
like that, then a CC license makes perfect sense.

On the other hand, scad code is very much code. You can have a scad
library that is not a description of an object. For that, I feel, a
license tailored towards code, like the GPL or LGPL is better suited.
MCAD for example is LGPL.

But CC and (L)GPL are incompatible, which means that one cannot use them
together. Unfortunately, a lot of the scad code that is around is CC
licensed, because the standard license on thingiverse is CC. I find
this very unsatisfactory that the available scad code is fragmented
into legally incompatible subsets.

Greetings

Johannes


--

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566



--
- Bryan
http://heybryan.org/
1 512 203 0507

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: License for scad files

Joshua Holbrook
A few things:

1) Dual licensing is an option.
2) MIT or BSD licenses are very permissive, such that you shouldn't run into many problems with incompatible licensing if you use them. Personally, I'm an MIT fan.

--Josh


On Tue, Oct 29, 2013 at 3:57 PM, Bryan Bishop <[hidden email]> wrote:

From: Johannes Reinhardt <[hidden email]>
Date: Tue, Oct 29, 2013 at 4:55 PM
Subject: [OpenSCAD] License for scad files
To: "[hidden email]" <[hidden email]>



Hi everybody,

while working on BOLTS, I started to think about licensing and scad
code and realised that this is a quite complicated topic. I am not a
lawyer, so I struggled quite a bit with that. Licenses are of some
importance to BOLTS, because I want to make sure, that existing code
can be incorporated with little effort, and for that I have to make
sure that this is legally possible.

I reached a state where I think I understood and then tried to write it
up:

http://jreinhardt.github.io/BOLTS/doc/general/licensing.html

However, today I thought about it from another perspective and
struggled again, so I decided to ask for your expertise, maybe you can
point out if I misunderstood something.

The main problem for me is that scad code is somehow both code and
content. On the one hand one can see a scad file as something that is
a description of an object, just like a stl file. If you look at it
like that, then a CC license makes perfect sense.

On the other hand, scad code is very much code. You can have a scad
library that is not a description of an object. For that, I feel, a
license tailored towards code, like the GPL or LGPL is better suited.
MCAD for example is LGPL.

But CC and (L)GPL are incompatible, which means that one cannot use them
together. Unfortunately, a lot of the scad code that is around is CC
licensed, because the standard license on thingiverse is CC. I find
this very unsatisfactory that the available scad code is fragmented
into legally incompatible subsets.

Greetings

Johannes


--

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566



--
- Bryan
http://heybryan.org/
<a href="tel:1%20512%20203%200507" value="+15122030507" target="_blank">1 512 203 0507

_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566


_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566
Reply | Threaded
Open this post in threaded view
|

Re: License for scad files

Alan Cox
In reply to this post by Johannes Reinhardt
> The main problem for me is that scad code is somehow both code and
> content. On the one hand one can see a scad file as something that is
> a description of an object, just like a stl file. If you look at it
> like that, then a CC license makes perfect sense.

All code is data, that's the very essence of Turing.

> On the other hand, scad code is very much code. You can have a scad
> library that is not a description of an object. For that, I feel, a
> license tailored towards code, like the GPL or LGPL is better suited.
> MCAD for example is LGPL.

One option is to dual license it and let people pick. As the creator of a
work you are not tied to a single licence.

> But CC and (L)GPL are incompatible, which means that one cannot use them
> together. Unfortunately, a lot of the scad code that is around is CC
> licensed, because the standard license on thingiverse is CC. I find
> this very unsatisfactory that the available scad code is fragmented
> into legally incompatible subsets.

It's unfortnate because CC doesn't really make much sense for code. It's
the legal equivalent of trying to clean your windows in a washing machine.

Alan
_______________________________________________
OpenSCAD mailing list
[hidden email]
http://rocklinux.net/mailman/listinfo/openscad
http://openscad.org - https://flattr.com/thing/121566