Apache 2.0 License is incompatible with GPL v2

[dralley]

Describe the bug

It appears that this library used to be licensed as MIT and eventually switched to Apache 2.0 for patent protections: #175

This is understandable but unfortunate because the Apache 2.0 license is not compatible with the GPL v2 license (at least according to the FSF, opinions on this differ).

The standard workaround for this (very common in the Rust community) is to license projects as MIT OR Apache 2.0, which means that contributions invoke the Apache 2.0 protections but downstream users can choose which license they want to accept the code under.

It would be excellent if aiohttp followed this strategy.

To Reproduce

N/A

Expected behavior

N/A

Logs/tracebacks

N/A

Python Version

N/A

aiohttp Version

$ python -m pip show aiohttp

multidict Version

$ python -m pip show multidict

yarl Version

$ python -m pip show yarl

OS

N/A

Related component

Server

Additional context

No response

Code of Conduct

• I agree to follow the aio-libs Code of Conduct