From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: licenses@gentoo.org
Subject: Re: [gentoo-dev] Guidance on distributed patented software
Date: Mon, 20 Sep 2021 13:27:37 -0400 [thread overview]
Message-ID: <CAGfcS_knT99Q63FKZA0L-NOd9wHs7i261TLQxivyy=m1DHut8Q@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr_LHo4Kbh-7no4ueUgLQwGR1Q-marf+=0z5icEh8tAkxA@mail.gmail.com>
On Mon, Sep 20, 2021 at 12:46 PM Alec Warner <antarus@gentoo.org> wrote:
>
> Could we add some text to the license concepts covering patents? It
> seems to have been omitted?
> Is my understanding of how we manage patented software correct?
I think you have the gist of it. Is there actually anything in the
repo these days which is patent-encumbered? I realize this is a
little tangential, but I think this is probably why we don't have a
well-thought policy: it just doesn't come up much.
The situation comes up less often since everything is copyrighted by
default, but software patents in FOSS are relatively rare. (Partially
because they're such a minefield that it discourages even creating
FOSS in the first place. Partially because they're such a minefield
that people tend to favor non-encumbered algorithms for things that
are commonplace now.)
Things that used to be patent-encumbered that were prevalent in FOSS
in the past include:
1. The GIF file format.
2. FAT-based filesystems.
3. MPEG-related codecs (codecs might be a space where patents are
still relevant).
4. RSA
I'm sure there are others I'm not thinking of offhand. All of these
helped drive adoption of more open standards, which is why we don't
run into this stuff as often.
Another topic like this are encryption keys like for DVDCSS and so on.
Those fall outside both copyright and patent law, but are legally
troublesome. Then there are export controls like ITAR/etc - less of
an issue today but might still apply to some things.
--
Rich
next prev parent reply other threads:[~2021-09-20 17:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 16:46 [gentoo-dev] Guidance on distributed patented software Alec Warner
2021-09-20 17:27 ` Rich Freeman [this message]
2021-09-20 18:15 ` Robin H. Johnson
2021-09-20 18:41 ` Ulrich Mueller
2021-09-20 19:20 ` Robin H. Johnson
2021-09-22 12:54 ` Joshua Kinard
2021-09-22 16:37 ` Robin H. Johnson
2021-09-23 5:54 ` Joshua Kinard
2021-09-23 15:52 ` Peter Stuge
[not found] ` <CAAr7Pr9a6cRbHDxkUbKwxabW8skh1izA7C2GqTE1XF8mg-CV0g@mail.gmail.com>
2021-09-24 7:46 ` Joshua Kinard
[not found] ` <20210924095510.6ff13620@computer>
2021-09-25 19:44 ` Joshua Kinard
2021-09-26 17:09 ` Peter Stuge
2021-09-26 19:20 ` Rich Freeman
2021-09-27 18:14 ` Marek Szuba
2021-09-27 21:09 ` Rich Freeman
2021-09-26 19:41 ` Sam James
2021-09-21 15:25 ` Andreas K. Huettel
2021-09-20 18:30 ` [gentoo-dev] " Ulrich Mueller
2021-09-26 6:38 ` Alec Warner
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='CAGfcS_knT99Q63FKZA0L-NOd9wHs7i261TLQxivyy=m1DHut8Q@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=licenses@gentoo.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