<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>All,<br>
<br>
At its Board meeting on September 20, 2024, the Board adopted the
recommendation of the License Review Committee and <i>approved </i>the
Los Alamos National Labs BSD-3 Variant License as an Open Source
Initiative Certified License.<br>
<br>
Pamela Chestek<br>
Chair, License Committee<br>
Open Source Initiative <br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 9/13/2024 10:03 PM, Pamela Chestek
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:938d76be-9a8b-4bd9-ade6-b1cf1494d310@opensource.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>All,<br>
<br>
Below is the recommendation of the License Committee that the
Los Alamos National Labs BSD-3 Variant License be approved as an
Open Source Initiative Certified license. The Board will vote on
the license at the next Board meeting, scheduled for September
20.<br>
<br>
Please respond to this email if you have any comments or
questions.<br>
<br>
Pamela Chestek<br>
Chair, License Committee<br>
Open Source Initiative</p>
<p><br>
</p>
<p>==========</p>
<p><br>
</p>
<p>License: Los Alamos National Labs BSD-3 Variant License
(Exhibit A)<br>
Submitted: June 26, 2024,
<a class="moz-txt-link-freetext"
href="https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2024-June/005490.html"
moz-do-not-send="true">https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2024-June/005490.html</a><br>
Decision date: due no later than the first Board meeting after
August 26, 2024<br>
<br>
License Review Committee Recommendation: <br>
<br>
<i>Resolved that it is the opinion of the OSI that the Los
Alamos National Labs BSD-3 Variant License be approved as an
Open Source Initiative Certified license in the Non-Reusable
category of licenses.<br>
</i><br>
<u>Rationale Document</u><br>
<br>
Notes: This is a legacy license, already in use for a number of
projects created under the auspices of the Los Alamos National
Lab. It is a standard BSD-3 license with an additional
disclaimer that imposes only a restriction that changes to the
software must be marked, which is commonly found in open source
licenses. There was only one substantive comment on the license,
which was that it should be approved.<br>
<br>
<u>Exhibit A</u><br>
<br>
Copyright (c) XXXX, Los Alamos National Security, LLC<br>
All rights reserved.<br>
Copyright XXXX. Los Alamos National Security, LLC. This software
was produced under U.S. Government contract DE-AC52-06NA25396
for Los Alamos National Laboratory (LANL), which is operated by
Los Alamos National Security, LLC for the U.S. Department of
Energy. The U.S. Government has rights to use, reproduce, and
distribute this software. NEITHER THE GOVERNMENT NOR LOS ALAMOS
NATIONAL SECURITY, LLC MAKES ANY WARRANTY, EXPRESS OR IMPLIED,
OR ASSUMES ANY LIABILITY FOR THE USE OF THIS SOFTWARE. If
software is modified to produce derivative works, such modified
software should be clearly marked, so as not to confuse it with
the version available from LANL.<br>
<br>
Additionally, redistribution and use in source and binary forms,
with or without modification, are permitted provided that the
following conditions are met:<br>
1. Redistributions of source code must retain the above
copyright notice, this list of conditions and the following
disclaimer.<br>
2. 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.<br>
3. Neither the name of Los Alamos National Security, LLC, Los
Alamos National Laboratory, LANL, the U.S. Government, nor the
names of its contributors may be used to endorse or promote
products derived from this software without specific prior
written permission.<br>
<br>
THIS SOFTWARE IS PROVIDED BY LOS ALAMOS NATIONAL SECURITY, LLC
AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL LOS ALAMOS NATIONAL SECURITY, LLC
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.<br>
<br>
<br>
</p>
<div class="moz-cite-prefix">On 6/26/2024 8:50 AM, Pettinger, Adam
L via License-review wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DM6PR11MB3146A9D8FF5C9CDF8391166CE8D62@DM6PR11MB3146.namprd11.prod.outlook.com">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8">
<style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hello,</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We are trying to get a package (<a
href="https://github.com/UTNuclearRoboticsPublic/netft_utils" id="LPlnk"
class="OWAAutoLink moz-txt-link-freetext"
title="https://github.com/UTNuclearRoboticsPublic/netft_utils"
moz-do-not-send="true">https://github.com/UTNuclearRoboticsPublic/netft_utils</a>)
distributed, and there is a small ambiguity in the licensing
situation, see here (<a
href="https://github.com/ros/rosdistro/pull/41583"
id="LPlnk" class="OWAAutoLink moz-txt-link-freetext"
title="https://github.com/ros/rosdistro/pull/41583"
moz-do-not-send="true">https://github.com/ros/rosdistro/pull/41583</a>)
for discussion.</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We determined that the best way forward is to get the license
for the project approved by the OSI. See the attached file for
the license text, but it is basically a Los Alamos National
Lab (LANL) flavored BSD-3, and would be similar to (<a
href="https://opensource.org/license/bsd-3-clause-lbnl"
id="LPlnk" class="OWAAutoLink moz-txt-link-freetext"
title="https://opensource.org/license/bsd-3-clause-lbnl"
moz-do-not-send="true">https://opensource.org/license/bsd-3-clause-lbnl</a>).</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I believe the legacy license path makes the most sense for
this, although that depends on how "unrelated" the entities
must be. Here is a list of projects using the license (<a
href="https://www.lanl.gov/software/open-source-software.php" id="LPlnk"
class="OWAAutoLink moz-txt-link-freetext"
title="https://www.lanl.gov/software/open-source-software.php"
moz-do-not-send="true">https://www.lanl.gov/software/open-source-software.php</a>),
and they are only related in that</div>
<ol data-listchain="__List_Chain_31" start="1">
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The authors have some affiliation with LANL and</div>
</li>
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The Feynman Center at LANL has approved them for open
source release.</div>
</li>
</ol>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The reason I think legacy makes sense is that the license is
already used many places, and the ability to change the
wording in it at this point is questionable.</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I will follow the legacy submission going forward, but please
let me know if you think I should update and switch to the new
license requirements. Per the guidelines on the website:</div>
<ul>
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The license text is attached</div>
</li>
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
It complies with the Open Source Definition, including
clauses 3, 5, 6, and 9</div>
</li>
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Here is a list of projects using the license: (<a
href="https://www.lanl.gov/software/open-source-software.php" id="LPlnk"
class="OWAAutoLink moz-txt-link-freetext"
title="https://www.lanl.gov/software/open-source-software.php"
moz-do-not-send="true">https://www.lanl.gov/software/open-source-software.php</a>)</div>
</li>
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The lisence steward would be the Intellectual Property
Team at the Richard P. Feynman Center for Innovation at
LANL. Phone: (505) 665-9090. Email: <a
class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:software@lanl.gov" moz-do-not-send="true">software@lanl.gov</a></div>
</li>
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Unknown other approvals or information</div>
</li>
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Following (<a
href="https://opensource.org/license/bsd-3-clause-lbnl"
id="LPlnk"
title="https://opensource.org/license/bsd-3-clause-lbnl"
moz-do-not-send="true" class="moz-txt-link-freetext">https://opensource.org/license/bsd-3-clause-lbnl</a>),
I propose the name: Los Alamos National Lab BSD Variant
License and identifier BSD-3-Clause-LANL</div>
</li>
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
No other existing IDs</div>
</li>
</ul>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
If it must be considered a new license, additional information
would be:</div>
<ul>
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Gap to be filled: ability to release projects approved by
LANL and using their license</div>
</li>
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The most similiar (<a
href="https://opensource.org/license/bsd-3-clause-lbnl"
id="LPlnk"
title="https://opensource.org/license/bsd-3-clause-lbnl"
moz-do-not-send="true" class="moz-txt-link-freetext">https://opensource.org/license/bsd-3-clause-lbnl</a>),
and really is quite close. Mostly just substituting LBNL
naming with LANL naming</div>
</li>
<li
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Not sure what review the license has been through</div>
</li>
</ul>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Please let me know if you have any questions, thanks!</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<p><span
style="font-family: "Open Sans", sans-serif;"><b>Adam
Pettinger</b></span></p>
<p><span
style="font-family: "Open Sans", sans-serif;">Senior
Research Engineer</span></p>
<p style="background-color: white;"><span
style="font-family: "Open Sans", sans-serif; font-size: 10pt; color: rgb(10, 10, 10); background-color: rgb(254, 254, 254);"><a
href="mailto:adam.pettinger@tamu.edu"
id="OWAa155aa77-57cb-8faa-81de-4ede5a82108d"
class="OWAAutoLink moz-txt-link-freetext"
style="margin-top: 0px; margin-bottom: 0px;"
moz-do-not-send="true">adam.pettinger@tamu.edu</a></span></p>
<p><span
style="font-family: "Open Sans", sans-serif; color: rgb(80, 0, 0); background-color: white;"><b>TEXAS
A&M ROBOTICS AND AUTOMATION DESIGN LAB</b></span></p>
<p><a href="https://rad.engr.tamu.edu/"
id="OWA36f4aab8-a5ba-e68b-082c-bcd3d53c8bb4"
class="OWAAutoLink moz-txt-link-freetext"
style="margin-top: 0px; margin-bottom: 0px;"
moz-do-not-send="true">https://rad.engr.tamu.edu/</a></p>
<p> </p>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Communication from the Open Source Initiative will be sent from an opensource.org email address.
License-review mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:License-review@lists.opensource.org"
moz-do-not-send="true">License-review@lists.opensource.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org"
moz-do-not-send="true">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</pre>
</blockquote>
<div class="moz-signature"><br>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Communication from the Open Source Initiative will be sent from an opensource.org email address.
License-review mailing list
<a class="moz-txt-link-abbreviated" href="mailto:License-review@lists.opensource.org">License-review@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</pre>
</blockquote>
<div class="moz-signature">-- <br>
Pamela S. Chestek
Chair, License Committee
Open Source Initiative</div>
</body>
</html>