Apereo/Sakai Licenses are now managed from http://www.apereo.org/licensing/agreements
Using 3rd Party Software in Sakai
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 Apereo 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.
The following workflow describes the process of evaluating 3rd party code and/or libraries for inclusion in the Sakai project. The basic idea is that as developers identify code that would be useful in meeting development objectives, they must follow this process to ensure that the conditions of the new code's license are compatible with the Sakai license and distribution practices.
P1. Identify 3rd party code
P2. Initiate assessment
Before beginning to use any 3rd party code, the developer must initiate a conversation with the Licensing WG. Members of the Licensing WG will work with the developer to determine compatibility and any requirements that go along with using the new software. The steps for this stage are:
- 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 firstname.lastname@example.org 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.
D1. Ok to distribute?
P3. Initiate conversation with author
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 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.
If negotiation with the author is successful, proceed to P5. If unsuccessful, proceed to P4.
P4. Find alternative, or alternative way to distribute
- 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 Apereo Foundation from the chain of responsibility.
P5. Document use and initiate any requirements
If the work in question is deemed acceptable to use. It's use must be documented on the Library and Licensing Information page in the Licensing Space. Any requirements for licensing and/or attribution must also be put in place. Often this involves:
- Adding the 3rd party license(s) to the licenses folder at the top of the distribution.
- Adding proper attribution to the Acknowledgments Screen .
In all cases, be sure to obey the licensing constraints of the original author. See Applying the ECL for more information.
Status of 3rd Party Licenses
The following table indicates 3rd party licenses which have been evaluated and determined to be either compatible with the Apereo Foundation's licensing practices, or incompatible. Each license is linked to a page that describes the requirements for use.
Code/libraries using this license are approved for use. Follow usage instructions.
Code/libraries using this license may not be used.
License currently under evaluation.
License may be used under some conditions. Check with Licensing WG.
License and usage instructions
JSR 170/Day Management AG