Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org, dewar@adacore.com, b07584@freescale.com,
	        rgetz@blackfin.uclinux.org, jimb@codesourcery.com
Subject: Re: Posting from work/university addresses
Date: Mon, 06 Aug 2007 14:04:00 -0000	[thread overview]
Message-ID: <m3hcncvk12.fsf@localhost.localdomain> (raw)
In-Reply-To: <u4pjfb0c7.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> > Cc: gdb@sourceware.org, dewar@adacore.com, b07584@freescale.com,         rgetz@blackfin.uclinux.org, jimb@codesourcery.com
> > From: Ian Lance Taylor <iant@google.com>
> > Date: 04 Aug 2007 11:32:44 -0700
> > 
> > As far as I can tell, you are requesting that we not do anything dumb,
> 
> No, that's not it.  My problem is that I don't see the motivation for
> rejecting such messages spelled out anywhere.  The URL you mentioned
> _advises_ to do something, but, AFAIU, there's some policy issues
> involved here, which are not explained anywhere.

The reason we would like to block the disclaimers is that they impose
a legal liability on us.  The problematic disclaimers are the ones
which say something along the lines of "If you are not the intended
recipient you must not disseminate, copy ....  We request that you
notify COMPANYNAME immediately."  The problem is that we can not obey
those instructions, as we automatically archive the e-mail message and
make it available for anybody in the world to see.  Since we are
violating the terms of the disclaimer, the sender has reasonable
grounds to sue us.  It is likely that the suit would not prevail in
the end, as my understanding is that the disclaimers are unenforceable
under U.S. law, but that does not matter since we are a volunteer
organization with no means to defend ourselves.  I think it is very
unwise to leave ourselves open to this sort of legal liability.  This
is of course a personal issue for me since as one of the
administrators of gcc.gnu.org/sourceware.org, and the owner of the
domain name sourceware.org, I would be personally named in the
lawsuit.

This may seem rather farfetched to you, but just in this year I have
received two threatening legal letters concerning sourceware.org on
other issues.  I was able to defuse both issues (one concerning
defamatory spam e-mail we had archived, one concerning the use of
software downloaded from sourceware.org in a contract dispute), but I
have a strong personal interest in defusing these issues before they
arise.

If there were a reason to accept those e-mail messages, then I would
have a different opinion on the matter.  But I see no reason that we
should accept them.  They are infrequent and relatively easy to avoid.
I know of only one case of a person who was required to use those
disclaimers and was prohibited from using web-based e-mail accounts at
work.  I am willing to sacrifice one potential contributor for this
issue.

Note that EU law does not require anything along the lines of "If you
are not the intended recipient....".  We have no problem with adding
company identification information to e-mail messages.  Many people do
this even within the U.S.

> > we're free software volunteers just like you.  We're on your side.
> > We won't do anything dumb.
> 
> Isn't this a matter of policy of Red Hat (or some other organization)?
> I do trust you, but I don't know about organizations.

No, this has nothing to do with Red Hat or any other organization.
Neither Chris nor I work for Red Hat.

Ian


  parent reply	other threads:[~2007-08-06 14:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30  8:14 Why does gdb implement 'next' command with a series of "vCont;s"? congli
2007-07-30 22:12 ` Posting from work/university addresses Jim Blandy
2007-07-31  0:08   ` Anmol P. Paralkar
2007-07-31  1:08     ` Christopher Faylor
2007-08-02 16:58       ` Robin Getz
2007-08-02 17:12         ` Robert Dewar
2007-08-02 17:42           ` Robin Getz
2007-08-02 18:09             ` Ian Lance Taylor
2007-08-04 17:36             ` Eric Weddington
2007-08-02 18:23           ` Jim Blandy
2007-08-02 18:34             ` Christopher Faylor
2007-08-03 12:05               ` Eli Zaretskii
2007-08-03 14:27                 ` Christopher Faylor
2007-08-03 14:39                 ` Ian Lance Taylor
2007-08-03 17:10                   ` Eli Zaretskii
2007-08-03 23:11                     ` Christopher Faylor
2007-08-04  8:41                       ` Eli Zaretskii
2007-08-04 18:36                         ` Ian Lance Taylor
2007-08-04 18:51                           ` Eli Zaretskii
2007-08-05  0:03                             ` Christopher Faylor
2007-08-05  3:51                               ` Robin Getz
2007-08-05  5:07                                 ` Christopher Faylor
2007-08-05 12:03                                   ` Robert Dewar
2007-08-05 18:27                                     ` Christopher Faylor
2007-08-06  6:53                                   ` Eli Zaretskii
2007-08-06 14:04                             ` Ian Lance Taylor [this message]
2007-08-06 14:22                               ` Eli Zaretskii
2007-08-04 20:04                           ` Bob Rossi
2007-08-05  0:06                             ` Christopher Faylor
2007-08-05  1:58                               ` Bob Rossi
2007-08-05  3:13                               ` Eli Zaretskii
2007-08-05  4:33                                 ` Christopher Faylor
2007-08-06 14:07                             ` Ian Lance Taylor
2007-07-31  7:59   ` Wenbo Yang

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=m3hcncvk12.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=b07584@freescale.com \
    --cc=dewar@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=jimb@codesourcery.com \
    --cc=rgetz@blackfin.uclinux.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