Hello,
I am concerned with the way we seem to be headed in regards to LUG
organizational matters. What with NNHLUG, SLUG, MonadLUG, MVLUG (or whatever
you're calling it, Paul :), and who-knows-what-else, we've got a bunch of
websites, a bunch of mailing lists, and several calendars. In other words,
we've got far more organizational structure then we currently have things to
organize! :-)
I'm worried that the various mini-LUGS are going to have problems
communicating with each other. Why does each mini-LUG need its own mailing
list? Isn't one of the major goals of a LUG information sharing? Doesn't
separating each LUG from each other like this run counter to that purpose?
This is my biggest concern. How can we share information if everybody is
isolated?
Case in point: We have a vigorous discussion about posting jobs to the main
discussion list. It seemed like more people were in favor then against. It
settles down. Next, we find out that someone has setup [EMAIL PROTECTED] but
hadn't told anyone else about it. Which way are we going?
People, we need to make sure we are COMMUNICATING here. :-) We have this
nice [EMAIL PROTECTED] mailing list -- make use of it! :) If you want
to, for example, setup a jobs mailing list, maybe it would be a good idea to
send out an RFC (Request For Comments) here, first? This is why I am posting
all this drivel about what I'm doing at NHCTC -- to make sure the information
is available, and so anyone who thinks I'm doing wrong can tell me so.
I'm not against a linux-jobs mailing list, per se. Personally, I think it's
overkill at this point, but let's assume it isn't, for the purposes of this
discussion. Is [EMAIL PROTECTED] just for the Seacoast? Wouldn't it make more
sense to have a single state-wide list, e.g., [EMAIL PROTECTED]?
The suggestion has been made that the SLUG calendar CGI be used for all
GNHLUG (and the mini-LUGs). I agree; I was going to suggest it myself. But I
think it should go on gnhlug.org -- one central calendar for all of GNHLUG
makes more sense then one for each mini-LUG.
Let me go further, and ask: Should we really have a complete website with a
second-level domain name for each mini-lug? Would pages on www.gnhlug.org be
better (reduces confusion, keeps things in one place, doesn't pollute the DNS
namespace)? Maybe http://www.gnhlug.org/slug and so on? Maybe
http://slug.gnhlug.org and so on?
We've got mailing lists at several different servers. I think it is past
time to look at consolidating everything into a single server... like this:
[EMAIL PROTECTED] (General discussion, replaces [EMAIL PROTECTED])
[EMAIL PROTECTED] (Announcements only, replaces gnhlug-announce...)
[EMAIL PROTECTED] (LUG Administrivia, replaces [EMAIL PROTECTED])
[EMAIL PROTECTED] (Linux job postings)
.... etc ....
Should we look at setting up a dedicated GNHLUG server for this purpose,
complete with remote admin access? I'm not saying Mark, Bruce, et. al. aren't
doing a good job -- far from it. I'm just thinking it is time to bring all
the pieces of GNHLUG together under one roof.
I'm not trying to rain on anybody's parade here, but I think we're in
serious danger of segmenting ourselves off from each other, and that is the
*LAST* thing we want to do.
Comments? Suggestions? Ideas? Disagreements? Corrections? Flames?
Keep in touch, folks. :-)
--
Ben Scott
[EMAIL PROTECTED]
