From: <Angela_Wang@compal.com>
To: <openbmc@lists.ozlabs.org>
Subject: Questions about OpenBMC
Date: Tue, 14 Feb 2023 03:26:50 +0000 [thread overview]
Message-ID: <86cb2f3434424349ad39c49aafdba2ce@compal.com> (raw)
In-Reply-To: <fa0bc7ae70714cd7816d542a8fc017d7@compal.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1857 bytes --]
Dear Sir or Madam,
Greetings. We are interested in incorporating OpenBMC into our commercial product/service, and we are studying OpenBMC’s licensing policy as attached, which is downloaded from https://github.com/openbmc/docs/blob/master/LICENSE.
To make sure we understand the terms and conditions correctly, may we seek your clarification for below 2 points?
1. Logo: in Section 2-b-2 it says “Patent and trademark rights are not licensed under this Public License.”, thus to our understanding, we (licensee) are not allowed to use OpenBMC’s logo because the logo is one kind of trademark and belongs to the licensor. For example, when we adopt the interface (see below) into our commercial product/service, we should remove this particular OpenBMC logo “[cid:image003.jpg@01D94067.39FA3B90]” and replace it with our own logo/service mark. On the other hand, we should indicate (for example put a copyright statement in our product/service description) that our commercial product/service incorporating codes which is under GitHub’s copyright authorization. Is this understanding correct? Please correct me if I am wrong.
[cid:image004.jpg@01D94067.39FA3B90][cid:image009.jpg@01D94067.39FA3B90]
2. Pricing: from Section 2-b-3 we understand that we are allowed to sell our commercial product/service which incorporates GitHub’s OpenBMC code on a royalty-free basis. There is no need to report to GitHub our sales amount, and GitHub will not audit our sales record either. As for the pricing listed in https://github.com/pricing, it refers to the extra technical support provided by GitHub, and we will need to pay only if we need these extra technical support service from GitHub. Is this understanding correct? Please correct me if I am wrong.
Your response is appreciated.
Regards,
Angela
[-- Attachment #1.1.2: Type: text/html, Size: 11803 bytes --]
[-- Attachment #1.2: image003.jpg --]
[-- Type: image/jpeg, Size: 2560 bytes --]
[-- Attachment #1.3: image004.jpg --]
[-- Type: image/jpeg, Size: 38408 bytes --]
[-- Attachment #1.4: image009.jpg --]
[-- Type: image/jpeg, Size: 65421 bytes --]
[-- Attachment #2: Creative Commons Attribution 4.0 International Public License.docx --]
[-- Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document, Size: 19951 bytes --]
next parent reply other threads:[~2023-02-19 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa0bc7ae70714cd7816d542a8fc017d7@compal.com>
2023-02-14 3:26 ` Angela_Wang [this message]
2023-02-22 18:18 ` Questions about OpenBMC Joseph Reynolds
2023-03-16 12:09 ` [External Mail] " Angela_Wang
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=86cb2f3434424349ad39c49aafdba2ce@compal.com \
--to=angela_wang@compal.com \
--cc=openbmc@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).