From: Daniel Stenberg Date: Sat, 29 Jan 2011 22:52:40 +0000 (+0100) Subject: FAQ: clarified/expanded 6.7 a bit X-Git-Tag: curl-7_21_4~29 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=819dfddc58e22ea2248851bcd1b4605a0de2a9e4;p=curl FAQ: clarified/expanded 6.7 a bit "6.7 What are my obligations when using libcurl in my commercial apps?" got the piece about what exactly "in all copies" mean to a user of the code. This interpretation is based on what other MIT-like licenses have made more explicit. --- diff --git a/docs/FAQ b/docs/FAQ index b4e945bc6..5f1740b43 100644 --- a/docs/FAQ +++ b/docs/FAQ @@ -1,4 +1,4 @@ -Updated: January 24, 2011 (http://curl.haxx.se/docs/faq.html) +Updated: January 29, 2011 (http://curl.haxx.se/docs/faq.html) _ _ ____ _ ___| | | | _ \| | / __| | | | |_) | | @@ -1347,12 +1347,16 @@ FAQ You do not have to reveal or make public any changes to the libcurl source code. - You do not have to reveal or make public that you are using libcurl within + You do not have to broadcast to the world that you are using libcurl within your app. - As can be seen here: http://curl.haxx.se/docs/companies.html and - elsewhere, more and more companies are discovering the power - of libcurl and take advantage of it even in commercial environments. + All we ask is that you disclose "the copyright notice and this permission + notice" somewhere. Most probably like in the documentation or in the section + where other third party dependencies already are mentioned and acknowledged. + + As can be seen here: http://curl.haxx.se/docs/companies.html and elsewhere, + more and more companies are discovering the power of libcurl and take + advantage of it even in commercial environments. 7. PHP/CURL Issues