[jitsi-dev] Switching to the Apache Licenses


#1

@Jitsi, @Atlassian, @Emil

Really great news! Thumbs up for Atlassian, seems to be a cool company :slight_smile:

Helpful for licenses comparison:

http://choosealicense.com/licenses/

路路路

2015-06-18 17:45 GMT+02:00 Emil Ivov emcho@jitsi.org:

Hey Zalmoxisus,

Whatever you have retrieved under a specific license you can continue

using under that license.

I don鈥檛 believe there are significant differences between MIT and

Apache BUT I am not a lawyer so you shouldn鈥檛 trust me on that.

Emil

On Thu, Jun 18, 2015 at 5:38 PM, Michael Diordiev zalmoxisus@gmail.com wrote:

Hey Emil,

Thanks for good news and the detailed explanation. Could you please explain

also about differences between MIT and Apache? In case we鈥檝e already use

jitsi-meet in production, do we need to update all the files with this

license header or may use it as MIT till we don鈥檛 need to merge from

upstream?

Regards,

Zalmoxisus

On Thu, Jun 18, 2015 at 11:25 AM, Emil Ivov emcho@jitsi.org wrote:

Hey all,

As you all know Blue Jimp has joined Atlassian. With this new partnership,

we are making changes, due to expected growth - thanks to more eyes than

ever on the Jitsi Community.

The first update we will be making is that we are changing our license.

In order to lower adoption barriers, Blue Jimp is switching to the Apache

license and contributor agreement.

Most of you on this list are familiar with differences between Apache and

LGPL, but we wanted to make sure everyone is on the same page:

LGPL, our current license allows everyone to integrate and ship our

various jars. Once you start making changes and distributing them however,

then you you need to make sure these changes are also available under LGPL,

AKA the LGPL reciprocity clause.

As the copyright holder, in BlueJimp we have been been exempt from this

reciprocity clause. Even though we rarely use it, we had the liberty to

modify our code without making our changes public. No one else had this

option.

Switching to Apache ends our advantage in this regard, and allows everyone

to use, integrate and distribute Jitsi with a lot less limitations.

We鈥檒l also be using DocuSign for the Apache Contributor License Agreement,

so we need all existing contributors to sign the Apache CLA, but thanks to

DocuSign, signing up for the new license will be just a few clicks.

Cheers,

Emil

https://jitsi.org


dev mailing list

dev@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/dev


dev mailing list

dev@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/dev

https://jitsi.org


dev mailing list

dev@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/dev