Skip to contentSkip to conversation

common-licenses: add OpenDDS

PATCH In review jan 2 participants 3 messages Dec 5, 2020

lore
Share & tools
lore

jan

author
#0 lore raw

PATCH 1/1 common-licenses: add OpenDDS

From: Jan Vermaete <[email protected]>

This is the license of OpenDDS found at
https://github.com/objectcomputing/OpenDDS
as LICENSE at commit 11b2e4771fa323485c0f231f7fa4030feedae9a0.

They have a meta layer at https://github.com/oci-labs/meta-opendds

---
 meta/files/common-licenses/OpenDDS | 50 ++++++++++++++++++++++++++++++
 1 file changed, 50 insertions(+)
 create mode 100644 meta/files/common-licenses/OpenDDS
meta/files/common-licenses/OpenDDS new file +50 -0
new file mode 100644
index 0000000000..e743a00e3a
@@ -0,0 +1,50 @@
+OpenDDS (Licensed Product) is protected by copyright, and is
+distributed under the following terms.
+
+OpenDDS is an open source implementation of the Object Management Group
+(OMG) Data Distribution Service (DDS), developed and copyrighted by
+Object Computing Incorporated (OCI). OpenDDS is both a multi-language
+and multi-platform implementation. The OMG DDS specification is intended
+to be suitable for systems whose requirements include real-time, high
+volume, robustness, failure tolerant data distribution utilizing a
+publish and subscribe model.
+
+Since OpenDDS is open source and free of licensing fees, you are free
+to use, modify, and distribute the source code, as long as you include
+this copyright statement.
+
+In particular, you can use OpenDDS to build proprietary software and
+are under no obligation to redistribute any of your source code that
+is built using OpenDDS. Note however, that you may not do anything to
+the OpenDDS code, such as copyrighting it yourself or claiming
+authorship of the OpenDDS code, that will prevent OpenDDS from being
+distributed freely using an open source development model.
+
+Warranty
+
+LICENSED PRODUCT IS PROVIDED AS IS WITH NO WARRANTIES OF ANY KIND
+INCLUDING THE WARRANTIES OF DESIGN, MERCHANTABILITY AND FITNESS FOR A
+PARTICULAR PURPOSE, NON-INFRINGEMENT, OR ARISING FROM A COURSE OF
+DEALING, USAGE OR TRADE PRACTICE.
+
+Support
+
+LICENSED PRODUCT IS PROVIDED WITH NO SUPPORT AND WITHOUT ANY
+OBLIGATION ON THE PART OF OCI OR ANY OF ITS SUBSIDIARIES OR AFFILIATES
+TO ASSIST IN ITS USE, CORRECTION, MODIFICATION OR ENHANCEMENT.
+
+Support may be available from OCI to users who have agreed to a
+support contract.
+
+Liability
+
+OCI OR ANY OF ITS SUBSIDIARIES OR AFFILIATES SHALL HAVE NO LIABILITY
+WITH RESPECT TO THE INFRINGEMENT OF COPYRIGHTS, TRADE SECRETS OR ANY
+PATENTS BY LICENSED PRODUCT OR ANY PART THEREOF.
+
+IN NO EVENT WILL OCI OR ANY OF ITS SUBSIDIARIES OR AFFILIATES BE
+LIABLE FOR ANY LOST REVENUE OR PROFITS OR OTHER SPECIAL, INDIRECT AND
+CONSEQUENTIAL DAMAGES, EVEN IF OCI HAS BEEN ADVISED OF THE POSSIBILITY
+OF SUCH DAMAGES.
+
+OpenDDS copyright OCI. St. Louis MO USA, 2005
Signature · 1 line
2.25.1
#1 lore raw
Quoted 7 lines · jan

From: Jan Vermaete <[email protected]>

This is the license of OpenDDS found at
https://github.com/objectcomputing/OpenDDS
as LICENSE at commit 11b2e4771fa323485c0f231f7fa4030feedae9a0.

They have a meta layer at https://github.com/oci-labs/meta-opendds

Why not add it in meta-opendds layer?

LICENSE_PATH += "${LAYERDIR}/licenses"
in meta-opendds/conf/layer.conf and meta-opendds/licenses/OpenDDS

If you don't expect other recipes outside this layer using this license, then it doesn't belong to oe-core.

Regards,

author
#2 lore raw

Fine,
I thought that the licenses had to be added to this layer. I deleting the message enough to undo the patch request?