License Agreements and Changes Are Coming

Finally! The current situation has caused a fair amount of grief. E.g. postgres not being able to link against libreadline and libedit (horribly buggy) instead being used.

> Our plan is to update the license to the Apache License version 2.0 (APLv2.0)).

So no more OpenSSL for GPLv2 projects?

That's not new unfortunately. The openssl license has always contained an advertising clause.

The problem is often worked around in the basis of GPL's OS exception though.

The OpenSSL license is not compatible with GPLv2 or GPLv3 due to the obnoxious advertising clause.

The ALv2 however is at least compatible with GPLv3, so it's clearly an improvement.

What will happen to changes coming in from LibreSSL or BoringSSL?