Re: Clarification on licenses and use of MPLv2 in GPLv3+ software

[Johnny Jazeix]

!hi Andreas,

Thank you!

I've read the different threads about the REUSE statements but didn't
took the time to check how much work was needed to apply it to
GCompris.

I've created a task in our backlog to not forget about it:
https://phabricator.kde.org/T13895

Johnny

Le lun. 23 nov. 2020 à 20:23, Andreas Cord-Landwehr
 a écrit :
>
> Hi Johnny,
>
> I read it exactly the same way. So this looks completely fine to me.
>
> Yet, I would suggest to have a look at REUSE compatible license statements,
> which make it much easier to see which files are under which license. Even if
> one should not refer to oneself for reference, here is a starting point how to
> convert to REUSE compatible license statements [1].
>
> Cheers,
> Andreas
>
> [1] 
> 
>
> On Sonntag, 22. November 2020 18:10:44 CET Johnny Jazeix wrote:
> > Hi,
> >
> > GCompris is released under GPLv3+ license. We incorporated the code of
> > a checkers engine under MPL2 licence
> > (https://github.com/shubhendusaurabh/draughts.js).
> >
> > I would like to be sure that it does not change the licence of
> > GCompris (or if we have to ask for a possible relicensing of the
> > library).
> > As I read the documentation in
> > https://www.gnu.org/licenses/license-list.en.html#MPL-2.0, we are
> > doing a "Larger Work" that combines that library with our GPLv3+ code.
> > The library, under our code, will have both licences (we left the
> > LICENSE file besides) and GCompris can be distributed as GPLv3+.
> >
> > Can anyone confirm if my logic is good?
> >
> > Cheers,
> >
> > Johnny
>
>
>
>

Re: Clarification on licenses and use of MPLv2 in GPLv3+ software

[Andreas Cord-Landwehr]

Hi Johnny,

I read it exactly the same way. So this looks completely fine to me.

Yet, I would suggest to have a look at REUSE compatible license statements, 
which make it much easier to see which files are under which license. Even if 
one should not refer to oneself for reference, here is a starting point how to 
convert to REUSE compatible license statements [1].

Cheers,
Andreas

[1] 


On Sonntag, 22. November 2020 18:10:44 CET Johnny Jazeix wrote:
> Hi,
> 
> GCompris is released under GPLv3+ license. We incorporated the code of
> a checkers engine under MPL2 licence
> (https://github.com/shubhendusaurabh/draughts.js).
> 
> I would like to be sure that it does not change the licence of
> GCompris (or if we have to ask for a possible relicensing of the
> library).
> As I read the documentation in
> https://www.gnu.org/licenses/license-list.en.html#MPL-2.0, we are
> doing a "Larger Work" that combines that library with our GPLv3+ code.
> The library, under our code, will have both licences (we left the
> LICENSE file besides) and GCompris can be distributed as GPLv3+.
> 
> Can anyone confirm if my logic is good?
> 
> Cheers,
> 
> Johnny

Re: Getting involved in SoK

[Mariam Fahmy]

Hi,
I am so enthusiastic to start  working in this project, and it will be ok
if we set a call to understand more about the project, it will help me a
lot, I am beginner in open source so there might be a lot of things which
isn't clear to me yet, but I will do my best to finish this project in a
perfect way with your help, I am a student, and I have exams nowdays, I
will finish exams on 1 December, if it is suitable for you, we can set a
call and start working on it.
Thanks.

On Mon, 23 Nov 2020, 8:10 pm Timothée Ravier,  wrote:

> Hi Miriam, Aleix,
>
> On Wed, Nov 18, 2020 at 5:07 AM Aleix Pol  wrote:
>
>> Including Timothée who will be co-mentoring the project. :)
>>
>> On Wed, Nov 18, 2020 at 5:03 AM Aleix Pol  wrote:
>> > Adding the mentors list to know what the exact process for students is.
>> >
>> > Mariam, in the meantime, if you want to start working on it or want to
>> > have some kind of call to get started, tell me and I'll see to it.
>>
>
> Fee free to send all rpm-ostree questions my way.
>
> Setting up a call to get things started may be good.
>
> Thanks,
> --
>
> Timothée Ravier
>
> Red Hat & Fedora CoreOS Engineer
>
> Red Hat 
>
> trav...@redhat.comIM: travier
> 
>