AGPLv3 change

[dguido]

You can find an explanation for this change in #1362

[akerl]

How does this work given prior contributions, which were provided under the MIT license?

[andreimc]

you can use anything prior under MIT license

[akerl]

@andreimc , to clarify, my point is that for people who haven’t assigned ownership of their code to trailofbits (via the new CLA), their past contributions still exist under MIT, they can’t just be relicensed without their consent.

[dguido]

@andreimc , to clarify, my point is that for people who haven’t assigned ownership of their code to trailofbits (via the new CLA), their past contributions still exist under MIT, they can’t just be relicensed without their consent.

The MIT license is compatible with the AGPL, which means that MIT licensed code can be included in a AGPL project without the original author’s consent or CLA, and future versions of that code will be GPL only. It’s the same as how MIT code can be included into a closed source commercial product.

That said, we did a review and there are only a small handful of non-CLA contributions in all of Algo’s prior development. Further, most of that code has been overwritten by code with a signed CLA or deleted. I’ll be happy to identify non-CLA code in a text file somewhere if you find any that still exists.