From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: licenses <licenses@gentoo.org>
Subject: [gentoo-dev] [RFC] @DISTFILE-REDISTRIBUTABLE license group
Date: Sat, 21 Sep 2019 09:17:14 +0200 [thread overview]
Message-ID: <289b815331e4d29c9cb5bb7e5613e30ab6016806.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
Hi,
We currently have @BINARY-REDISTRIBUTABLE license group that somewhat
concerns RESTRICT=bindist. I think it'd be reasonable to introduce
a matching group concerning RESTRICT=mirror.
My proposition would be to add @DISTFILE-REDISTRIBUTABLE group with
the following rules:
- MUST permit redistribution of unmodified distfiles
- MUST NOT require explicit approval (No items from @EULA)
- MAY prohibit redistributing modified distfiles
- MAY restrict the cost of redistribution
Rationale: the main idea is to aid checking for missing
RESTRICT="mirror". The rules are based on current bindist group but are
more relaxed given the specific use case of our mirrors. Most notably:
1. It permits licenses that prohibit redistributing modified distfiles.
In this case, due diligence is required from developers. If this is
prohibited, they may only add original upstream sources to SRC_URI.
2. It permits restrictions on cost of redistribution, as some upstreams
prohibit selling their products. While this renders them non-free, it
shouldn't be a problem for our mirrors since we don't expect to sell
stuff there ;-).
Note that while technically there could be a problem with selling, say,
Gentoo CDs with distfiles included, RESTRICT=mirror doesn't cover this
case anyway.
WDYT?
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next reply other threads:[~2019-09-21 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 7:17 Michał Górny [this message]
2019-09-21 19:27 ` [gentoo-dev] [RFC] @DISTFILE-REDISTRIBUTABLE license group Ulrich Mueller
2019-09-21 20:00 ` Michał Górny
2019-09-21 20:37 ` Ulrich Mueller
2019-09-21 20:57 ` Michał Górny
2019-09-25 6:19 ` Michał Górny
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=289b815331e4d29c9cb5bb7e5613e30ab6016806.camel@gentoo.org \
--to=mgorny@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