On 9/21/06, Matt Frye <[EMAIL PROTECTED]> wrote:
This policy has not changed, but YES, the steering *does* gets lots of
SPAM and it takes a lot of time to parse through what's in the junk
bucket.  Sometime after the election, I changed the setting to "Hold"
from "Accept" and took personal responsibility for checking the trap.

If the list was set to "Reject," then this is indeed incorrect
according to our policy, but I have just verified that the setting is
now "Hold."

> If the current SC has changed this,
> then they need to publicize this fact immediately and also provide
> an alternative contact mechanism.

Again, the policy hasn't changed, but I welcome with alacrity any
SC-related queries at mattfrye at gmail dot com .

So, basically, what you're saying is that if anyone wants to reach
the Steering Committee, they have to rely on someone
randomly checking the moderation queue.  I have a serious
problem with that.  What if you go on vacation or a business
trip?  What if it's something timely that the SC needs to know
(i.e. someone has hacked into the TriLUG servers and is spamming
the world)?  The [EMAIL PROTECTED] e-mail address is there
for a reason.  It's the direct link between the membership
and the Steering Committee.  Any obstacle between that
is a problem.  Yes, I know it gets a lot of spam.  It did while
I was on the SC too.  You, however, seem to be using a gmail
account, and that does very good spam detection so I would
imagine that to be a red herring.

TriLUG is a membership organization.  The route between
the membership and the SC should not have roadblocks on it.

Tanner Lovelace
TriLUG SC Co-Chairman 2004-2005
TriLUG SC System Administrator 2002-2004

--
Tanner Lovelace
clubjuggler at gmail dot com
http://wtl.wayfarer.org/
(fieldless) In fess two roundels in pale, a billet fesswise and an
increscent, all sable.
--
TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ  : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/

Reply via email to