The Fluid community is a network of open source projects and contributors who are dedicated to inclusive design. Fluid supports a variety of tools and resources, each of which may be distributed under different licenses. In general, we advocate for "open-open" licensing models in which anyone can freely contribute, and which place few restrictions on modification, redistribution, or use in commercial or other open source projects.
This page documents the licenses, agreements, and associated documentation used by Fluid-supported projects such as Infusion, FLOE, the Social Justice Repair Kit, and others.
Source Code Licenses
Two primary source code licenses are used by Fluid community projects:
Fluid-supported projects are free to choose other licenses or to use multiple licenses if appropriate. New projects are encouraged to use the 3-Clause BSD license.
Documentation, in this context, includes all resources shared by contributors to the Fluid community, except for software source code. This includes:
- Design resources, mock-ups, wireframes, functional requirements, and work-in-progress
- Logos, style guides, icons, and image assets
- Examples, tutorials, and application programming interface (API) reference information
- Essays, notes, and documentation of the approach and thinking behind the design and development process
The Fluid community's documentation is licensed under several different versions of the Creative Commons Attribution license, including the Creative Commons Attribution 2.5 Canada and Creative Commons Attribution 3.0 Unported licenses. Please see individual project sites or repositories for details about the licensing of a specific project or resource.
All new documentation contributed to the Fluid community is licensed under the Creative Commons Attribution 4.0 International License. By contributing to the Fluid Project Wiki, you agree to share your work under the terms of this license.
License Headers and File Templates
Typically, a project or resource will include two different kinds of license declarations:
- A LICENSE.txt file at the root of the project's source code repository, which provides the full text of the license
- Headers at the top of each source code file, which list each major contributor to the file, and provide a link to the full text of the license
It is also possible to "override" the root LICENSE file by including an alternate LICENSE file in a subdirectory of the repository. For example, this could be used to declare the license of a third party library if it is included in the project's repository.
License File Template
Copyright <YEAR> <COPYRIGHT HOLDER>
Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
3. Neither the name of the copyright holder nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Source Code File Header
Copyright <YEAR> <COPYRIGHT HOLDER>
Copyright <YEAR> <OTHER COPYRIGHT HOLDER>
Licensed under the 3-Clause BSD license. You may not use this file except in compliance with this license.
You may obtain a copy of the 3-Clause BSD License at
Contributor License Agreements
Currently, the Fluid community asks each contributor to sign a Contributor License Agreement, which provides a clear agreement to share code under terms amenable to Fluid's licensing strategy. In order to publish source code in the Fluid repository, OCAD University needs permission from the creators of the code and from the organizations for which they work. The following agreements are provided for this purpose:
- Individual Contributor License Agreement (CLA) - to be signed by each code creator, covering any contributions made outside of the context of employment by an organization that owns the rights to the work
- Corporate Contributor License Agreement (CCLA) - to be signed by an appropriate person in an organization, which covers contributions made by employees when the owner owns the rights the work:
Signed agreements can be emailed, mailed, or faxed to Iris Neher at the Inclusive Design Research Centre.
The Fluid community is investigating more streamlined alternatives to our paper-based Contributor License Agreements.
Project-Specific Licensing Information
The Fluid Infusion Framework is released under both the ECL 2.0 and 3-Clause BSD licenses, making it widely compatible with a variety of open source licenses as well as commercial code.
Templates are available for an Infusion-compatible LICENSE file, containing the full text of both the ECL 2.0 and BSD licenses, and for the embedded source code license header are available.
Infusion's documentation site is distributed under the Creative Commons Attribution 3.0 Unported license.
Flexible Learning for Open Education (FLOE)
FLOE contributes to a variety of open educational resource community projects, such as PhET, PressBooks, the Global Public Inclusive Infrastructure, and other projects under the terms of their licenses. In addition, FLOE's reusable components and tools are licensed dually under the terms of the ECL 2.0 and 3-Clause BSD licenses.
FLOE's Inclusive Learning Design Handbook and Inclusive Design Guide are licensed under the Creative Commons Attribution 3.0 Unported.
Social Justice Repair Kit
The Social Justice Repair Kit tools are distributed under the 3-Clause BSD license.
SJRK's resources and guides are distributed under the Creative Commons Attribution 4.0 International License.