Can code licensed under AGPL also be (re)licensed under LGPL by its contributor?

Question

I have a puzzling question:
Somebody contributed to a AGPL licensed project (he is not the owner). Now this code could also be applied to a different project licensed under LGPL. Could the author of this code part (he is listed in the license header of the AGPL code as (c) ) give permission to use that code in the other LGPL project? The contributor thinks that he can not because he signed some contributor agreement with the AGPL project but I wanted to ask this here and maybe someone has some insight...
Update: I think I found the CLA, so here is the interesting part:

Bart van Ingen Schenau · Accepted Answer

What this author has signed in not a Contributor License Agreement, giving the project additional (non-exclusive) rights in addition to what they get under the AGPL, but a transfer of copyrights (CTA, Copyright Transfer Agreement).
This means that the AGPL project owns the copyrights on the contribution and the author has just as many rights as anyone else who obtained a copy1.

1: This is not entirely true, depending on the view on moral rights in the author's jurisdiction, but that does not make a difference when it comes to re-using the code in a different project.

allo · Answer

The author has the copyright, so he can relicense from the license point of view.
But the CLA is not a license, but a contract. And you need to read the contract to know what it allows and what not.
One possiblity is, that the contributor signed that he will not license the code other than to the company the CLA is for or AGPL for the general public.
Another possiblity is, that he just signed that the project can use the code without following the AGPL and nothing more. I know some projects that accept code from people that do not belong to the project either under a CLA or under a permissive license like MIT, which allows everyone to use it without following the AGPL, when no other AGPL code is involved.

Can code licensed under AGPL also be (re)licensed under LGPL by its contributor?

2 Answers

Add your own answers!

Ask a Question