Return-Path: Delivered-To: apmail-legal-discuss-archive@www.apache.org Received: (qmail 27584 invoked from network); 1 Oct 2009 19:26:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Oct 2009 19:26:27 -0000 Received: (qmail 86539 invoked by uid 500); 1 Oct 2009 19:26:26 -0000 Delivered-To: apmail-legal-discuss-archive@apache.org Received: (qmail 86249 invoked by uid 500); 1 Oct 2009 19:26:24 -0000 Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: Reply-To: legal-discuss@apache.org List-Id: Delivered-To: mailing list legal-discuss@apache.org Received: (qmail 86241 invoked by uid 99); 1 Oct 2009 19:26:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2009 19:26:24 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of reddy.vikas@gmail.com designates 209.85.212.204 as permitted sender) Received: from [209.85.212.204] (HELO mail-vw0-f204.google.com) (209.85.212.204) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2009 19:26:14 +0000 Received: by vws42 with SMTP id 42so213862vws.17 for ; Thu, 01 Oct 2009 12:25:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=9pLpbim36qb8sFMeaqR8/DTmdXDRvSS8q5OZUYAZrfo=; b=GTPQg2j4zNo5lvJiZZuTdEK9rUltq/9yBab+6UoGXeP/e5XE0sA8IzjG39WGDwLA2o wvnc9nmATqQuthIQ/zqK10U8FEUAzHnZQU1zpeWfN4/SvikjL5yO5rz5lcXFHu8jKi+1 tAY1ObZioeWr5f3e4PRiNFVa+uIta760zw4tI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=QWdiZQsBaL2ljYWRyMbAq9F9UImUvPOEb00YeWijn9taXQITeD/E2ro4GsxhQkwHBS +T/y4ci+PqcyOeEudoPjSFnF+QaQAOjtphQn/0xz0i0QwkPNuLC5Pw7o1Ipc93tlXfbP 0QCGrJnh3gGO1salzeV/XxRHGoFdzq/iG6e+M= MIME-Version: 1.0 Received: by 10.220.44.136 with SMTP id a8mr2911613vcf.47.1254425153625; Thu, 01 Oct 2009 12:25:53 -0700 (PDT) Date: Thu, 1 Oct 2009 13:25:53 -0600 Message-ID: Subject: Using Apache 2.0 license in iPhone applications From: Vikas Reddy To: legal-discuss@apache.org Content-Type: multipart/alternative; boundary=001636832cb0ade6260474e49d87 X-Virus-Checked: Checked by ClamAV on apache.org --001636832cb0ade6260474e49d87 Content-Type: text/plain; charset=ISO-8859-1 Hi, this is my first time using a mailing list so apologies in advance if I commit any mailing list faux pas - please let me know if I have. Our company is currently using Apache 2.0 licensed code in our iPhone application which is distributed as a compiled binary - no source code. The Apache 2.0 license states that "You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: 1. You must give any other recipients of the Work or Derivative Works a copy of this License;" *For an iPhone application, what constitutes giving the recipients a copy of the work? *On the iPhone and many other mobile platforms, users have no direct access to the file system. In our application we have an info screen that has an attribution link that takes users to a webpage describing our use of the Apache 2.0 licensed code. This seems to fit better with the spirit of the license since otherwise users would have no way to see the license file. Is this the right approach with our application? Or can we simply include a text file. I came across one discussion that had some relevant information, but it didn't really answer my question: http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200908.mbox/%3C4FFA9271-8BF6-4CBC-AD47-263C201DBC68@gmail.com%3E. One option, as suggested in this linked thread, is to add attribution to the iTunes description. Also, we are licensing (for money) a compiled library (no source code) that we created that uses an Apache 2.0 licensed library (with some modification by us) as an independent module. *How should other companies that license our library include an attribution?* Is it sufficient for companies that license our library to attribute us in some way, and then we will attribute the Apache 2.0 licensed library on our own site? Thanks for your help! Vikas --001636832cb0ade6260474e49d87 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, this is my first time using a mailing list so apologies in advance if I= commit any mailing list faux pas - please let me know if I have.

Ou= r company is currently using Apache 2.0 licensed = code in our iPhone application which is distributed as a compiled binary - = no source code. The Apache 2.0 license states tha= t
"You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
1. You must give any other recipients of the Work or Derivative Works a copy of this License;"

For an i= Phone application, what constitutes giving the recipients a copy of the wor= k? On the iPhone and many other mobile platforms, users have no direct access to the file system. In our application we have an info screen that has an attribution link that takes users to a webpage describing our use of the Apache 2.0 licensed code. This seems to fit better with the spirit of the license since otherwise users would have no way to see the license file. Is this the right approach with our application? Or can we simply include a text file. I came across one di= scussion that had some relevant information, but it didn't really answer my question: http://mail-ar= chives.apache.org/mod_mbox/www-legal-discuss/200908.mbox/%3C4FFA9271-8BF6-4= CBC-AD47-263C201DBC68@gmail.com%3E . One option, as suggested in this l= inked thread, is to add attribution to the iTunes description.

Also, we are licensing (for money) a compiled library (no source code) = that we created that uses an Apache 2.0 licensed = library (with some modification by us) as an independent module. How sho= uld other companies that license our library include an attribution? Is= it sufficient for companies that license our library to attribute us in so= me way, and then we will attribute the Apache 2.0= licensed library on our own site?

Thanks for your help!
Vikas --001636832cb0ade6260474e49d87--