<div dir="ltr">For purposes of discussion, this is the 2.0 text submitted in 2013:<br><br>
<pre>NASA OPEN SOURCE AGREEMENT VERSION 2.0
This open source agreement (“Agreement”) defines the rights of use, reproduction, modification and redistribution of certain software released by the United States Government (“Government”) as represented by the Government Agency listed below (“Government Agency”). The United States Government, as represented by Government Agency, is an intended third-party beneficiary of all subsequent redistributions of the Subject Software. Anyone who uses, reproduces, modifies or redistributes the Subject Software, as defined herein, or any part thereof, is, by that action, accepting in full the responsibilities and obligations contained in this Agreement.
Government Agency: ______________________________________________________
Government Agency Original Software Designation: _____________________________
Government Agency Original Software Title & Ver. No. : _________________________
Government Agency Point of Contact: ________________________________________
User Registration Requested. Please Visit http://________________________________
1. DEFINITIONS
A. “Contributor” means Government Agency and any other person or entity that creates or contributes to the creation of Subject Software.
B. “Contribution” means any Work, including Your own Works and Works of other Contributors, that are Derivative Works of the Subject Software and that are intentionally submitted by You or other Contributors to Government Agency for inclusion in, or documentation of, the Subject Software.
C. “Covered Patents” means any patent claims licensable by a Contributor that are necessarily infringed by the manufacture, import, use, offer for sale, or sale of a Contributor’s Derivative Works or Contributions alone or when combined with the Subject Software.
D. “Derivative Work” means a Work that is based on (or derived from) the Subject Software and for which the revisions, annotations, or other modifications, as a whole, represent an original work of authorship. Derivative Works shall not include (i) Works that remain separate from, or merely link to, the Subject Software, or (ii) additions to the Subject Software which are separable modules of software distributed in conjunction with the Subject Software, or parts of the Subject Software, under their own license agreement. Including Subject Software or parts thereof in a Larger Work is not in and of itself a Derivative Work.
E. “Larger Work” means software that combines Subject Software, or portions thereof, with software that remains separate from, or is merely linked to, the Subject Software and that is not governed by the terms of this Agreement.
F. “Original Software” means the software first released under this Agreement by Government Agency with the Government Agency designation and title listed above, including source code, object code and accompanying documentation, if any.
G. “Subject Software” means the Original Software, Derivative Works, or Contributions, and any combination or respective parts thereof.
H. “Work” means an original work of authorship fixed in a tangible medium of expression, now known or later developed, from which it can be perceived, reproduced, or otherwise communicated, either directly or with the aid of a machine or device, including Derivative Works. A work is original if it is independently created by You, as opposed to copied from other works, and it possesses at least some minimal degree of creativity.
I. “You” or “Your” means an individual or a legal entity exercising rights under, and complying with all the terms of, this Agreement. For legal entities, “You” or “Your” includes an entity and any other entity that controls, is controlled by, or is under common control with such entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
2. GRANT OF RIGHTS YOU RECEIVE (FROM UPSTREAM CONTRIBUTORS) ALONG WITH YOUR GRANT OF RIGHTS AND OBLIGATIONS IF YOU MAKE DERIVATIVE WORKS OF OR REDISTRIBUTE THE SUBJECT SOFTWARE (TO DOWNSTREAM RECIPIENTS)
A. Subject to, and, so long as You comply with, the terms and conditions of this Agreement, the Government hereby grants permission to You to use civil servant authored U.S. Government Work (17 U.S.C. § 105) portions of the Subject Software, if any, in the United States.
B. Under Non Patent Rights/Copyright License: Subject to, and, so long as You comply with, the terms and conditions of this Agreement, each Contributor hereby grants to You (with respect to the Subject Software and its Contributions to or Derivative Works of the Subject Software) and You hereby grant to each recipient (with respect to Your Contributions to and Derivative Works of the Subject Software, as defined in Paragraphs 1.B and 1.C) a non-exclusive, worldwide, royalty-free, irrevocable (except as stated in Paragraphs 3.J and 5.A) license to use, reproduce, modify, redistribute, prepare Derivative Works of, publicly display, publicly perform, and sublicense the Subject Software.
C. Under Patent Rights: Subject to, and, so long as You comply with, the terms and conditions of this Agreement, each Contributor hereby grants to You (with respect to the Subject Software and its Contributions to or Derivative Works of the Subject Software) and You grant to each recipient (with respect to Your Contributions to and Derivative Works of the Subject Software, as defined in Paragraphs 1.B and 1.C) a non-exclusive, worldwide, royalty-free, irrevocable (except as stated in Paragraphs 3.J and 5.A) license with respect to its Covered Patents to make, have made, use, redistribute, reproduce, sell, offer to sell, import, sublicense and otherwise transfer the Subject Software.
3. ADDITIONAL OBLIGATIONS IF YOU MAKE DERIVATIVE WORKS OF OR REDISTRIBUTE THE SUBJECT SOFTWARE
A. Contributions.
1. Submission. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in Subject Software by You to the Government Agency shall be governed by the terms and conditions of this Agreement, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate agreement you may have executed with the U.S. Government regarding such Contributions.
2. Representation. You represent that each of Your Contributions is Your own Work or is the Work of another Contributor that You are authorized to submit. You represent that Your submission(s) of Contributions that are the Work of another Contributor, that You are authorized to submit, include complete details of any agreements, licenses, or other restriction (including, but not limited to, related copyright, patents and trademarks) of which You are aware that will impose additional terms and conditions on the Subject Software.
B. Redistribution. You may redistribute the Subject Software, with or without Your Derivative Works or Contributions, provided that You meet the following conditions:
1. Whenever You redistribute the Subject Software, You must include a copy of this Agreement with each copy of the Subject Software; and
2. You may redistribute Your Derivative Works or Your Contributions under this Agreement or under a license that includes additional or different terms provided it otherwise complies with the terms and conditions provided in this Agreement; and
3. If You redistribute the Subject Software in any form other than source code, You must also make the source code freely available, and must provide with each copy of the Subject Software information on how to obtain the source code in a reasonable manner on or through a medium customarily used for software exchange; and
4. If You choose to offer services under Paragraph 3.G, such services must be covered under a separate agreement.
C. You must ensure that the following copyright notice appears prominently in the Subject Software:
[GOVERNMENT AGENCY WILL INSERT THE APPLICABLE COPYRIGHT NOTICE ALONG WITH ANY OTHER REQUIRED NOTICES IN EACH AGREEMENT ACCOMPANYING THE INITIAL DISTRIBUTION OF ORIGINAL SOFTWARE AND REMOVE THIS BRACKETED LANGUAGE.]
[The following copyright notice may be used if created in whole or in part by a non-federal entity and rights obtained from author/copyright holder by assignment. Government Agency will insert the year and its Agency designation and remove the bracketed language.]
Copyright {YEAR} United States Government as represented by _______________________________. All Rights Reserved.
[The following copyright notice may be used if created by civil servants only. Government Agency will insert the year and its Agency designation and remove the bracketed language.]
Copyright {YEAR} United States Government as represented by __________________________________________. No copyright is claimed in the United States under Title 17, U.S. Code. All Other Rights Reserved.
D. You must include in any of Your Derivative Works or Contributions a notice that describes the alterations made and the date of the alterations, identifies You as Contributor of the Derivative Work or Contribution, and includes a statement that the Derivative Work or Contribution is derived, directly or indirectly, from Original Software provided by Government Agency.
E. Once a copyright notice has been added to the Subject Software, You may not remove it without the express permission of the Contributor who added the notice. You may add Your own copyright notice to the Subject Software.
F. You may not make any representation in the Subject Software or in any promotional, advertising or other material that may be construed as an endorsement by Government Agency or by any other Contributor or recipient of any product or service provided by You, or that may seek to obtain commercial advantage of Government Agency's or any other recipient’s participation in this Agreement.
G. You may choose to offer, and to charge a fee for, warranty, indemnity and/or liability obligations to one or more other recipients of the Subject Software. You may do so, however, only on Your own behalf and not on behalf of Government Agency or any other Contributor. You must make it absolutely clear that any such warranty, indemnity and/or liability obligation is offered by You alone. Further, You agree to indemnify Government Agency and every other Contributor for any liability incurred by them as a result of warranty, indemnity and/or liability offered by You.
H. You may create a Larger Work by combining Subject Software with separate software not governed by the terms and conditions of this Agreement and redistribute the Larger Work as a single product. In such case, You must make sure Subject Software, or portions thereof, included in the Larger Work is licensed under this Agreement or a license that complies with the terms and conditions provided in this Agreement.
I. Notwithstanding any provisions contained herein, You are hereby put on notice that export of any goods or technical data containing all or part of the Subject Software from the United States may require some form of export license from the U.S. Government. Government Agency makes no representation as to whether an export license is required nor that, if required, it will be issued. Nothing granted herein provides any such export license.
J. If any recipient institutes patent or copyright litigation against Government Agency or any other recipient (including a cross-claim or counterclaim in a lawsuit) alleging that the Subject Software, part of the Subject Software, or a Contribution incorporated within the Subject Software constitutes direct or indirect patent infringement or copyright infringement, then any patent and copyright licenses granted to the litigating recipient under this Agreement for the Subject Software shall terminate as of the date such litigation is filed.
K. [This paragraph may be included or deleted at the option of the Government Agency releasing the Original Software.] In an effort to track usage and maintain accurate records of the Subject Software, You, upon receipt of the Subject Software, are requested to register with Government Agency by visiting the website provided above (if any) or by e-mail to the Point of Contact listed above. Your name and personal information shall not be disclosed outside of the Government and its contractors. Once You make a Derivative Work or Contribution available, it is requested that You inform Government Agency, through the website or Point of Contact provided above, how to access the Derivative Work or Contribution.
4. DISCLAIMER OF WARRANTIES, NON-ENDORSEMENT AND LIMITATION OF LIABILITIES
A. Disclaimer of Warranty: GOVERNMENT AGENCY PROVIDES THE SUBJECT SOFTWARE (AND EACH CONTRIBUTOR PROVIDES ITS DERIVATIVE WORK OR CONTRIBUTION) “AS IS” WITHOUT ANY WARRANTY OF ANY KIND, EITHER EXPRESSED, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY THAT THE SUBJECT SOFTWARE WILL CONFORM TO SPECIFICATIONS, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR FREEDOM FROM INFRINGEMENT, ANY WARRANTY THAT THE SUBJECT SOFTWARE WILL BE ERROR FREE, OR ANY WARRANTY THAT DOCUMENTATION, IF PROVIDED, WILL CONFORM TO THE SUBJECT SOFTWARE. FURTHER, GOVERNMENT AGENCY DISCLAIMS ALL WARRANTIES AND LIABILITIES REGARDING THIRD-PARTY SOFTWARE, IF PRESENT IN THE ORIGINAL SOFTWARE, AND DISTRIBUTES IT “AS IS.”
B. Non-Endorsement: THIS AGREEMENT DOES NOT, IN ANY MANNER, CONSTITUTE AN ENDORSEMENT BY GOVERNMENT AGENCY OR ANY OTHER CONTRIBUTOR OF ANY RESULTS, RESULTING DESIGNS, HARDWARE, SOFTWARE PRODUCTS OR ANY OTHER APPLICATIONS RESULTING FROM USE OF THE SUBJECT SOFTWARE.
C. Limitation of Liability: YOU AGREE TO WAIVE ANY AND ALL CLAIMS AGAINST THE UNITED STATES GOVERNMENT, ITS CONTRACTORS AND SUBCONTRACTORS, AS WELL AS ANY OTHER CONTRIBUTOR, ARISING FROM OR RELATED TO USE OR REDISTRIBUTION OF THE SUBJECT SOFTWARE. YOU ARE SOLELY RESPONSIBLE FOR DETERMINING THE APPROPRIATENESS OF USING OR REDISTRIBUTING THE SUBJECT SOFTWARE AND ASSUME ANY RISK ASSOCIATED WITH YOUR EXERCISE OF RIGHTS GRANTED UNDER THIS AGREEMENT.
5. GENERAL TERMS
A. Termination: This Agreement and the rights granted hereunder will terminate automatically if You fail to comply with these terms and conditions and fail to cure such noncompliance within thirty (30) days of such noncompliance. Upon termination, You agree to immediately cease use and redistribution of the Subject Software. All sublicenses to the Subject Software properly granted by You shall survive any such termination of this Agreement.
B. Applicable Law: This Agreement shall be subject to United States Federal law for all purposes, including, but not limited to, determining the validity of this Agreement, the meaning of its provisions and the rights, obligations and remedies of the parties.
NOSA Ver 2 final draft clean 2013Mar26
1/6
</pre>
<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 21, 2018 at 5:08 PM, Geurts, Bryan A. (GSFC-1401) <span dir="ltr"><<a href="mailto:bryan.a.geurts@nasa.gov" target="_blank">bryan.a.geurts@nasa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
Not a problem. Can you be more specific? Any extraordinary limitations in 2.0 are necessitated by statute and/or regulation. Having said that, however, I don’t think there is anything that either is unclear or unduly favorable to NASA. Happy to discuss.
<div>Bryan<br>
<br>
<div id="m_-4039750441120484458AppleMailSignature">Sent from my iPhone</div><div><div class="h5">
<div><br>
On Feb 21, 2018, at 7:49 PM, Richard Fontana <<a href="mailto:richard.fontana@opensource.org" target="_blank">richard.fontana@opensource.<wbr>org</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">Hi Bryan,
<div><br>
</div>
<div>My general impression in the past has been that NASA has been unwilling to consider making changes to NOSA 2.0. If you are willing to submit a revised draft that:</div>
<div>* is written with a view to maximizing clarity and comprehensibility, particularly for individual software developers</div>
<div>* takes care not to give, or have the appearance of giving, special legal privileges to NASA over other licensors and licensees (or else to give a clear justification to us of why that sort of structure is necessary) then I think we can make progress,
perhaps rapid progress, towards approval. </div>
<div></div>
<div><br>
</div>
<div>Richard</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Feb 21, 2018 at 5:41 PM, Geurts, Bryan A. (GSFC-1401)
<span dir="ltr"><<a href="mailto:bryan.a.geurts@nasa.gov" target="_blank">bryan.a.geurts@nasa.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-US">
<div class="m_-4039750441120484458m_-6637652617332811418WordSection1">
<p class="MsoNormal"><span style="color:#1f497d">All,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">I am just now seeing this after having been out over the long weekend, so apologies for a slow response. We at NASA are very pleased to have someone finally express a willingness to work with us on certifying
NOSA 2.0! Apologies that I didn’t respond to Bruce’s December email, but, in looking back over my emails from that period, I couldn’t find it. Believe me, we at NASA are more than ready to engage any and all interested parties in order to come to a resolution;
whatever you need, we will provide as quickly as possible. As you know, NASA first applied for certification nearly five years ago and has been baffled by a lack of action on the part of OSI ever since. We responded to every comment from the license-review
group as well as from the OSI license-review coordinator (Richard Fontana), but nothing has come of it so far. In all honesty, we are now discussing the need to upgrade from NOSA 2.0 to NOSA 3.0, but that’s a discussion for another day, assuming we can get
approval for 2.0 in short order. Nigel Tzeng at AFL (below), Cem Karan at ARL, and others have been vocal advocates for NOSA 2.0 (many thanks to them) as some of the many persons and organizations, in particular government organizations, in need of the unique
application of an open source license tailored for government created works. From a legal perspective, government works are in a different category than other software because of a section of the US Copyright Statute (17 USC 105), which precludes the US federal
government from creating works covered by a US copyright (foreign copyrights are allowed, as are copyrights assigned or licensed to the government). Since copyright is the core legal theory under which open source software licenses operate, special accommodations
must be made if government created works are to be protectable at all. The NOSA is all about those special accommodations for government works; no other OSD compliant license addresses these issues. NOSA 1.3, approved well over a decade ago, is admittedly
a bit klunky by today’s standards, but represents a huge step forward for the times; NOSA 2.0 is several steps closer to the “mainstream” OSI-approved licenses. Both licenses were designed to be fully compliant with the OSD.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Please help me understand the next step forward. We have an open source legal team at NASA that wrote both NOSA 1.3 and 2.0, that meets regularly and is anxious to address any concerns. We are happy to engage
by email, by phone or even in person if that will move the process forward.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Bryan<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:#1f497d">Bryan A. Geurts<u></u><u></u></span></b></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1f497d">Chief Patent Counsel<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1f497d">NASA Goddard Space Flight Center<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1f497d">Code 140.1, 8800 Greenbelt Road<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1f497d">Greenbelt, MD 20771<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1f497d">Phone: <a href="tel:(301)%20286-7352" value="+13012867352" target="_blank">
301-286-7352</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1f497d">Fax: <a href="tel:(301)%20286-9502" value="+13012869502" target="_blank">
301-286-9502</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1f497d">This document, including any attachments, contains information that is confidential, protected by the attorney-client or other privileges, or constitutes non-public information. It is intended
only for the intended recipients. If you are not an intended recipient, please take appropriate steps to destroy this document in its entirety and notify the sender of its destruction. Use, dissemination, distribution or reproduction of this information
by unintended recipients is not authorized and may be unlawful.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1f497d">This communication should only be used for the particular matter discussed herein. Changes in circumstances and changes in law can greatly alter any current legal advice.<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Tzeng, Nigel H. [mailto:<a href="mailto:Nigel.Tzeng@jhuapl.edu" target="_blank">Nigel.Tzeng@jhuapl.edu</a><wbr>]
<br>
<b>Sent:</b> Tuesday, February 20, 2018 9:43 AM<br>
<b>To:</b> License submissions for OSI review <<a href="mailto:license-review@lists.opensource.org" target="_blank">license-review@lists.opensour<wbr>ce.org</a>>;
<a href="mailto:cem.f.karan.civ@mail.mil" target="_blank">cem.f.karan.civ@mail.mil</a>; Geurts, Bryan A. (GSFC-1401) <<a href="mailto:bryan.a.geurts@nasa.gov" target="_blank">bryan.a.geurts@nasa.gov</a>><br>
<b>Subject:</b> Re: [License-review] Fwd: [Non-DoD Source] Resolution on NOSA 2.0<u></u><u></u></p>
</div>
</div>
<div>
<div class="m_-4039750441120484458h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Bruce,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">There was no reply on license review because you didn’t send it to either license review or Bryan.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><a href="http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2017-December/thread.html" target="_blank">http://lists.opensource.org/pi<wbr>permail/license-review_lists.<wbr>opensource.org/2017-December/<wbr>thread.html</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">It’s been over FOUR YEARS since NOSA 2.0 was submitted in June of 2013. Maybe you should have asked these questions in 2013 rather than 2017?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">In any case, according to the archive of the license-review lists from November 2017 to February 2018, NASA was ignored. If the board has formally rejected the NOSA 2.0 submission in the meantime that’s just awesome communication on the
lists.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">By blocking the approval of NOSA 2.0 the OSI has blocked the fix for the section that you have an issue with in v1.3 (original work of authorship clause). If you were interested in seeing that language removed then you should have advocated
for approval of NOSA 2.0.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">As I noted in License-Discuss, if one the agencies that has been forward thinking and generating GOSS code for public use as part of their strategy for nearly two decades under the NOSA license (<a href="https://open.nasa.gov" target="_blank">https://open.nasa.gov</a>
and <a href="https://code.nasa.gov" target="_blank">https://code.nasa.gov</a> ) and likely has released one of the oldest GOSS/PD codebases around (<a href="https://github.com/chrislgarry/Apollo-11)" target="_blank">https://github.com/chrislgarr<wbr>y/Apollo-11)</a> believes
it needs to update that license then the OSI shouldn’t continue to be a roadblock for improving that
<b>already approved special purpose license </b>but instead be helpful and <b>responsive</b>.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">According to Open Nasa they have:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal">39,054 Open Data Sets<u></u><u></u></li><li class="MsoNormal">356 Open Code Repositories (155 on GitHub under the NASA account)<u></u><u></u></li><li class="MsoNormal">41 Open APIs<u></u><u></u></li></ul>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I think NASA has met and exceeded any “higher standard” set for Open Source and Open Data advocacy and performance.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Regards,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Nigel<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">On 2/16/18, 4:38 PM, "License-review on behalf of Bruce Perens" <<a href="mailto:license-review-bounces@lists.opensource.org" target="_blank">license-review-bounces@lists.<wbr>opensource.org</a> on behalf of
<a href="mailto:bruce@perens.com" target="_blank">bruce@perens.com</a>> wrote:<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
I did not get any reply from NASA when I first sent this, in early December.<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
Thanks<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"> Bruce<u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">---------- Forwarded message ---------<br>
From: Bruce Perens <<a href="mailto:bruce@perens.com" target="_blank">bruce@perens.com</a>><br>
Date: Fri, Dec 8, 2017, 21:39<br>
Subject: Re: [License-review] [Non-DoD Source] Resolution on NOSA 2.0<br>
To: License submissions for OSI review <<a href="mailto:license-review@opensource.org" target="_blank">license-review@opensource.org</a><wbr>>, <<a href="mailto:cem.f.karan.civ@mail.mil" target="_blank">cem.f.karan.civ@mail.mil</a>>, <<a href="mailto:bryan.a.geurts@nasa.gov" target="_blank">bryan.a.geurts@nasa.gov</a>><u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<u></u> <u></u></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">> Could you (meaning you and the board) please give us a breakdown of what the issues were?
<u></u><u></u></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">and<u></u><u></u></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<br>
> <span style="color:#1f497d">If we resubmit, will we be engaged or simply ignored, as before?</span><u></u><u></u></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1f497d">I didn't see any public response to these questions. I am not a member of the OSI board, but I am the creator of the Open Source Definition. As a member of the license review committee
(admission being equivalent to being granted a subscription to this mailing list) I would be willing to look at a new submission and make a recommendation.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1f497d">I think the missing piece in your previous submissions is that they were not a good deal for the Open Source developer community, only a license engineered to grant maximal protection
to NASA. The board cited legal ambiguities in their response, these are of course to the disadvantage of the community. Individual developers do not have the easy access to counsel and the legal budget that NASA has, and it's an even worse day for
<i>them </i>when they are sued. To give a personal example, my recent participation in an Open-source-related lawsuit will probably exceed my year's income in legal fees. So, I believe that both NASA and OSI should place the individual developer's protection
before that of NASA if we are all to pursue Open Source fairly.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1f497d">In addition, the language in 1.3 that prevents combination of Open Source that is not an original work of authorship of the contributor seems to me to be inimical to the concept of Open
Source. I would not have recommended its approval. I would be especially interested in seeing a submission that removed that language.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1f497d"> Thanks</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1f497d"> Bruce</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
License-review mailing list<br>
<a href="mailto:License-review@lists.opensource.org" target="_blank">License-review@lists.opensourc<wbr>e.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/ma<wbr>ilman/listinfo/license-review_<wbr>lists.opensource.org</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div></div></div>
</div>
<br>______________________________<wbr>_________________<br>
License-review mailing list<br>
<a href="mailto:License-review@lists.opensource.org">License-review@lists.<wbr>opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/<wbr>mailman/listinfo/license-<wbr>review_lists.opensource.org</a><br>
<br></blockquote></div><br></div>