public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Joe Pallas <pallas@cs.stanford.edu>
To: sourcenav@sources.redhat.com
Subject: Re: Acceptable Use section added to mail.html
Date: Wed, 13 Jun 2001 09:37:00 -0000	[thread overview]
Message-ID: <2748610000.992450189@olympus> (raw)
In-Reply-To: <Pine.SOL.3.91.1010612134551.9912G-100000@cse.cygnus.com>

Mo DeJong <mdejong@cygnus.com> wrote:

> I just added an "Acceptable Use" section to the mailing
> list signup page.

[which says in part:
Fictional contract claims

Some organizations require disclaimers along the lines of "This email may 
contain confidential information. By reading it you agree to sign over your 
first born child." Obviously, these claims are a legal fantasy. Posts 
including such claims are strictly forbidden.
]

I don't understand how the prohibition on "fictional contract claims" fits 
with the open source philosophy.

We've already established that the people whose messages contain these 
boilerplate notices usually have no control over them.  It's safe to assume 
that their workplace policies are not going to be changed in response to 
this prohibition.

So, the only effect this will have is preventing people who are interested 
in using or contributing to Source Navigator from doing so.  How can this 
benefit the Source Navigator community?

The alternative--to ignore any "legal fictions"--seems both more practical 
and more inclusive.

joe

  reply	other threads:[~2001-06-13  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 14:05 Mo DeJong
2001-06-13  9:37 ` Joe Pallas [this message]
2001-06-13 12:56   ` Mo DeJong

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=2748610000.992450189@olympus \
    --to=pallas@cs.stanford.edu \
    --cc=sourcenav@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).