summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarsten Haitzler (Rasterman) <raster@rasterman.com>2013-10-30 19:27:26 +0900
committerCarsten Haitzler (Rasterman) <raster@rasterman.com>2013-10-30 19:27:26 +0900
commitb3debcc3e1651e41c419db422b465d9070c180b4 (patch)
tree9113f7cc3b9707898f458194f4f16540814db4d7
parent309e287b7c5ca4fb505d7756748d01da5c0fc203 (diff)
compliance/licensing - clarify, fix formatting and point to tldrlegal.com
-rw-r--r--COMPLIANCE24
-rw-r--r--COPYING2
2 files changed, 19 insertions, 7 deletions
diff --git a/COMPLIANCE b/COMPLIANCE
index 1ee0023..ecd0c34 100644
--- a/COMPLIANCE
+++ b/COMPLIANCE
@@ -16,14 +16,16 @@ The simple advice
16files as printed material with your product and/or in a dialog (e.g. 16files as printed material with your product and/or in a dialog (e.g.
17an "about" dialog) in your product user interface. 17an "about" dialog) in your product user interface.
182. Provide a URL from which to be able to download "tar files" with 182. Provide a URL from which to be able to download "tar files" with
19ALL of the source of EFL exactly as it was when used to compile the 19ALL of the source of this software exactly as it was when used to compile the
20binaries for your product that ships EFL. Keep this URL valid for the 20binaries for your product. Keep this URL valid for the lifetime of the product.
21lifetime of the product.
223. Unless you are doing PS3 (PSl1ght) development any libraries or 213. Unless you are doing PS3 (PSl1ght) development any libraries or
23applications you write that use EFL are yours and you do not need to 22applications you write that use EFL are yours and you do not need to
24make the source available. 23make the source available. That means if you link to EFL dynamically.
24If you copy in EFL source into your application or library or
25statically link, then you will need to provide full source of whatever
26statically links or copies any of this software into yours.
254. If you made changes to EFL it would be appreciated if you 274. If you made changes to EFL it would be appreciated if you
26interacted with us (see http://www.enlightenment.org ) and provided the 28interacted with us (see http://www.enlightenment.org) and provided the
27changes you made in patch form BEFORE you ship a product, so they may 29changes you made in patch form BEFORE you ship a product, so they may
28be reviewed to see if you have made any mistakes and perhaps have 30be reviewed to see if you have made any mistakes and perhaps have
29created problems you do not know of yet. 31created problems you do not know of yet.
@@ -44,7 +46,7 @@ relevant.
44Q. Do I need to provide the source for EFL? 46Q. Do I need to provide the source for EFL?
45A. Yes. In general you do. If you are shipping any of the binaries or 47A. Yes. In general you do. If you are shipping any of the binaries or
46libraries that are produced, you must provide the EXACT source code 48libraries that are produced, you must provide the EXACT source code
47used to build those binaries. So stick to doing this and you'll be fine. 49used to build those binaries.
48 50
49Q. If I have to provide source, how should I do this? 51Q. If I have to provide source, how should I do this?
50A. The best way is to provide a reference in an "about" dialog in the 52A. The best way is to provide a reference in an "about" dialog in the
@@ -69,3 +71,13 @@ source code, provide them as part of the user interface in full (e.g.
69in a dialog), or as files in the filesystem, on actual printed 71in a dialog), or as files in the filesystem, on actual printed
70material (manuals, papers) that accompany the product or in CD, DVD 72material (manuals, papers) that accompany the product or in CD, DVD
71etc. media. 73etc. media.
74
75Q. Is there a simpler list of do's and don'ts i can use?
76A. Yes. See http://www.tldrlegal.com. specifically:
77
78http://www.tldrlegal.com/license/bsd-2-clause-license-(freebsd)
79http://www.tldrlegal.com/license/gnu-lesser-general-public-license-v2.1-(lgpl-2.1)
80http://www.tldrlegal.com/license/gnu-general-public-license-v2-(gpl-2)
81http://www.tldrlegal.com/license/zlib-libpng-license-(zlib)
82
83Then match this up with the licensing listed in COPYING.
diff --git a/COPYING b/COPYING
index 3aa431f..80f87c3 100644
--- a/COPYING
+++ b/COPYING
@@ -20,7 +20,7 @@ evas: licenses/COPYING.BSD
20embryo: licenses/COPYING.SMALL 20embryo: licenses/COPYING.SMALL
21ecore: licenses/COPYING.BSD 21ecore: licenses/COPYING.BSD
22eio: licenses/COPYING.LGPL 22eio: licenses/COPYING.LGPL
23eldbus: licenses/COPYING.LGPL 23eldbus: licenses/COPYING.LGPL
24efreet: licenses/COPYING.BSD 24efreet: licenses/COPYING.BSD
25eeze: licenses/COPYING.BSD 25eeze: licenses/COPYING.BSD
26ephysics: licenses/COPYING.BSD 26ephysics: licenses/COPYING.BSD