Add Open Source License Document to Repository

[paluka]

To allow people to know the usage rights of SMT, we should have the license document in the root directory of the repository and state in the README file that SMT is open source.

[ZachCook]

Most if not all of the code is GPL3, which does mean our license affects users of SMT too (they must also license their code as GPL3), so this is very important to document.

[kiwistrongis]

I'd recommend the LGPL over the GPL. Is there a reason why we're stuck with the GPL? All of the original source code for SMT belongs to use, right? Erik noted that the original code for mouse2tuio doesn't, does anybody know mouse2tuio's original license?

[paluka]

I used the concept of the Zone from tuioZones, but I created my own project and classes when I created the first version of SMT, so we do not have to abide by tuioZones license.

For mouseToTUIO, I used the reacTIVision TUIO simulator code and edited it to provide mouse emulation for SMT. mouseToTUIO is licensed under GPLv2 and needs to be rewritten if we want to license our project under something else other than GPL.

LGPL seems like a better choice for SMT.

[ZachCook]

LGPLv3 in particular looks like the only choice for re-licensing due to the
libraries SMT uses (ZLIB,LGPL and Apache 2.0)

Contacting reactivision tuio simulator's author and all SMT contributors
for re-licensing should be all that is required, otherwise the code would
have to be removed to re-license.

On Thu, Mar 19, 2015 at 3:10 PM Erik Paluka [email protected]
wrote:

I used the concept of the Zone from tuioZones
http://www.photonfarm.net/tz/, but I created my own project and classes
when I created the first version of SMT, so we do not have to abide by
tuioZones license.

For mouseToTUIO, I used the reacTIVision TUIO simulator
http://reactivision.sourceforge.net/ code and edited it to provide
mouse emulation for SMT. mouseToTUIO is licensed under GPLv2
http://www.gnu.org/licenses/gpl-2.0.html and needs to be rewritten if
we want to license our project under something else other than GPL.

LGPL https://www.gnu.org/licenses/lgpl.html seems like a better choice
for SMT.

—
Reply to this email directly or view it on GitHub
#218 (comment).

[kiwistrongis]

So if we have tuio simulator's author's approval we can relicense touch2tuio as LGPL?

[kiwistrongis]

Hey Erik, are you aware of this section from reactivision's website?:

The related TUIO reference implemenations and clients are available under the LGPL, license which both allows its inclusion in open and closed source projects, while only the changes to the actual libraries need to be published under the same LGPL license.

[ZachCook]

@mkalten you have copyright to some of our codebase, would you support re-licensing of it to LGPLv3?

Here are the files with your copyright

[paluka]

@kiwistrongis That section is talking about the TUIO clients, not the TUIO simulator. I forgot to mention that I did use the TUIO Java client implementation in SMT as well.

[mkalten]

Sure, no problem from my side, feel free to relicense that code to LGPL, I already did so with some of the TUIO projects that I updated recently ...