Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Received-SPF: pass (athena.apache.org: domain of kevan.miller@gmail.com
 designates 209.85.220.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <39C7D2B9-7989-43CF-8785-1DCF15FE222E@classsoftware.com>
References: <CFCAE652.24C84%aharui@adobe.com>
	<CAM1oqKq5m4f6PAs+X2JZiV8FBqPYExvqUJn47NDNdKPqT91ATQ@mail.gmail.com>
	<49D423B3-1FCE-49B5-80FE-217746D3B739@classsoftware.com>
	<CAOGo0VZxq4rbkRrhpNU5xCFDmFseC_pBzWa0kia+Ff2mtSUhJQ@mail.gmail.com>
	<39C7D2B9-7989-43CF-8785-1DCF15FE222E@classsoftware.com>
Date: Mon, 23 Jun 2014 22:14:17 -0700
Message-ID: 
 <CAM1oqKpm7TnNKRDc2=dDpYFcH4mFF2bFJ1f5WJ6GZwTsQmZA3Q@mail.gmail.com>
Subject: Re: Bundling an AL Font
From: Kevan Miller <kevan.miller@gmail.com>
To: "legal-discuss@apache.org" <legal-discuss@apache.org>
Content-Type: multipart/alternative; boundary=089e013d05020ebf9604fc8e080d

--089e013d05020ebf9604fc8e080d
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jun 23, 2014 at 4:58 PM, Justin Mclean <justin@classsoftware.com>
wrote:

> > Not necessarily. An ASF project NOTICE can include additionall
> attributions.
>
> For simplicity sake I was assuming that no NOTICE file exist the 3rd party
> code.
>

In that case you don't need to do anything.

If there was a NOTICE file, you must include all non-ASF attributions that
apply to your usage (there's no need to copy the ASF attributions).

Without a NOTICE file, in the distributed binary or original source(I try
to check if .jar files don't include a NOTICE. Some projects aren't good
about building jars with LICENSE/NOTICE files), you don't need to do
anything. I downloaded the Open-Sans source, and don't see a NOTICE file
there. You should verify this...


>
> > Once you have established the LICENSE (and NOTICE if any) that apply
> > to the 3rd party code, the normal process applies.
>
> So where does the copyright attribution go?
>

In the absence of a NOTICE file? Nowhere, IMO. If the producers of
Open-Sans wanted a copyright attribution, they would have (should have)
created a NOTICE file. You can always verify with the producers to see if
they made a mistake.


> To put in context the current situation with the fonts is that we have
> binary files (the font files) in a release that there no clear indication
> what the license is or where they come from). You can assume that they are
> Apache licensed (as no other license is indicated) but anyone reviewing the
> release may want to know more information, like where they come from and
> the original copyright owner may want attribution and/or it may be legally
> required.


To handle this, I would put something like the following in the LICENSE
file:

The <path-to-open-sans-font-file-in-your-source-distribution> is licensed
under Apache License, Version 2.0.

You can find similar examples from other LICENSE files. For example --
http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE

--kevan

--089e013d05020ebf9604fc8e080d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Jun 23, 2014 at 4:58 PM, Justin Mclean <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:justin@classsoftware.com" target=3D"_blank">justin@classsoftwar=
e.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div>&gt; Not necessarily. An ASF project NOTICE can inclu=
de additionall attributions.<br>

<br>
</div>For simplicity sake I was assuming that no NOTICE file exist the 3rd =
party code.<br></blockquote><div><br></div><div>In that case you don&#39;t =
need to do anything.</div><div><br></div><div>If there was a NOTICE file, y=
ou must include all non-ASF attributions that apply to your usage (there=
9;s no need to copy the ASF attributions).</div>

<div><br></div><div>Without a NOTICE file, in the distributed binary or ori=
ginal source(I try to check if .jar files don&#39;t include a NOTICE. Some =
projects aren&#39;t good about building jars with LICENSE/NOTICE files), yo=
u don&#39;t need to do anything. I downloaded the Open-Sans source, and don=
&#39;t see a NOTICE file there. You should verify this...</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">

<div><br>
&gt; Once you have established the LICENSE (and NOTICE if any) that apply<b=
r>
&gt; to the 3rd party code, the normal process applies.<br>
<br>
</div>So where does the copyright attribution go?<br></blockquote><div><br>=
</div><div>In the absence of a NOTICE file? Nowhere, IMO. If the producers =
of Open-Sans wanted a copyright attribution, they would have (should have) =
created a NOTICE file. You can always verify with the producers to see if t=
hey made a mistake.</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">
<br>
To put in context the current situation with the fonts is that we have bina=
ry files (the font files) in a release that there no clear indication what =
the license is or where they come from). You can assume that they are Apach=
e licensed (as no other license is indicated) but anyone reviewing the rele=
ase may want to know more information, like where they come from and the or=
iginal copyright owner may want attribution and/or it may be legally requir=
ed.</blockquote>

</div><div class=3D"gmail_extra"><br></div>To handle this, I would put some=
thing like the following in the LICENSE file:</div><div class=3D"gmail_extr=
a"><br></div><div class=3D"gmail_extra">The &lt;path-to-open-sans-font-file=
-in-your-source-distribution&gt; is licensed under Apache License, Version =
2.0.=A0</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">You can fin=
d similar examples from other LICENSE files. For example --=A0<a href=3D"ht=
tp://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE">http://svn.apache.=
org/repos/asf/httpd/httpd/trunk/LICENSE</a></div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">--kevan</di=
v><div class=3D"gmail_extra"><br></div></div>

--089e013d05020ebf9604fc8e080d--