Child pages
  • Applying the ECL
Skip to end of metadata
Go to start of metadata


Apereo/Sakai Licenses are now managed from

Applying the Educational Community License, Version 2.0

The following is to provide guidance for software developers, both inside and outside the Sakai projects, to understand what they need to do to apply the Educational Community License, Version 2.0 (ECLv2), to their own or the Sakai project's software, including source code, documentation, and binary distributions. It is not intended to supplant or otherwise modify any of the terms within the license itself.

Understanding the License

The ECLv2 consists of a set of copyright licensing terms that are documented in the ecl2.txt file. The license terms are written in such a way that they can be used by anyone, not just the Apereo Foundation and the Sakai Project, and can be applied by reference to the versioned license terms.

Applying the license to a Sakai software distribution

The Sakai software distribution is an aggregation of software developed and copyrighted by multiple parties. The distribution as a whole is licensed under the ECL by the Apereo Foundation. Individual source files, libraries, and other contributions frequently must retain acknowledgements and copyright notices.

The ECL is applied to the Sakai software distribution by:

  1. Placing the following copyright statement in the footer of the application as it is rendered by default:

    Copyright 2003-2011 The Sakai Foundation. All rights reserved. Portions of Sakai are copyrighted by other parties as described in the Acknowledgments screen.

  2. Maintaining an accurate and complete Acknowledgments Screen That includes the following statement followed be a detailed list of acknowledgments:

    Copyright 2003-20011 The Apereo Foundation. All rights reserved. Sakai is licensed for use pursuant to the Educational Community License, Version 2.0 . Portions of Sakai are copyrighted by other parties, including the parties listed below, and you should see the licenses directory for complete copyright and licensing information.


  3. Placing the ecl2.txt file in the root of the licenses folder of the source distribution.

Applying the license to individual source files and libraries

The license is applied to each source file (code and documentation by including a short copyright notice at the top, as demonstrated below:

Copyright [yyyy] [name of copyright owner]
Licensed under the Educational Community License, Version 2.0 (the "License"); 
you may not use this file except in compliance with the License. 
You may obtain a copy of the License at 
Unless required by applicable law or agreed to in writing, software 
distributed under the License is distributed on an "AS IS" BASIS, 
See the License for the specific language governing permissions and 
limitations under the License.

Source files contributed to or developed as part of the Sakai Project should begin with a copyright notice like

Copyright 2005 The Apereo Foundation.
Copyright 2003-2005 The Apereo Foundation.
Copyright 2003,2005 The Apereo Foundation.

where the years given start with the first publication year of the file contents (the authored expression) and include a range of years for each year that new significant content (derivative work) is published within the file. Since the SF publishes its code in public source code modules (CVS and Subversion), we generally want to include a range of years starting with the year of origin. Do not worry about consistency in the first year – it is not supposed to be uniform and should never be dated prior to the year of first creation.

If the distribution also contains source files not owned by the SF, such as third-party libraries, then be sure to leave their licenses intact. Follow the process for evaluating third-party code for use in Sakai.

  • No labels

1 Comment

  1. Just to re-iterate if there are questions about the ability to obey the licensing constraints look at the to see how to resolve them.

    It is a lot harder to clean up code that depends on something that can't be distributed than it is to avoid that problem in the first place. Any critical third party code should be examined up front.