> Two things.
> 
> First, has usage of the <[EMAIL PROTECTED]> and
> <[EMAIL PROTECTED]> lists been deprecated?  I still have them in my
> mailbox but don't see them on a lot of the traffic, including meeting
> announcements that I'd expect to see going there.

I wouldn't expect this traffic to be on announce, many people are 
subscribed to announce
to hear only about the general meeting. This is not a general meeting.
 
>  Second, some thoughts about tonight's meeting:
> 
> I think a lot of the proposed agenda items (subchapter pros/cons, proposed
> subchapters) should not require a lot of meeting time.  From the recent
> discussions on the mailing lists it seems like the subchapter structure has
> garnered a significant consensus, the biggest questions now seem to be defining
> the details not deciding whether or not to move in that direction.  Subchapter
> criteria might be the biggest bone of contention, maybe also putting names to
> jobs (although I'd contend that the organization meeting should give higher
> priority to a general solution of how that gets done than to doing it for
> specific cases at this time, so that need not be a major time sink).

Am I the only one who thinks we're getting a little to wrapped up in this?
If people want to form subchapters GNHLUG has no ability/power to stop
them, if I want to start the "Linux users group for people who live in my
house" subchapeter I'm going to, and I wouldn't look to GNHLUG for
approval.

I got involved with GNHLUG (and later MonadLUG) because it was fun....
what I see proposed below is a group so wrapped up in the organization of
itself that nothing would get accomplished. The question I'm asking myself
right now is "How is GNHLUG going to survive?". Now that Maddog has
stepped down we need somebody (or a group) to take over the duties of
finding speakers and places to meet, not a group that dictates the rules
of what qualifies as a subcapter and who will be on which subcommitee!

It appears to me that the current approach is to try and apply the big
business model of management to an inheratly loose knit organization.
Linux itself is somewhat disorganised....what makes us thing the user
group should be this formal?

I appologize if this offends anyone, that was not my intention. I just see
this moving in what I consider a dangerous direction.

--rdp






Reply via email to