Today, Benjamin Scott gleaned this insight:

>   If anyone is willing to get together with me to plan some sort of
> presentation on this topic, please take up the discussion on the
> [EMAIL PROTECTED] "GNHLUG Organization" list.  I have set the "Reply-To"
> header appropriately.

I'd like to again interject here (as I often do), to point out that I
really think issues like this DON'T belong on gnhlug-org (and thusly have
removed Ben's reply-to header).  This is the sort of thing that, by its
very nature, affects (potentially) all members of the group (or at least
those considering whether to attend upcoming meetings).

I think it makes sense to use gnhlug-org to talk about the specific
details of specific meetings; location, agenda and schedule, discussion
topics, guests, and other similar details of meetings and other upcoming
events. Most members (like myself) probably have no interest in these
things, where meeting organizers probably do. However as to what KINDS of
things people want to see at meetings, I really think that discussion
belongs on this list.

I for one am VERY interested in hearing what people are interested in
hearing about at meetings, a) to get to know the membership better (which,
isn't that largely the point of this discussion?) and b) so I can jump in
with a "me too!" vote when appropriate.  I'd rather not have to join
another list to do that, but at the same time I don't want to be bothered
with the details of the other.

Thanks


-- 
You know that everytime I try to go where I really want to be,
It's already where I am, cuz I'm already there...
---------------------------------------------------------------
Derek D. Martin              |  Unix/Linux Geek
[EMAIL PROTECTED] |  [EMAIL PROTECTED]
---------------------------------------------------------------


**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to