From: Phil Edwards <pedwards@jaj.com>
To: overseers@sourceware.cygnus.com
Subject: Re: ORBS redux, round n
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <200003241717.MAA07788@jaj.com> (raw)
Chris Faylor <cgf@cygnus.com>:
> On Fri, Mar 24, 2000 at 04:54:42PM +0000, Jonathan Larmour wrote:
> >Jim Kingdon wrote:
> >>
> >> The current list of people in the "sourceware" group (who can edit
> >> infra/bin/rbl-whitelist) are:
> >
> >Well, if I do get added to the sourceware group, my first act will be
> >editting http://sourceware.cygnus.com/sourceware/spam.html to mention this
> >file!
>
> Do we want to make it publicly known that there is a whitelist? That might
> remove an incentive for people to actually work to fix the problem.
"If you make an exception for one, you'll have to make exceptions for
everyone..."
My experience with these kinds of exceptions is that you don't publicize
them, and that you make the requirements to get on the list very stringent,
with no exceptions. Of course, if you're going to be stringent about
no-exceptions-on-the-exceptions-list, you should probably be stringent
about ORBS in the first place, etc, etc.
Phil
WARNING: multiple messages have this Message-ID
From: Phil Edwards <pedwards@jaj.com>
To: overseers@sourceware.cygnus.com
Subject: Re: ORBS redux, round n
Date: Fri, 24 Mar 2000 09:04:00 -0000 [thread overview]
Message-ID: <200003241717.MAA07788@jaj.com> (raw)
Message-ID: <20000324090400.WJUQ7EdRF4geaYpiGq5ZBC5I17SDqexmdHImpgOgkMM@z> (raw)
Chris Faylor <cgf@cygnus.com>:
> On Fri, Mar 24, 2000 at 04:54:42PM +0000, Jonathan Larmour wrote:
> >Jim Kingdon wrote:
> >>
> >> The current list of people in the "sourceware" group (who can edit
> >> infra/bin/rbl-whitelist) are:
> >
> >Well, if I do get added to the sourceware group, my first act will be
> >editting http://sourceware.cygnus.com/sourceware/spam.html to mention this
> >file!
>
> Do we want to make it publicly known that there is a whitelist? That might
> remove an incentive for people to actually work to fix the problem.
"If you make an exception for one, you'll have to make exceptions for
everyone..."
My experience with these kinds of exceptions is that you don't publicize
them, and that you make the requirements to get on the list very stringent,
with no exceptions. Of course, if you're going to be stringent about
no-exceptions-on-the-exceptions-list, you should probably be stringent
about ORBS in the first place, etc, etc.
Phil
next reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Phil Edwards [this message]
2000-03-24 9:04 ` Phil Edwards
2000-12-30 6:08 Jim Kingdon
2000-03-24 8:22 ` Jim Kingdon
2000-12-30 6:08 ` Chris Faylor
2000-03-24 8:28 ` Chris Faylor
2000-12-30 6:08 ` Jonathan Larmour
2000-03-24 8:32 ` Jonathan Larmour
2000-12-30 6:08 ` Chris Faylor
2000-03-24 8:33 ` Chris Faylor
2000-12-30 6:08 ` Jim Kingdon
2000-03-24 8:41 ` Jim Kingdon
2000-12-30 6:08 ` Jeffrey A Law
2000-03-24 9:11 ` Jeffrey A Law
2000-12-30 6:08 ` Jonathan Larmour
2000-03-24 8:54 ` Jonathan Larmour
2000-12-30 6:08 ` Chris Faylor
2000-03-24 8:58 ` Chris Faylor
2000-12-30 6:08 ` Chris Faylor
2000-03-24 9:02 ` Chris Faylor
2000-12-30 6:08 ` Jim Kingdon
2000-03-24 9:54 ` Jim Kingdon
2000-12-30 6:08 ` Jeffrey A Law
2000-03-24 9:19 ` Jeffrey A Law
2000-12-30 6:08 ` Jonathan Larmour
2000-03-24 9:22 ` Jonathan Larmour
2000-12-30 6:08 ` Chris Faylor
2000-03-24 9:57 ` Chris Faylor
2000-12-30 6:08 ` Tom Tromey
2000-03-24 8:50 ` Tom Tromey
2000-12-30 6:08 ` Chris Faylor
2000-03-24 8:53 ` Chris Faylor
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=200003241717.MAA07788@jaj.com \
--to=pedwards@jaj.com \
--cc=overseers@sourceware.cygnus.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).