public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "jan" <jan.vermaete@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Jan Vermaete <jan.vermaete@gmail.com>
Subject: [PATCH] common-licenses: add OpenDDS
Date: Sat,  5 Dec 2020 19:49:34 +0100	[thread overview]
Message-ID: <20201205184934.6105-1-jan.vermaet@gmail.com> (raw)

From: Jan Vermaete <jan.vermaete@gmail.com>

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

Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
---
 meta/files/common-licenses/OpenDDS | 50 ++++++++++++++++++++++++++++++
 1 file changed, 50 insertions(+)
 create mode 100644 meta/files/common-licenses/OpenDDS

diff --git a/meta/files/common-licenses/OpenDDS b/meta/files/common-licenses/OpenDDS
new file mode 100644
index 0000000000..e743a00e3a
--- /dev/null
+++ b/meta/files/common-licenses/OpenDDS
@@ -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
-- 
2.25.1


             reply	other threads:[~2020-12-05 18:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 18:49 jan [this message]
2020-12-05 18:56 ` [OE-core] [PATCH] common-licenses: add OpenDDS Martin Jansa
2020-12-05 19:03   ` jan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201205184934.6105-1-jan.vermaet@gmail.com \
    --to=jan.vermaete@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox