Precisions on the licensing requirements

Add some precision on reviewing licensing requirements when adding
new dependencies.

Change-Id: I46bda1f9792c4cb01860dca3c3dbcbb4a0ea9287
This commit is contained in:
Thierry Carrez 2016-03-24 16:38:12 +01:00
parent f8cf7eba89
commit 0cb0425d42
1 changed files with 5 additions and 1 deletions

View File

@ -275,7 +275,11 @@ For new Requirements
- Is the library license compatible?
The library should be licensed as described in `Licensing requirements`_.
The library should be licensed as described in `Licensing requirements`_,
and the license should be described in a comment on the same line as the
added dependency. If you have doubts over licensing compatibility, like
for example when adding a GPL test dependency, you can seek advice from
Robert Collins (lifeless), Monty Taylor (mordred) or Jim Blair (jeblair).
- Is the library already packaged in the distros we target (Ubuntu
latest / Fedora latest)?