OSS License compatibility

[Ashley123456789]

Description

There’s some possible confusion on the license of your repository when you combine other open-source code.
You can select another proper license for your repository, or write a custom license with license exceptions if some license terms couldn’t be summed up consistently

Rationale

The module {{cookiecutter.project_slug}} claims its license as dynamically changing among MIT license, BSD-3-clause, GPL v3, and Apache-2.0. However, the license of your whole project is shown as a BSD-3-clause license in LICENSE, i.e., less strict than GPL v3 and Apache-2.0 on license terms, which has impacted the whole license compatibility in your repository and may bring legal and financial risks, if GPL v3 or Apache-2.0 is chosen sometime.

[browniebroke]

Hey! Thanks for raising this. I'm not quite sure I understand what you're suggesting...

Also, there is #1213 which was raising some concern about licenses compatibility, and has valuable context.