Angus Lees said something along the lines of:
> i'd like to come up with some rough guidelines about what is or isn't
> allowed on the list.
>
> jeff, once decided on - can we put this in a prominent place on the
> slug web pages.
Look at questions 6 & 7 on the SLUG FAQ <URL: http://slug.org.au/faq.shtml>
One thing I realise I must add is, "Respect Netiquette. For example, do not
CC private email to the list."
> RESTRICTED:
>
> non-linux (but nerdy anyway ;) discussion. this includes MS bashing.
> eg: "hey, i saw the railway indicator boards blue screen!"
> eg: "cool new gadget that doesn't run linux"
> [or should this be under "allowed" ?]
I think this borders on the "community vbs. utility" point that I bring up
when the idea of splitting the lists comes up.
What do you (plural, not just Gus) want the list to be? A droll, grey
support network, or a lively, interested community? Right now I think SLUG
has a number of challenges on the "lively, interested community" front - not
just related to the mailing list.
I'd be horribly disappointed if we managed to McCarthy our list to complete
boredom.
> HTML or "rich text" posts.
Well, whilst it is annoying and frustrating, I don't think this should be a
"not allowed" point. Nor should tdif attachments and multiparts. More often
than not, the poster is privately reminded when they first start posting,
and will probably change to text, and if not - get yourself a mailer that
can handle it! (for those who don't - mutt and w3m are a good duo, and
Debian can set it up for you without you even having to lift a finger)
I dread the day when someone asks us to filter out these emails. Argh!
Anyway, after discussion, I'll add some points to the FAQ.
- Jeff
-- [EMAIL PROTECTED] ------------------------------- http://linux.conf.au/ --
Ye shall be cursed to fall in love so easily, and yet be so
cold of heart as never to express it.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
