[License-discuss] [Non-DoD Source] Re: US Army Research Laboratory Open Source License proposal
Karan, Cem F CIV USARMY RDECOM ARL (US)
cem.f.karan.civ at mail.mil
Mon Jul 25 13:14:19 UTC 2016
> -----Original Message-----
> From: License-discuss [mailto:license-discuss-bounces at opensource.org] On Behalf Of Lawrence Rosen
> Sent: Friday, July 22, 2016 5:23 PM
> To: license-discuss at opensource.org
> Cc: Lawrence Rosen <lrosen at rosenlaw.com>
> Subject: [Non-DoD Source] Re: [License-discuss] US Army Research Laboratory Open Source License proposal
>
> Cem Karan wrote:
>
> > Most of our researchers work for the US Federal Government and under US copyright law any works they produce during the course of
> their duties do not have copyright attached, so we have to rely on contract law as a protection mechanism within the USA.
>
> I don't understand your worry. Not only can't you assert copyright in the U.S., you can't prevent anyone in the U.S. from copying or
> modifying those works even without any license needed from you. You can't even rely on contract law in the U.S. to protect against those
> uses here. I have personally, on occasion, considered filing a Freedom of Information Act request for useful government code to see if that
> works to pry free software from government hands. I never did that. The U.S. government has almost always proven to be very generous
> without demands.
We're fine with distributions and modifications; we wouldn't be putting it out as Open Source if we weren't. However, as I said in my earlier email, we still need to deal with liability, misrepresentation, and various forms of IP trolling.
As for FOIA requests, that is one way of getting the code, but it doesn't make for a very good Open Source experience for anyone. We want an internal process that lets our researchers participate in Open Source properly, and that requires a license that works for the USG.
>
> It is true that this public domain result doesn't apply outside the U.S. But if you apply a valid open source license to it – such as Apache 2.0
> – that should be good enough for everyone who doesn't live in the U.S. and irrelevant for us here.
We'd rather avoid the issues that come with dual licensing; it is its own maintenance headache. A single license is easy to apply, and easy to understand for everyone. In addition, if we ever do have to deal with litigation, everyone knows which license applies, rather than spend time arguing over the license that should be used.
> /Larry
>
>
>
> -----Original Message-----
> From: Karan, Cem F CIV USARMY RDECOM ARL (US) [Caution-mailto:cem.f.karan.civ at mail.mil]
> Sent: Friday, July 22, 2016 2:01 PM
> To: license-discuss at opensource.org
> Subject: [License-discuss] US Army Research Laboratory Open Source License proposal
>
>
>
> Hi, my name is Cem Karan. I work for the US Army Research Laboratory (ARL) in Adelphi, MD. I'm in charge of defining the Open Source
> policy for ARL. As a part of this, we need a license that meets our legal and regulatory needs, but is ideally fully interchangeable with
> everything licensed under the Apache 2 license as defined at Caution-http://www.apache.org/licenses/LICENSE-2.0.txt < Caution-
> http://www.apache.org/licenses/LICENSE-2.0.txt > . We also want our license to be fully accepted by OSI as a valid Open Source license.
>
>
>
> Unfortunately, we cannot directly use the Apache 2 license for all of our code. Most of our researchers work for the US Federal
> Government and under US copyright law any works they produce during the course of their duties do not have copyright attached, so we
> have to rely on contract law as a protection mechanism within the USA. We considered using NOSA 1.3 (Caution-
> https://opensource.org/licenses/NASA-1.3 < Caution-https://opensource.org/licenses/NASA-1.3 > ), but apparently that it isn't
> interoperable with other licenses. As I understand it, some work on the NOSA
>
> 2.0 license was done to improve interoperability, but that work is currently stalled.
>
>
>
> For that reason, we've tried to modify the Apache 2.0 license to fit our needs. The license in full is below and can be diffed with license
> text found at Caution-http://www.apache.org/licenses/LICENSE-2.0.txt < Caution-http://www.apache.org/licenses/LICENSE-2.0.txt > with
> relative ease; the text has also been attached to this email in case my mail client scrambles the formatting. The summary of changes are
> as follows:
>
>
>
> 1) Changed the name and version number.
>
>
>
> 2) Changed the definition of 'Licensor' to use 'project originator' instead of 'copyright owner'.
>
>
>
> 3) Changed the definition of 'Work' to not use the word 'copyright'.
>
>
>
> 4) Changed the definition of 'Contributor' to use 'author' instead of 'copyright owner'.
>
>
>
> 5) Removed the word 'copyright' from the Appendix's instructions
>
>
>
> 6) In the notice, removed the word 'Copyright'
>
>
>
> 7) In the notice, changed 'copyright owner' to Licensor.
>
>
>
> 8) Scrambled the URL as we don't have one yet.
>
>
>
> In general, we want our license to provide the following:
>
>
>
> - Protection against liability, not only for ourselves, but also for anyone that contributes to our projects.
>
>
>
> - Protection against fraud where derivative work is represented as being the original.
>
>
>
> - Protection against malicious contributors that intend to entangle projects with IP headaches (patent trolls and the like). This must
> protect not only protect the US Government, but also anyone that downloads our code (just like the Apache 2 license does).
>
>
>
> - The ability to deal with contributions where copyright may or may not be attached. If there is copyright attached, the License should
> treat it as similarly as possible to the Apache 2.0 license. If there is no copyright attached, then the contribution is in the public domain,
> but it may have patent or other IP rights that also need to be dealt with.
>
>
>
> Finally, there is opinion within the US Government that while there is no US copyright protection, copyright attaches outside of the US.
> Thus, if a project is downloaded and used outside of the USA, then any work produced by a US Government employee will have foreign
> copyright protection, and the terms of the License should apply to that copyright as well.
>
>
>
> Comments on this proposed license are much appreciated.
>
>
>
> Thank you,
>
> Cem Karan
>
>
>
> """
>
>
>
> U.S. Army Research Laboratory Open Source License (ARL OSL)
>
> Version 0.2, July 2016
>
> Caution-http://no/URL/as/yet < Caution-http://no/URL/as/yet >
>
>
>
> TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
>
>
>
> 1. Definitions.
>
>
>
> "License" shall mean the terms and conditions for use, reproduction,
>
> and distribution as defined by Sections 1 through 9 of this document.
>
>
>
> "Licensor" shall mean the project originator or entity authorized by
>
> the project originator that is granting the License.
>
>
>
> "Legal Entity" shall mean the union of the acting entity and all
>
> other entities that control, are controlled by, or are under common
>
> control with that 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.
>
>
>
> "You" (or "Your") shall mean an individual or Legal Entity
>
> exercising permissions granted by this License.
>
>
>
> "Source" form shall mean the preferred form for making modifications,
>
> including but not limited to software source code, documentation
>
> source, and configuration files.
>
>
>
> "Object" form shall mean any form resulting from mechanical
>
> transformation or translation of a Source form, including but
>
> not limited to compiled object code, generated documentation,
>
> and conversions to other media types.
>
>
>
> "Work" shall mean the work of authorship, whether in Source or
>
> Object form, made available under the License, as indicated by a
>
> notice that is included in or attached to the work
>
> (an example is provided in the Appendix below).
>
>
>
> "Derivative Works" shall mean any work, whether in Source or Object
>
> form, that is based on (or derived from) the Work and for which the
>
> editorial revisions, annotations, elaborations, or other modifications
>
> represent, as a whole, an original work of authorship. For the purposes
>
> of this License, Derivative Works shall not include works that remain
>
> separable from, or merely link (or bind by name) to the interfaces of,
>
> the Work and Derivative Works thereof.
>
>
>
> "Contribution" shall mean any work of authorship, including
>
> the original version of the Work and any modifications or additions
>
> to that Work or Derivative Works thereof, that is intentionally
>
> submitted to Licensor for inclusion in the Work by the author
>
> or by an individual or Legal Entity authorized to submit on behalf of
>
> the author. For the purposes of this definition, "submitted"
>
> means any form of electronic, verbal, or written communication sent
>
> to the Licensor or its representatives, including but not limited to
>
> communication on electronic mailing lists, source code control systems,
>
> and issue tracking systems that are managed by, or on behalf of, the
>
> Licensor for the purpose of discussing and improving the Work, but
>
> excluding communication that is conspicuously marked or otherwise
>
> designated in writing by the author as "Not a Contribution."
>
>
>
> "Contributor" shall mean Licensor and any individual or Legal Entity
>
> on behalf of whom a Contribution has been received by Licensor and
>
> subsequently incorporated within the Work.
>
>
>
> 2. Grant of Copyright License. Subject to the terms and conditions of
>
> this License, each Contributor hereby grants to You a perpetual,
>
> worldwide, non-exclusive, no-charge, royalty-free, irrevocable
>
> copyright license to reproduce, prepare Derivative Works of,
>
> publicly display, publicly perform, sublicense, and distribute the
>
> Work and such Derivative Works in Source or Object form.
>
>
>
> 3. Grant of Patent License. Subject to the terms and conditions of
>
> this License, each Contributor hereby grants to You a perpetual,
>
> worldwide, non-exclusive, no-charge, royalty-free, irrevocable
>
> (except as stated in this section) patent license to make, have made,
>
> use, offer to sell, sell, import, and otherwise transfer the Work,
>
> where such license applies only to those patent claims licensable
>
> by such Contributor that are necessarily infringed by their
>
> Contribution(s) alone or by combination of their Contribution(s)
>
> with the Work to which such Contribution(s) was submitted. If You
>
> institute patent litigation against any entity (including a
>
> cross-claim or counterclaim in a lawsuit) alleging that the Work
>
> or a Contribution incorporated within the Work constitutes direct
>
> or contributory patent infringement, then any patent licenses
>
> granted to You under this License for that Work shall terminate
>
> as of the date such litigation is filed.
>
>
>
> 4. Redistribution. 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:
>
>
>
> (a) You must give any other recipients of the Work or
>
> Derivative Works a copy of this License; and
>
>
>
> (b) You must cause any modified files to carry prominent notices
>
> stating that You changed the files; and
>
>
>
> (c) You must retain, in the Source form of any Derivative Works
>
> that You distribute, all copyright, patent, trademark, and
>
> attribution notices from the Source form of the Work,
>
> excluding those notices that do not pertain to any part of
>
> the Derivative Works; and
>
>
>
> (d) If the Work includes a "NOTICE" text file as part of its
>
> distribution, then any Derivative Works that You distribute must
>
> include a readable copy of the attribution notices contained
>
> within such NOTICE file, excluding those notices that do not
>
> pertain to any part of the Derivative Works, in at least one
>
> of the following places: within a NOTICE text file distributed
>
> as part of the Derivative Works; within the Source form or
>
> documentation, if provided along with the Derivative Works; or,
>
> within a display generated by the Derivative Works, if and
>
> wherever such third-party notices normally appear. The contents
>
> of the NOTICE file are for informational purposes only and
>
> do not modify the License. You may add Your own attribution
>
> notices within Derivative Works that You distribute, alongside
>
> or as an addendum to the NOTICE text from the Work, provided
>
> that such additional attribution notices cannot be construed
>
> as modifying the License.
>
>
>
> You may add Your own copyright statement to Your modifications and
>
> may provide additional or different license terms and conditions
>
> for use, reproduction, or distribution of Your modifications, or
>
> for any such Derivative Works as a whole, provided Your use,
>
> reproduction, and distribution of the Work otherwise complies with
>
> the conditions stated in this License.
>
>
>
> 5. Submission of Contributions. Unless You explicitly state otherwise,
>
> any Contribution intentionally submitted for inclusion in the Work
>
> by You to the Licensor shall be under the terms and conditions of
>
> this License, without any additional terms or conditions.
>
> Notwithstanding the above, nothing herein shall supersede or modify
>
> the terms of any separate license agreement you may have executed
>
> with Licensor regarding such Contributions.
>
>
>
> 6. Trademarks. This License does not grant permission to use the trade
>
> names, trademarks, service marks, or product names of the Licensor,
>
> except as required for reasonable and customary use in describing the
>
> origin of the Work and reproducing the content of the NOTICE file.
>
>
>
> 7. Disclaimer of Warranty. Unless required by applicable law or
>
> agreed to in writing, Licensor provides the Work (and each
>
> Contributor provides its Contributions) on an "AS IS" BASIS,
>
> WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>
> implied, including, without limitation, any warranties or conditions
>
> of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
>
> PARTICULAR PURPOSE. You are solely responsible for determining the
>
> appropriateness of using or redistributing the Work and assume any
>
> risks associated with Your exercise of permissions under this License.
>
>
>
> 8. Limitation of Liability. In no event and under no legal theory,
>
> whether in tort (including negligence), contract, or otherwise,
>
> unless required by applicable law (such as deliberate and grossly
>
> negligent acts) or agreed to in writing, shall any Contributor be
>
> liable to You for damages, including any direct, indirect, special,
>
> incidental, or consequential damages of any character arising as a
>
> result of this License or out of the use or inability to use the
>
> Work (including but not limited to damages for loss of goodwill,
>
> work stoppage, computer failure or malfunction, or any and all
>
> other commercial damages or losses), even if such Contributor
>
> has been advised of the possibility of such damages.
>
>
>
> 9. Accepting Warranty or Additional Liability. While redistributing
>
> the Work or Derivative Works thereof, You may choose to offer,
>
> and charge a fee for, acceptance of support, warranty, indemnity,
>
> or other liability obligations and/or rights consistent with this
>
> License. However, in accepting such obligations, You may act only
>
> on Your own behalf and on Your sole responsibility, not on behalf
>
> of any other Contributor, and only if You agree to indemnify,
>
> defend, and hold each Contributor harmless for any liability
>
> incurred by, or claims asserted against, such Contributor by reason
>
> of your accepting any such warranty or additional liability.
>
>
>
> END OF TERMS AND CONDITIONS
>
>
>
> APPENDIX: How to apply the U.S. Army Research Laboratory Open Source License (ARL OSL) to your work.
>
>
>
> To apply the ARL OSL to your work, attach the following
>
> boilerplate notice, with the fields enclosed by brackets "[]"
>
> replaced with your own identifying information. (Don't include
>
> the brackets!) The text should be enclosed in the appropriate
>
> comment syntax for the file format. We also recommend that a
>
> file or class name and description of purpose be included on the
>
> same "printed page" as the notice for easier
>
> identification within third-party archives.
>
>
>
> [yyyy] [name of Licensor]
>
>
>
> Licensed under the Apache License, Version 2.0 (the "License");
>
> you may not use this file except in compliance with the License.
>
> You may obtain a copy of the License at
>
>
>
> Caution-http://no/URL/as/yet < Caution-http://no/URL/as/yet >
>
>
>
> Unless required by applicable law or agreed to in writing, software
>
> distributed under the License is distributed on an "AS IS" BASIS,
>
> WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>
> See the License for the specific language governing permissions and
>
> limitations under the License.
>
> """
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5559 bytes
Desc: not available
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20160725/c54d7eb2/attachment.p7s>
More information about the License-discuss
mailing list