[erlang-questions] Is there an accepted way of including GPL code in a project?
Fri Apr 13 15:02:23 CEST 2012
Is this possible, to switch licenses? I'd think all the Erlang code
that was already under the GPL has to stay under the GPL.
On 4/13/12, Joe Armstrong <> wrote:
> It has been suggest that the Erlang licence be changed to MPL2
> If [*] this change were to be made would it solve your problem?
> [*] (please note the word "if" - this is not a promise it's a pure question)
> On Fri, Apr 13, 2012 at 11:57 AM, Alan Evans <> wrote:
>> Hello list,
>> I'm thinking about using some GPL code in a project I'm working on.
>> Namely the SIGTRAN stack from the osmocom project
>> Is there a recognized way to incorporate GPL code in an erlang project
>> without making the whole project subject to the GPL license?
>> I haven't yet decided whether or not to make my project open source.
>> My thinking is that if I isolate all the GPL code to a particular
>> Erlang node then only the modules running on that node need to be GPL
>> or GPL compatible, I am free to license the modules running on the
>> other nodes any way I wish.
>> Any thoughts? Other than the obvious "ask a lawyer" response :-)
>> Thanks in advance
>> erlang-questions mailing list
> erlang-questions mailing list
More information about the erlang-questions