- License of resources (libraries, tools, fonts, images, everything) which are installed via npm or any other package manager (what means that they are not part of our repository) and are not included in any form in any release package do not concern us. It means that as long as a resource (or any its parts) is not included in our repository or any release package, we can freely use it (of course, as long as we have rights to use it). Example: licenses of your operating system or a LESS compiler are not a problem even if these tools were licensed under GPL. Example 2: You cannot use Photoshop if you haven't bought a license for it.
- Before using any resource that does not fall into the previous category, consult with WW, FCK or PK if its license does allow this.
Project specific rules
- Licenses of all resources included in the
ckeditor-devrepository or any release package must be specified in "Sources of Intellectual Property Included in CKEditor" section of the
LICENSE.mdfile and full text of their licenses must be included as appendix in this file. Note: This section is divided into source code and release code sections.
- If a 3rd party resource is concatenated with our resource, then the result file must include our license pointing to the
LICENSE.md(which mentions that a file XYZ contains a resource Foo licensed under Bar). Other licenses may be removed (so the result file contains only one license comment).