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