Browse Source

updated license to v1.2

remotes/origin_old/ugfx_release_2.6
Joel Bodenmann 8 years ago
parent
commit
110191f68d
  1. 13
      license.html

13
license.html

@ -2,7 +2,7 @@
<!-- saved from url=(0028)http://ugfx.org/license.html -->
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta charset="utf-8">
<title>GFX License, version 1.1</title>
<title>GFX License, version 1.2</title>
<!--[if lt IE 9]>
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
@ -100,7 +100,7 @@
<dt>1.12. Commercial Use</dt>
<dd><p>means any use of the Works that may result in income or equivalent benefit in any form. Examples of Commercial Use include; selling an Application or Device containing the Works,
offering paid support to modify the Works, selling a library containing the Works. Examples of use that are NOT Commercial Use include; using the Works for Education, use of the Works in hobbyist projects that have no expectation of income, use of the Works in building what will later become a Commercial Use product.
Note that Commercial Use does not the prototyping and preparation for income generating activities - only the income producing activity itself.</p></dd>
Note that Commercial Use does not include the prototyping and preparation for income generating activities - only the income producing activity itself.</p></dd>
</dl>
<h2>2. Non Commercial Use</h2>
@ -116,7 +116,7 @@
<h3>2.2. Distribution of Executable form</h3>
<p>If You distribute the Works in an Executable form then:</p>
<ol type="a">
<li><p>and You must inform recipients of the Executable form that it contains the Works and how they can obtain a copy of the Works in Source Code Form from the License Owners master repository; and</p></li>
<li><p>You must inform recipients of the Executable form that it contains the Works and how they can obtain a copy of the Works in Source Code Form from the License Owners master repository; and</p></li>
<li><p>Any modification to the Works must be contributed to the License Owners as per Section 4 prior to distribution; and</p></li>
<li><p>You may distribute such Executable form under the terms of this License, or license it under different terms, provided that the license for the Executable form does not allow for Commercial Use of the Works or attempt to limit or alter the recipients' rights in the Source Code Form under this License.</p></li>
</ol>
@ -125,7 +125,7 @@
<h3>3.1. Commercial Use Agreement</h3>
<p>A "Commercial Use Agreement" explicitly signed by the License Owner will override any specified terms of this License for the party to the agreement under the terms of the agreement. All other terms of this License will still apply.</p>
<h3>3.2. Distribution</h3>
<p>Other than as provided for in a signed "Commercial Use Agreement", where there is a Commercial Use involved or implied; you are not permitted to distribute the Works, in any form, either in source code or Executable form,
<p>Other than as provided for in a signed "Commercial Use Agreement", where there is a Commercial Use involved or implied, you are not permitted to distribute the Works in any form, either in source code or Executable form,
either as software or on a device or in any other way.</p>
<h2>4. Contributions</h2>
@ -177,7 +177,8 @@
<p>You may distribute the Works under the terms of the version of the License under which You originally received the Works, or under the terms of any subsequent version published by the license steward.</p>
<h3>12.3. Modified Versions</h3>
<p>If you create software not governed by this License, and you want to create a new license for such software, you may create and use a modified version of this License if you rename the license and remove any references to the name of the License Owner (except to note that such modified license differs from this License).</p>
<h3>13. Source Code License Notice</h3>
<p>Where ever possible the source code for the Works is to contain a header as per Exhibit A. Where this would be syntactically incorrect then modifications to allow syntactic parsing by a compiler are allowed but only to the extent that they allow correct syntactic parsing. If it is not possible to put the notice in a particular file, then You may include the notice in a location where a recipient would be likely to look for such a notice such as a “license.txt” file in a relevant directory.</p>
<h2>Exhibit A - Source Code Form License Notice</h2>
<pre>/*
* This file is subject to the terms of the GFX License. If a copy of
@ -186,7 +187,5 @@
* http://ugfx.com/license.html
*/
</pre>
<p>If it is not possible or desirable to put the notice in a particular file, then You may include the notice in a location (such as a LICENSE file in a relevant directory) where a recipient would be likely to look for such a notice.</p>
</body></html>

Loading…
Cancel
Save