public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nicholas Jones <carpaski@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gentoo's policy on sender id
Date: Sun, 5 Sep 2004 17:33:32 -0400	[thread overview]
Message-ID: <20040905213332.GA19167@twobit.net> (raw)
In-Reply-To: <200409052024.28670.chrb@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]


Read this one:
http://www.apache.org/foundation/docs/sender-id-position.html

> One of the things that I like about gentoo is the lack of
> deep politics.

There are reasons you don't see deep politics. Most of us don't
like them, hence they are avoided. This is probably part of it.

> If someone is willing to maintain ebuild for packages that
> support sender id then why shouldn't gentoo host them? We
> already have stuff like vmware that is both patented and
> proprietary binary-only software.

Because we then have to deal with non-compliant interaction
with the liceneses. There is a great deal of bad-mojo here
if you read the full Apache position.

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.

Someone get a law degree from somewhere and argue with me,
please.

--NJ



[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-09-05 21:33 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 [this message]
2004-09-06 10:29     ` Chris Bainbridge
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=20040905213332.GA19167@twobit.net \
    --to=carpaski@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