Contents of /licenses/4F

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.2 - (show annotations) (download)
Tue Aug 2 07:00:58 2011 UTC (8 years, 6 months ago) by mr_bones_
Branch: MAIN
Changes since 1.1: +0 -0 lines
remove unused license

1 <HTML>
2 <HEAD>
5 DT { font-weight: bold; }
6 </STYLE>
7 </HEAD>
8 <BODY>
11 <B>Revision:</B> 2 November 2, 2002
12 <P>
13 This license is (C) Copyright 2002 Lameter Corporation,
14 7131 Cabernet Ave, Newark, CA 94560, United States of America, http://lameter.com christoph@u-OS.org
15 </P>
16 <P>
17 Distribution of exact copies of this license agreement is allowed and must
18 be redistributed with all modifications and enhancements to this product.
19 </P>
20 <P>
21 The text of section 1 might be changed if this license agreement is
22 to be applied by a copyright holder for another software product.
23 </P>
24 <P>
26 Please contact the license holder(s) for details.
27 </P>
28 <P>Note that this license is in its early stages of formulation. It will most likely be refined in the next weeks.
29 Ultimately a non-profit should be the license holder and not a commercial entity. It might take awhile until
30 the necessary organization and funds are available to start such a non-profit organization.
31 Comments are appreciated. Please respond to christoph@u-OS.org.</P>
33 <H1>SECTION ONE: The software under the 4F License</H1>
34 <DL>
35 <DT>Name of the Software Product<DD>uPM - Micro Package Manager
36 <DT>Short Description<DD>uPM is a package management system with source build and archive maintenance capability
37 <DT>License Holder<DD>Lameter International Corporation, 7131 Cabernet Ave, Newark, CA 94560, http://lameter.com info@lameter.com
38 <DT>Distribution License<DD>4F Class D
39 </DL>
40 <H1>SECTION TWO: The 4F License</H1>
41 <P>The aim of this license is not to restrict your rights. <i>4F Licensing</i> was developed to preserve the four freedoms when using a software product:
42 </P>
43 <OL>
44 <LI>The freedom to obtain and review the source code for the software product. The <i>4F license</i> requires that the source be made
45 available for software products distributed under 4F licenses.
46 <LI>The freedom to redistribute the source code and the binary. The <i>4F license</i> gives anyone the right to redistribute
47 the source as well as the binaries.
48 <LI>The freedom to modify the source code and redistribute the modifications.
49 <LI>The freedom to use software for any purpose by any person.
50 </OL>
51 <P><i>4F Licensing</i> protects your and other persons rights to make use of these freedoms.
52 Redistribution is only allowed if the person you are distributing to will also have the Four Freedoms.
53 A 4F License becomes invalid if those rights are not given. And this license is the only legal justification for the
54 use, modification and deployment of this software.
55 </P>
56 <P>We have chosen not to use the typical terms <b>Free Software</b> or <b>Open Source Software</b>
57 because both terms have led to a wrong understanding of this type of licensing in the past.
58 The concern of free or open source licensing is <b>not</b> to get the software for free
59 (meaning one does not have to pay any money for it) but to preserve the Four Freedoms.
60 The term <b>Free Software</b> typically leads to that misunderstanding.
61 The term <b>Open Source</b> often seems to avoid mentioning the Four Freedoms that need to be preserved.
62 It also gives rise to the misunderstanding that the access and ability to view the source code is sufficient.
63 <P>
64 We have chosen the term 4F (long <i>Four Freedoms</i>) because it does not have the baggage of the other terms
65 and clearly expresses the purpose of <i>Free</i> or <i>Open Source</i> Licenses.
66 <P>
67 <i>4F Licensing</i> allows different grades
68 of protection of these rights. If a <i>4F licensed</i> product is combined with other products the four freedoms might no
69 longer be applicable to the whole. <i>4F licensing</i> defines CLASSES of protection. A later class requires that the requirements of all earlier classes be fulfilled too. The following classes exist:
71 <TR><TH>Class</TH><TH>Description</TH></TR>
72 <TR><TD>A</TD><TD><B>No protection</B>.
73 The sourcecode might be modified and redistributed under other licenses at will.
74 4F Class A licenses are similar to BSD licensed code.
75 The only provision is that credit is given to the authors of the code in the final product.</TD></TR>
76 <TR><TD>B</TD><TD><B>Protection for the software product itself</B>.
77 The Four Freedoms must be preserved for all modifications of the source code that are distributed.
78 The product might be combined (f.e. linked into) other software that is licensed differently.
79 The combination of other software plus the software product might not preserve the Four Freedoms.
80 Class B licensing is similar to the protection offered by the LGPL.
81 </TD></TR>
82 <TR><TD>C</TD><TD><B>Program (Executable) protection</B>.
83 The Four Freedoms must be preserved for all binaries generated.
84 If a piece of software is used for the generation of a binary
85 then all sourcecode that was used to generate the binary and all shared
86 objects loaded must also be made available under the Four Freedoms.
87 If this is not possible then the combination or the production
88 of the binary is not permitted under this license.
89 </TD></TR>
90 <TR><TD>D</TD><TD><B>Media / Site protection.</B>.
91 The software might not be distributed on media combined with software not preserving
92 the four freedoms. This means that publication on a CD that contains non 4F compliant software is not
93 permitted. The medium and all content must be sharable under the Four Freedoms principle.
94 The same is true for publication of ftp sites.
95 Publication on ftp sites that also distribute non 4F compliant software is not permitted.
96 CDs and ftp site contents must be freely redistributable and modifiable in order to satisfy Class D.
97 </TD></TR>
98 <TR><TD>E</TD><TD><B>System protection.</B>.
99 The Four Freedoms must be preserved for all software installed under the same Operating System and all software
100 used to install the system and any software on it.
101 The license becomes invalid if software is present under the installation
102 with the same operating system that contain software not conformant to 4F licensing.
103 Specifically this prohibits installation of proprietary software (such as Microsoft Software) under the same installed
104 operating system as a Class E product.
105 </TD></TR>
106 <TR><TD>F</TD><TD><B>Organizational protection</B>. The software might not be used by an organization/group/corporation that
107 is combining the use of the software so licensed with software that does not provide the Four Freedoms.
108 </TD></TR>
109 <TR><TD>G</TD><TD><B>Protection for program interaction</B>. The software must be deployed in such a way that it does not interact (transfer data to/from, use documents formatted by) non 4F compliant software.</TD></TR>
110 </TABLE>
111 <P>
112 4F licensing aims to be conforming to the DFSG (Debian Free Software Guidelines http://www.debian.org), the OSI criteria
113 for free software licenses (Open Source Initiative see http://www.opensource.org) and the free software criteria of the
114 Free Software Foundation (The GNU project see http://www.gnu.org).
115 Only Classes A-C are compliant with the criteria of the those organizations since protection against loss of the Four Freedoms by aggregation is only permitted for binaries.
116 </P>
117 <H1>SECTION THREE: Warranty</H1>
118 <P>
119 The software is provided and licensed free of charge therefore there is no
120 warranty for the software to the extent permitted by applicable law.
121 </P><P>
122 This license is void in legal context where a law makes the copyright holder
123 or any contributor provide a warranty for this software that was provided free of charge.
124 </P><P>
125 There is no warranty unless otherwise stated in writing by the copyright holders.
126 The software is provides "as-is" without warranty of any kind, either expressed
127 or implied, including, but not limited to, the implied warranties of merchantability
128 and fitness for a particular purpose. The entire risk of using this software
129 is with the user of this program. Should this software fail then the user will
130 assume the cost of all necessary services, repairs, corrections or whatever
131 else is necessary to remedy the situation.
132 </P>
133 <H1>SECTION FOUR: Liability</H1>
134 <P>
135 In no event unless required by applicable law or agree to in writing will any
136 copyright holder, or any other party who may have modified and/or redistributed
137 the software under the regulations of this license be liable to you for damages
138 including any general, special, incidental or consequential damages arising out
139 of the use or inability to use the software (including but not limited to loss
140 of data or data being rendered inaccurate or losses sustained by the user or
141 third parties or a failure of the software to operate with any other software), even
142 if such holder or other party has been advised of the possibility of such damages.
143 </P><P>
144 This license is void if the above limitations are rendered ineffective by law or
145 judicial decision.
146 </P>
147 <H1>SECTION FIVE: Definition of Terms</H1>
148 <P>
149 <DL>
150 <DT>4F Conformant License<DD>
151 A conformant license is a license that is conformant to the Free Software/Open Source principles.
152 OSI accredited licenses (see http://www.opensource.org) are
153 4F conformant. So is any license that allows the exercise
154 of the Four Freedoms. Examples of conformant licenses are:
155 <UL>
156 <LI>4F Licenses
157 <LI>GPL (is a 4F Class C compliant license)
158 <LI>LGPL (is a 4F Class B compliant license)
159 <LI>BSD (is a 4F Class A compliant license)
160 <LI>Public Domain (is 4F Class A compliant)
161 </UL>
162 </DL>
163 <P>
164 </BODY>
165 </HTML>

  ViewVC Help
Powered by ViewVC 1.1.20