[License-review] NOSA 2.0 and Government licensing [was: moving to an issue tracker [was Re: Some notes for license submitters]]

[Nigel T]

On Wed, Jun 20, 2018 at 3:43 PM, Bruce Perens <bruce at perens.com> wrote:

>
>
> On Wed, Jun 20, 2018 at 12:10 PM, Nigel T <nigel.2048 at gmail.com> wrote:
>>
>> You will have to explain how public domain code released under a specific
>> agreement impacts other public domain code that isn't under the agreement.
>>
>
> OSI sets precedent by accepting the text, which can be used in court cases
> to stop Open Source developers from fighting assertions of contractual
> restrictions on public domain software where such would hurt
> interoperability with proprietary software.
>
>
If you look at my own court case, you can see where statements of Richard
> Stallman, Bradley Kuhn, and I are used in the plaintiff's exhibits.
>

That is already the case with NOSA 1.3 isn't it?


> That is an odd objection.  NOSA 1.3 code has been incorporated into other
>> open source projects in the past and parts of the community have maintained
>> NOSA code on their own without any license proliferation issues.
>>
>
> Are you really sure? One would expect that there is at least some license
> combination in such projects.
>
>
OpenVSP is a NOSA project being supported by the community (rather than
NASA) I found via google.  I released code to the NASA WorldWind project
under NOSA 1.3 and I had commit privs in the older C# repo.

I also don't see the issue with license combination in terms of
proliferation.  NOSA code has been used in Apache licensed projects and
NOSA projects have used other open source licensed code.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20180620/e2d89954/attachment.html>