In the software license BSD, what is &quot; Redistribution in binary form must reproduce the above copyright notice...&quot;
<p>I'm trying to understand all the responsibilities of this license.</p>
<p>Does redistribution mean:</p>
<ul>
<li><p>publicly placing a windows .exe using the BSD licensed library for users to download on a website(free and commercial)</p>
</li>
<li><p>sharing the exe with friends (free and commercial)</p>
</li>
</ul>
<p>Can redistribution even mean just packaging your project into a exe because you are like rearranging the files into one executable??</p>
<p>Are we required to include the license in readable form in an exe in the project application itself or just in the project folder like a readme?</p>
<p>What if people forget to include the notices for some libraries? Do they have to pay fines or something?</p>

<p>Disclaimer: I'm not a lawyer.  This advice may be materially inaccurate.</p>
<p><strong>What does redistribution mean?</strong></p>
<p>Redistribution means you have somehow caused the software to make its way to another person.  Things that probably count as distribution:</p>
<ul>
<li>Placing the file on a public website.</li>
<li>Printing the binary in hex onto paper and giving that paper to someone else.</li>
<li>Putting the file onto a USB drive and handing it to someone.</li>
<li>Putting the file onto your own computer, then giving that computer to someone else.</li>
<li>Putting the file onto a shared network drive.</li>
</ul>
<p>Things that probably don't count as distribution:</p>
<ul>
<li>Copying the files onto your own computer(s)</li>
<li>Compiling the program</li>
<li>Placing the program on your phone.</li>
<li>Printing out the source code on paper, but not sharing it.</li>
</ul>
<p>As a practical matter, I recommend ensuring that BSD license accompanies any instances of the software, even if you don't intend to distribute those instances.  If you don't distribute it, then nobody will see it.  If you &quot;inadvertently&quot; distribute the software, then including the license means you are in compliance.</p>
<p><strong>Should you include the license in the exe or in the same folder:</strong></p>
<p>The specific clause is:</p>
<blockquote>
<p>Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.</p>
</blockquote>
<ul>
<li><p>Including the license in the exe (e.g., via some sort of credits menu) is typically fine.  I'll note that this is the approach used by Chrome (help-&gt;about chrome has a link to &quot;other open source software&quot; which includes these licenses).  This approach works well for software which makes use of an installer, since users probably won't be looking in the install folder.</p>
</li>
<li><p>Including the license in the folder adjacent to the exe is also typically fine.  If your application does not have an install process (e.g., installed via xcopy deployment), then this approach works well, since users will easily be able to find the license.</p>
</li>
<li><p>If your software is sold in a physical box, then printing out the license and including that license inside the box also works.</p>
</li>
</ul>
<p><strong>What if I violate the license by not including the BSD terms?</strong></p>
<p>If you violate the license, you are subject to a lawsuit for copyright violation. What happens next depends on how the copyright owners wishes to proceed:</p>
<ul>
<li><p>Some copyright owners will sue. The actual results/penalties for such a violation will depend on a variety of factors.</p>
</li>
<li><p>Some copyright owners will ask you to comply with the license.  If you respond by apologizing and then complying, that's as far as it will go.</p>
</li>
<li><p>Some copyright owners will ask you for money (with threat of lawsuit).  I would expect this result if the copyright owners offers a dual-licensing scheme (i.e., where you can pay the copyright owner to exclude the acknowledgement).</p>
</li>
</ul>

copyright software licensing