You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Peter Firmstone (JIRA)" <ji...@apache.org> on 2010/05/06 10:14:50 UTC

[jira] Commented: (RIVER-339) Jini Community Standards Patent Non-Assertion Covenant

    [ https://issues.apache.org/jira/browse/RIVER-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864694#action_12864694 ] 

Peter Firmstone commented on RIVER-339:
---------------------------------------

http://web.archive.org/web/20051025223600/http://www.jini.org/standards/docs/jcs-pna-covenant.txt

The covenant was retrieved from the web archive link above.

In today's patent encumbered environment this document appears important, should a copy be stored in svn or in the release artifacts?

> Jini Community Standards Patent   Non-Assertion Covenant
> --------------------------------------------------------
>
>                 Key: RIVER-339
>                 URL: https://issues.apache.org/jira/browse/RIVER-339
>             Project: River
>          Issue Type: Question
>          Components: other
>            Reporter: Peter Firmstone
>            Priority: Minor
>         Attachments: jcs-pna-covenant.txt
>
>
> To quote Jim Hurley from jini-users:
> Sun is re-licensing its Jini technology Standard specifications under
>   ALv2 and providing a separate "Jini Community Standards Patent
>   Non-Assertion Covenant ("Covenant") that enables others to create
>   unrestricted independent implementations of the specifications. This
>   Covenant is available at:
>   http://www.jini.org/standards/docs/jcs-pna-covenant.txt
>   This choice of ALv2, as well as the wording of the Covenant, were made
>   with the hope and expectation that they be used by many others in the Jini
>   Community to share their Jini technology code and Standards Proposals.
>   License choice is now a freedom that developers and companies in the Jini
>   Community have for their Jini technology works. It is hoped that Sun's
>   lead with ALv2 will help act as a catalyst for others to choose ALv2 for
>   their shared works. The resulting commonality around ALv2 will help simplify
>   and facilitate code sharing and collaboration throughout the Jini Community. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.