public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: Cœur <coeur@gmx.fr>
Cc: devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH] EmbeddedPkg: Fix various typos
Date: Thu, 4 Jul 2019 15:20:38 +0100	[thread overview]
Message-ID: <20190704142038.h4rjbjb3ybqgtcpe@bivouac.eciton.net> (raw)
In-Reply-To: <28803.1562249017634518697@groups.io>

On Thu, Jul 04, 2019 at 07:03:37AM -0700, Cœur wrote:
> On Thu, Jul 4, 2019 at 09:01 PM, Leif Lindholm wrote:
> 
> > 
> > Urgh, don't make me elaborate on the implications of public domain
> > versus copyright... If you're interested, have a look at
> > https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Public_Domain_within_SPDX_Files
> > 
> 
> This link says:
> 
> > Some commonly used “Public Domain dedications” have already been included in the SPDX License List (e.g., ANTLR, Sax, CC-0).
> 
> And CC-0 was what I was proposing; I'm aware of the difference with
> American Public Domain, as, for the record, I'm an elected Wikipedia
> Administrator, so I've also had my share of licensing questions.

That is a very fair point, but see also:
3. The rules around “Public Domain” often vary or are unspecified
   jurisdiction to jurisdiction. Adding to the confusion, some
   jurisdictions may not even recognize the concept of “Public Domain”
   (or similar). As such, a license may nevertheless be required or
   implied in these cases.

We already have *some* public domain code in the tree, and are trying
to figure out what to do about that.

Basically, we are quite heavily dependent on corporate contributors,
and we need to keep things simple for them (and their legal
departments).

> Anyway, BSD+Patent is really fine by me.

Thanks!

Best Regards,

Leif

      reply	other threads:[~2019-07-04 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28  3:42 [PATCH] EmbeddedPkg: Fix various typos Cœur
2019-07-03 15:30 ` [edk2-devel] " Leif Lindholm
2019-07-03 16:58   ` Cœur
2019-07-04 13:01     ` Leif Lindholm
2019-07-04 14:03       ` Cœur
2019-07-04 14:20         ` Leif Lindholm [this message]

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-list 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=20190704142038.h4rjbjb3ybqgtcpe@bivouac.eciton.net \
    --to=devel@edk2.groups.io \
    /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