[NTLUG:Discuss] NTLUG Discuss Guidelines

[MadHat]

I apologize for it taking so long to get back.
I have read through all the messages about the "guidelines" and I have a
few comments.

First, the note about sending suggestions off list were there because if
it wasn't something that needed to be discussed, it would be better to
not have it sent to the list.  I agree that some of it did need to be
discussed and I have gotten a lot from this.

Second, yes this is mostly netiquette stuff, but that is because the
problems that come up are more often someone not thinking of someone
else on the list.

This is not a moderated group (and won't become one with me as admin),
but there does have to be some idea of what should be done and what
shouldn't.  Some people have said the rules are "old" and not valid, and
other have stated that they don't answer any questions, while still
other are saying that we don't need them because everything has been
fine up until now. 

Let me approach each one of these and explain why I think it is good to
include the items in the guidelines and try to answer some questions and
comments from some of you. 

On the comments that that the guidelines are out of date because of the
entries on "me too" posts and on not replying with less that is quoted
and the length of the sig.  All three of these are not completely based
on bandwidth, but at the same time are.  Now it was argued that a 10
line signature takes no more time than a 4 line.
Well, it has been that 4 lines is the "proper" netiquette for a
signature, so that is where that number came from, and if you choose not
to follow that, that is your choice. This and the items on "me too"
posts and the quoting were included because if you add 100 bytes to your
message, then send it to the list, that is 100 bytes * 300 members =
30Kb.  Now remember, we have our mail hosted by Hex.net, they have to
pay for the bandwidth and if you have really large signatures, or quote
a 200 line message for 4 lines of reply, that is more bandwidth they
have to pay for.  It is all just being considerate.  Not to mention that
by trimming down the replied section of the email it is often easier for
people to read.  No, it is not necessary to have more new lines than
quoted line, it is just a guideline to try to use.

Next, no I didn't go in and say, this item is on topic and this one is
not and this one is, etc...  because we all know, more or less :~), what
Linux is and we should have a good idea what is Linux related (besides,
we couldn't cover everything and there would always be exceptions).  If
the list has worked well until now, why try to admin it so closely (oh
no, now I am a hypocrite).  Here is the idea behind all of this, we need
to talk about Linux, we need to not make personal remarks and we need to
keep in mind that we (as individules) are not the only ones here.

I don't want to change the list or try to set up 6 more lists, but I do
want people to feel like they can post a Linux question and I want
people to think before they post.  It is often easier to post a question
here than a news group (besides the fact that some don't use newsgroups,
they are intimidating to some).  But we need to think about what we post
before we post it.  Honestly, is something about a MS commercial's music
about Linux, even indirectly?  Not that I can see.  Is talking about how
MS has stated how bad Linux is Linux related?  I think so. 

As for the Press releases, in my eyes they are fine, as long as you
think it pertains to the group and you have something to say about it or
want to start a discussion about it.  If you are just wanting to pass
that article on, this really isn't the proper place.


So with all this said, these were not rules, but ideas for guidelines. 
Guidelines are just concepts to keep in mind and are not the type of
thing that you will get booted (which is partly why I choose "NTLUG
Discuss _Guidelines_" instead of "NTLUG Discuss _Rules_").  I will not
kick anyone from the list.  I just want to be able to discuss Linux in a
civilized fashion and not have people worried to post because of the
response they might get.

Thanks

-- 
%_=split';','2e;hac;40;not;64;ju;66; Perl ;68;st a;6f;ker;75;her';
print map $_{unpack "H2",$_}, split //,
'madhat at unspecific.com'
# aka Lee Heath, but don't tell anyone.