The Sakai software distribution(s) use 3rd party code and libraries developed by other individuals and organizations and licensed under specific terms deemed compatible with the ECL and the SFApereo Foundation's policies.
If you are planning to use any 3rd party code in developing for Sakai, please follow the process outlined below to ensure that the 3rd party code is license-compatible with Sakai and its use in Sakai is properly documented.
- Developer completes an initial checklist .
- Developer then creates a Jira Task against the Licensing component, and attaches the checklist document to it.
- Developer sends an email to licensing@email@example.com citing the Jira.
If the code's license has already been identified as one that is compatible with Sakai, then you still need to work with the Licensing WG to document your use of it and ensure that you meet the license requirements for documentation and acknowledgment in your code. Skip to step |#P5.
If the initial assessment determined that the terms are not acceptable, the developer may wish to contact the author and request that the author grant Sakai the right to distribute the code under more acceptable terms. The best way to do this is by using a standard request email template asking the author to execute a contribution of the code to the Sakai Apereo Foundation. Other acceptable outcomes would be permission to use the work under the terms of the ECL, Apache 2.0 license, or another compatible license.
- Find an alternative.
- Find an alternative method of distribution. It may be acceptable to have the end user download the work in question themselves, removing the Sakai Foundation from Apereo Foundation from the chain of responsibility.
The following table indicates 3rd party licenses which have been evaluated and determined to be either compatible with the Sakai Apereo Foundation's licensing practices, or incompatible. Each license is linked to a page that describes the requirements for use.
License and usage instructions
JSR 170/Day Management AG