-aware of all licenses covering the source code and other materials
-(such as documentation and images) in your software. Make sure
-to document them properly. Make sure that the licenses
-covering the source code are compatible to each other (e.g. you cannot
-release under the GPL_ if the license of some other part of your code says
-"must not be used on Thursdays"). The easiest way to avoid unnecessary
-complications is to use a `standard license`_ (such as BSD, or GPL) that
-are known and have been evaluated by legal experts regarding their
-implications and their compatibility with each other. Beware that
-standard licenses created to cover programs source code are not always
-appropriate for content (e.g. images and documentation) or data (which
-might not even be copyrightable in some jurisdictions such as USA). You
-can find some of popular licenses for content and data on
-`Open Knowledge Definition (OKD)
-<http://www.opendefinition.org/licenses>`_ website. For any license, check if your legal
-terms comply with the `open-source definition`_ or the `Debian free software
+aware of all licenses covering the source code and other materials (such as
+documentation and images) in your software. Make sure to document them
+properly. Make sure that the licenses covering the source code are
+compatible to each other (e.g. you cannot release under the GPL_ if the
+license of some other part of your code says "must not be used on
+Thursdays"). The easiest way to avoid unnecessary complications is to use a
+`standard license`_ (such as BSD, or GPL) that are known and have been
+evaluated by legal experts regarding their implications and their
+compatibility with each other. For any license, check if your legal terms
+comply with the `open-source definition`_ or the `Debian free software