The top-level LICENSE file is unhelpful, as it suggests that there may be non-permissive licenses scattered through the repo but does not help the user to locate them.
It would be more helpful to the user if the content were to be explicit:
- Which files (or directory trees) are under different licenses, and whether they are permissive.
- Whether those files are part of the linkable library, build/test infrastructure, documentation, or optional examples.
It would also help if the contribution guidelines were revised to require that any further contributions be under a permissive license, to avoid making the problem worse.
The top-level LICENSE file is unhelpful, as it suggests that there may be non-permissive licenses scattered through the repo but does not help the user to locate them.
It would be more helpful to the user if the content were to be explicit:
It would also help if the contribution guidelines were revised to require that any further contributions be under a permissive license, to avoid making the problem worse.