path: root/COMPLIANCE
diff options
authorCarsten Haitzler (Rasterman) <>2013-03-22 17:40:56 +0900
committerCarsten Haitzler (Rasterman) <>2013-03-23 13:29:13 +0900
commit10fe8f29e387c72fddb6b0fcde5bad4c0243c23d (patch)
treef7199241fd4b4fab1f64c2993723aeb7a25a31ef /COMPLIANCE
parent46be79a206bc90d844e7589605505e7ac8804307 (diff)
add a COMPLIANCE file for convenience.
Diffstat (limited to 'COMPLIANCE')
1 files changed, 71 insertions, 0 deletions
new file mode 100644
index 0000000000..1ee00231ae
--- /dev/null
@@ -0,0 +1,71 @@
3 This is not a legal notice, so do not treat it as one. This is
4intended as "plain English" advice for the average person to ensure
5they comply with licenses in this software in the most simple way. It takes
6the position of "comply with the MOST restrictive license in this
7aggregation and then you will comply with all." If you have any doubts,
8please consult the full license COPYING files and a lawyer. Take this
9as a rough guide.
11The simple advice
13 Do this and you won't go too wrong.
151. Provide the content of ALL of the COPYING, AUTHORS and licenses/COPYING.*
16files as printed material with your product and/or in a dialog (e.g.
17an "about" dialog) in your product user interface.
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
20binaries for your product that ships EFL. Keep this URL valid for the
21lifetime of the product.
223. Unless you are doing PS3 (PSl1ght) development any libraries or
23applications you write that use EFL are yours and you do not need to
24make the source available.
254. If you made changes to EFL it would be appreciated if you
26interacted with us (see ) and provided the
27changes 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
29created problems you do not know of yet.
33Q. Where is the licensing information?
34A. See the COPYING file here and then the COPYING.* files inside the
35licenses directory that it references. These are the proper legal
36pieces of information you will need.
38Q. Do I need to make the source public of libraries or applications that I
39build on top of EFL?
40A. No, UNLESS you use the escape library. Escape is GPL. This is ONLY
41needed for PS3 development, so unless you are doing this, it is not
44Q. Do I need to provide the source for EFL?
45A. 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
47used to build those binaries. So stick to doing this and you'll be fine.
49Q. 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
51product that ships the EFL libraries/tools that gives a URL from
52which the source can be downloaded EXACTLY as you used to compile EFL.
53You may not simply point to upstream repositories and pass the problem
54to someone else. You MUST provide the source exactly as used.
56 You MAY also provide the source code itself on the product itself
57(e.g. on its filesystem) (provide the tar archives of the source), or in
58place of a download link if you do not believe you will be able to
59maintain that download link for the lifetime of the product.
61 You MAY also (or instead of the above 2) provide the source on media
62(CD, DVD, flash etc.) that accompany the product.
64 Choose 1 or more of the above methods and you will be fine.
66Q. Do I need to reproduce the license information in the COPYING* files?
67A. Yes. You must provide these with your product, and just like the
68source 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
70material (manuals, papers) that accompany the product or in CD, DVD
71etc. media.