From: Chris Bainbridge <chrb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-core@lists.gentoo.org
Subject: Re: [gentoo-dev] gentoo's policy on sender id
Date: Mon, 6 Sep 2004 11:29:28 +0100 [thread overview]
Message-ID: <200409061129.28448.chrb@gentoo.org> (raw)
In-Reply-To: <20040905213332.GA19167@twobit.net>
On Sunday 05 September 2004 22:33, Nicholas Jones wrote:
> Recall that every distro has dropped XFree because of the
> 'logo adjacency' issue? Violation of the GPL... Well, that
> is merely _one_ problem with Sender-ID.
>
> We would not have the infrastructure to manage compliance
> with such an annoying licence. I am not certain on this
> point here, but it's entirely possible that arbitrary linking
> of applications with sender-id may be inducing a violation
> of the agreement. It's possible that we would be liable.
>
> There are also points regarding termination of the licence
> and the inability to transfer it. So there is no guarentee
> that software using sender-id could be passed on to another
> developer/team. Suddenly finding yourself in violation of
> a license is probably not a good idea if your income is
> zero, especially facing a prosecution with several billion
> in the bank.
From the gentoo point of view all of these problems are restrictions on
redistribution. At worst, RESTRICT="nomirror" solves them. Lets at least have
a consistent policy - we already have software (particularly games) that we
aren't allowed to redistribute. Sender-id software is no different. Having
said that, I doubt that this patent actually prohibits 3rd party mirrors like
cnet.
Theres no doubt that this is a bad patent/license from a software developer
point of view, but gentoo is not in the business of developing mail server
software. The decision of whether to support sender-id should be left in the
hands of people who are (or are we going to start patching postfix to remove
code?).
It's a slippery slope to reject ebuilds because we don't agree with the
licenses imposed on the developers of those packages, or because we believe
that they violate software patents. Where do you draw the line? There is no
doubt that the linux kernel violates some (bad) patents. Should it
potentially be removed? How about quake3 - I'm not allowed to rebrand and
redistribute it without paying a lot of money for a license. Should it also
be excluded from gentoo?
> Someone get a law degree from somewhere and argue with me,
> please.
You can email Microsofts licensing people and they will forward any questions
they can't answer to their lawyers. It might be useful to do this anyway, for
future protection.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-06 10:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 14:00 [gentoo-dev] gentoo's policy on sender id John Davis
2004-09-05 16:26 ` Tom Gall
2004-09-05 19:24 ` Chris Bainbridge
2004-09-05 20:33 ` Stephen P. Becker
2004-09-05 21:33 ` Nicholas Jones
2004-09-06 10:29 ` Chris Bainbridge [this message]
2004-09-06 18:36 ` [gentoo-dev] Re: [gentoo-core] " Nicholas Jones
2004-09-16 4:38 ` Rob Cakebread
2004-09-16 14:02 ` Malte S. Stretz
2004-09-05 23:44 ` Kurt Lieber
2004-09-16 23:25 ` Michiel de Bruijne
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=200409061129.28448.chrb@gentoo.org \
--to=chrb@gentoo.org \
--cc=gentoo-core@lists.gentoo.org \
--cc=gentoo-dev@lists.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