Beat Licence
Dear all,
as you may know, one of the Milestone in February 2016 for the Beat project is to release an open source version of the platform. The goal of this issue is to discuss:
-
What license will be used ?
-
How to handle contribution from people outside of Idiap ?
-
How to separate the modules that will be in the open-sourced version and the modules that will stay closed source ?
-
What license will be used ?
Idiap default license is the GPLv3. I think that in this case, using the GNU AGPLv3, makes more sense. By using the AGPL, anyone providing Beat as a service will also have to share his/her modifications. It is important to note that, as Idiap owns the copyright on all the code, the license we choose will not limit what Idiap can do with the platform. There will still be the possibility for Idiap to propose commercial license or produce derived produce not under the GPL/AGPL. -
How to handle contribution from people outside of Idiap ?
I suggest doing a Copyright transfer agreement for external contributors. The Idea is the ensure that Idiap continue to own the copyright on the whole platform. Any other suggestions are welcome. -
How to separate the modules that will be in the open-sourced version and the modules that are closed source ?
I have no suggestion here. As all of you know the architecture better than me, you are probably more competent to suggest a solution here.
Once we settle on a license, we will know what information need to be added to the files and directories in the project.
Cheers,
Hugues