License

General Baseline License
JogAmp's general baseline license is the New BSD 2-Clause License or 3-Clause BSD License.

TL;DR Legal on BSD-2-Clause and BSD-3-Clause gives a quick overview of its features and Wikipedia has a comparison chart.

Bottom line, JogAmp's license goal is to be most permissive while refusing to be liable for its usage.

However, some modules might contain less permissive licensed elements for building the to be distributed artifacts and some may even optionally distribute build artifacts with a less permissive license as shown below.

License Details of each JogAmp Module

 * [/git/?p=gluegen.git;a=blob;f=LICENSE.txt GlueGen's License]
 * Source Code: 2 + 3-Clause BSD License
 * Build Artifacts: 2 + 3-Clause BSD License
 * Build Time Artifacts in Repository: Miscellaneous Licenses but Open Source
 * [/git/?p=joal.git;a=blob;f=LICENSE.txt JOAL's License]
 * Source Code: 3-Clause BSD License
 * Build Artifacts: 3-Clause BSD License
 * Build Time Artifacts in Repository: 3-Clause BSD License
 * [/git/?p=jogl.git;a=blob;f=LICENSE.txt JOGL's License]
 * Source Code: 2 + 3-Clause BSD License + Optional other Permissive Licensed Material
 * Build Artifacts: 2 + 3-Clause BSD License + Optional other Permissive Licensed Material
 * Build Time Artifacts in Repository: Miscellaneous Licenses but Open Source
 * Additional Source Code Licenses are:
 * Apache License 2.0 (One w/ 1.1 + 2.0 Dual License)
 * SGI Free-B and MIT style permissive licenses
 * Ubuntu Font License 1.0
 * Optional: Oculus VR SDK License 3.1 or 3.2 for sub-module oculusvr-sdk
 * [/git/?p=jocl.git;a=blob;f=LICENSE JOCL's License]
 * Source Code: 2-Clause BSD License
 * Build Artifacts: 2-Clause BSD License
 * Build Time Artifacts in Repository: 2-Clause BSD License

Note about our Copyright Holder
Most important, all original authors have given consent to the license when contributing to the project.

One might have noticed that the entity used to hold the copyright for the 2 or 3 Clause BSD License is quite often a non-existing legal entity or non-natural person like JogAmp Community.

We have chosen this path as the license's goal is permissive and third parties can retrieve the actual author and hence original copyright holder via the source repositories.

In case of any disputes, it is important to us that we are able to identify contributions and resolve the matter at hand to keep the overall license valid, see below.

As of April 2019, majority of contributions came from Sven Gothel for ''Göthel Software e.K., followed by the historical contributions of Sun Microsystems and new contributors.

License Audits
We have performed two license audits with 3rd parties and both results were satisfactory for all involved parties, i.e. our license claims were correct and no other material with a more restrictive license has been included.

The audits further scanned the repositories at the time of the audit and have not found any 3rd party code licensed differently or being wrongly injected from other commercial projects.


 * 2010 Eclipse Foundation
 * 2011 Siemens AG E D EA

Details and communication of both audits are available to Göthel Software e.K..

Respect Copyright Law
When contributing to the JogAmp project, be sure not to include any code or data that you can't legally donate to the JogAmp community. For example, you shouldn't cut and paste code from some other commercial or less permissive licensed open-source project without appropriate attribution. This could put JogAmp's own open-source licensing status in jeopardy and would require painstaking efforts to remove the violating code.

Traceable Contributions
As noted above, it is important to us that we are able to identify contributions and resolve the matter at hand to keep the overall license valid.

This was also one crucial element of the first two license audits in 2010 and 2011 as mentioned above.

Therefor, we ask contributors to either use their real world name (preferable) or alternatively to have their real world name at least deposited with us. This is especially true when it comes to source code contributions. Note: Of course, we can not and do not verify the identity given to us.