Re: [SLUG] mail list acceptable use guidelines
tom burkart said something along the lines of: > I also have been noticing that replies usually go to the list as a > whole. I have started doing it as well to try to reduce the number of > followups on the list. Really, what should happen is that these should > end up in the archives somehow without cluttering the list - does that > sound feasible? You want to reply to emails, have the valuable answers in those emails go into the archives, but don't want them going out to the list? The archives archive only what is sent to the list. If you have a good answer, it's much more important to send that to the list so everyone knows about it. The archives are for finding answers to questions that have been asked before - the list is for a) helping out others with stuff you know about, and b) finding out stuff you never even thought to ask for! :) - 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
Re: [SLUG] mail list acceptable use guidelines
On Thu, 12 Oct 2000, Dave Fitch wrote: > just bounce all attachments, whatever their type. Strip is probably easier than bounce... > maybe repeat offenders (within a certain timeframe) should be put > on a list of people who can't post without manual approval? Sounds like you are volunteering for this job? ;-) I would have thought we had better things to do than police a list in this manner. > Probably (a) a hassle for the list maintainers, and (b) pointless > anyway with free web email accounts etc. Quite true. Something that bugs me every now and then is when people include the previous message verbatim. We are all rather intelligent and all that should be necessary is a mind jogger... I also have been noticing that replies usually go to the list as a whole. I have started doing it as well to try to reduce the number of followups on the list. Really, what should happen is that these should end up in the archives somehow without cluttering the list - does that sound feasible? tom. Consultant AUSSECPhone: 61 4 1768 2202 339 Blaxland Rd., Ryde NSW 2112 Email: [EMAIL PROTECTED] -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
Re: [SLUG] mail list acceptable use guidelines
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 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
Re: [SLUG] mail list acceptable use guidelines
[EMAIL PROTECTED] said something along the lines of: > Just a thought, why not appoint someone as god of the lists to > enforce such measures as needed. We have list gods already! ;) > eg. This thread is of topic and I am killing it now, if you wish > to further discuss this topic, please feel free to do so off-list. > If you maintain posts on this thread you will be cast off to dalnet irc. But they don't have the time, nor the inclination to do this. If SLUG had to be moderated much more than it is now, we wouldn't be able to do all the other things we do for Free Software (let alone earn money, have a life, etc, etc, etc...) - 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
Re: [SLUG] mail list acceptable use guidelines
Terry Collins said something along the lines of: > So far I know of one list that has been started to get away from the > general list. Mysteriously undefined. > How about we leave this as the general Slug list and move all linux > technical questions to a slug-tech list that is for technical problems > only and is regourously enforce? I make this suggestion as I fully > believe you will be forever firefighting and subject to "who appointed > you god" posts if you try and put a tight rein on the Slug list. If a split was ever going to happen, I think the opposite would be preferable. slug@ for Linux stuff, and slug-discuss@ for random discussion. - 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
Re: [SLUG] mail list acceptable use guidelines
Terry Collins wrote: > How about we leave this as the general Slug list and move all linux > technical questions to a slug-tech list that is for technical problems > only and is regourously enforce? I make this suggestion as I fully > believe you will be forever firefighting and subject to "who appointed > you god" posts if you try and put a tight rein on the Slug list. Just a thought, why not appoint someone as god of the lists to enforce such measures as needed. eg. This thread is of topic and I am killing it now, if you wish to further discuss this topic, please feel free to do so off-list. If you maintain posts on this thread you will be cast off to dalnet irc. Kind regards Kevin Waterson -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
Re: [SLUG] mail list acceptable use guidelines
Angus Lees wrote:
Just some general comments.
>
> imo, we are getting way too many off topic threads on slug. I believe
> the quality of this list has dropped in the last year or so, and i
> believe it is from the large number of off topic threads.
This is a side affect of the growth of Slug and (bit of perspective)
this complaint has been heard for the last four years.
So far I know of one list that has been started to get away from the
general list.
In general, the Slug really exists as the Slug list, with a large number
attending the meeting and fewer attending Fests. So the SLUG list really
needs the three factors, which includes "social chit chat" - unless of
course you believe Slug is now too big and should become smaller ?
...snip...
> RATIONALE:
>
> this is a linux users' list. it is meant for discussion about linux
> related topics, and technical queries.
The discussion is what a lot of people object to.
..snip...
> since lots of this is subject to personal opinion, be lenient and work
> off a "punish only on more than one complaint" system.
This is the contentious issue.
...snp.
> linux job ads. must be *linux* jobs, not just general unix sysadmin or
> web/programming jobs. should have "[JOB]" (or similar) in the subject.
I think posting of Linux jobs should be restricted to paid up SLUG
members. Other persons should be pointed to the Linux Australia job
list http://www.linux.org.au/jobs.
>
> non-linux (but nerdy anyway ;) discussion. this includes MS bashing.
NO MS bashing - do it elsewhere
> eg: "cool new gadget that doesn't run linux"
There are clueless nerd lists for this sort of thing.
>
> HTML or "rich text" posts.
Agreed.
..snip
> PENALTIES/PROCEDURE:
This is where you start to get into trouble as some people object to
censorship.
Also keep in mind that a certain amount of discusson is going to be
needed SLUG
...snip..
How about we leave this as the general Slug list and move all linux
technical questions to a slug-tech list that is for technical problems
only and is regourously enforce? I make this suggestion as I fully
believe you will be forever firefighting and subject to "who appointed
you god" posts if you try and put a tight rein on the Slug list.
Netscape comes with a T option = skip this thread, which I admit to
using quite frequently on the Slug list now.
--
Terry Collins {:-)}}} Ph(02) 4627 2186 Fax(02) 4628 7861
email: [EMAIL PROTECTED] www: http://www.woa.com.au
WOA Computer Services
snail: PO Box 1047, Campbelltown, NSW 2560.
"People without trees are like fish without clean water"
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
Re: [SLUG] mail list acceptable use guidelines
Angus Lees <[EMAIL PROTECTED]> > imo, we are getting way too many off topic threads on slug. I believe > the quality of this list has dropped in the last year or so, and i > believe it is from the large number of off topic threads. yep > RESTRICTED: > (ie: allowed, but replies should be off list, unless they are > particularly "worthy") > non-linux (but nerdy anyway ;) discussion. this includes MS bashing. > eg: "hey, i saw the railway indicator boards blue screen!" this (above) should be in the "not allowed" category sure it may be amusing, but the channel 7 dot thing is amusing, it's still completely not related to linux. Constant crapping on about M$ stuff on this list is probably the main thing pissing me off. I am completely not interested in M$ stuff (no matter how stupid the things they do). > eg: "cool new gadget that doesn't run linux" > [or should this be under "allowed" ?] this is definitely ok (ie. "allowed") (cos why doesn't it run linux? we need to know what manufacturers to avoid or lobby etc) > NOT ALLOWED: > (not even a post with "[OT]" in the subject and asking for private > replies. there are more appropriate lists for these) > > windows-only tech-support questions. > eg: "how do i get MSOutlook to read PGP signed email?" > eg: "Does anyone know what runs ITS_EJ.EXE?" > [sorry howard] big agree here! Maybe to also help discourage these questions, include some info on other mailing lists more appropriate. It's not much use just saying "more appropriate lists exist" if people can't find them, they will ask their question anyway reasoning that (a) it's worth a go, (b) I really need to solve this problem, and (c) it'll only piss off a few people. > anything classed as "spam" > > personal flames. (flames, particularly funny ones, are a part of email > life and so should be allowed as part of a normal email > discussion. anything that the recipient gets more than trivially upset > over is not allowed.) > > HTML or "rich text" posts. just bounce all attachments, whatever their type. > irrelevant quoted text or long sigs. (be lenient, since this is > largely personal opinion) > [this needs to be mentioned, but probably not in this category] "netiquette" says 4 lines is enough for a sig. It's tough if you work for a company that adds one of stupid legal disclaimer bullshit sigs on all emails (I'm tempted to add here "use a private email account or find a better company to work for" but that sounds a bit arrogant). > PENALTIES/PROCEDURE: > > if someone is caught breaking these, send them a *private* message > saying this is inappropriate and pointing them at wherever these > guidelines can be read. don't be too harsh on a first offence ;) > > if they disagree with your interpretation of these guidelines, > something should probably be mentioned on the list, so the point can > be clarified (or adjusted to fit future list demographics). > > if someone repeatedly ignores these guidelines, complaints should be > made to whomever the listmaster is, and the listmaster (after > considering the list guidelines rationale) can block further posts > from that address (or something). > [or should complaints go to the list, so everyone knows whats happening?] maybe repeat offenders (within a certain timeframe) should be put on a list of people who can't post without manual approval? Probably (a) a hassle for the list maintainers, and (b) pointless anyway with free web email accounts etc. Dave. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
[SLUG] mail list acceptable use guidelines
imo, we are getting way too many off topic threads on slug. I believe the quality of this list has dropped in the last year or so, and i believe it is from the large number of off topic threads. i'd like to come up with some rough guidelines about what is or isn't allowed on the list. can everyone modify this list, until we get something we agree on. if people think there shouldn't be such a list of guidelines, then please voice that opinion too. if a particular point can't be decided on, i suggest we remove it, rather than spend weeks negotiating something we aren't unanimously in favour of anyway. jeff, once decided on - can we put this in a prominent place on the slug web pages. RATIONALE: this is a linux users' list. it is meant for discussion about linux related topics, and technical queries. posts that would be of interest to the linux community are also allowed, but replies should be moved off the list, unless they add something new to the discussion and are also of interest to the linux community. since lots of this is subject to personal opinion, be lenient and work off a "punish only on more than one complaint" system. ALLOWED: questions about linux. eg: "how do i setup a linux firewall?" eg: "how do i allow windows NT to login to my linux-samba PDC?" linux discussions. eg: "what do the different linux distributions have to offer?" eg: "i just started using lbdb, and its cool." eg: "interesting linux article: " RESTRICTED: (ie: allowed, but replies should be off list, unless they are particularly "worthy") linux job ads. must be *linux* jobs, not just general unix sysadmin or web/programming jobs. should have "[JOB]" (or similar) in the subject. 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" ?] NOT ALLOWED: (not even a post with "[OT]" in the subject and asking for private replies. there are more appropriate lists for these) windows-only tech-support questions. eg: "how do i get MSOutlook to read PGP signed email?" eg: "Does anyone know what runs ITS_EJ.EXE?" [sorry howard] anything classed as "spam" personal flames. (flames, particularly funny ones, are a part of email life and so should be allowed as part of a normal email discussion. anything that the recipient gets more than trivially upset over is not allowed.) HTML or "rich text" posts. irrelevant quoted text or long sigs. (be lenient, since this is largely personal opinion) [this needs to be mentioned, but probably not in this category] PENALTIES/PROCEDURE: if someone is caught breaking these, send them a *private* message saying this is inappropriate and pointing them at wherever these guidelines can be read. don't be too harsh on a first offence ;) if they disagree with your interpretation of these guidelines, something should probably be mentioned on the list, so the point can be clarified (or adjusted to fit future list demographics). if someone repeatedly ignores these guidelines, complaints should be made to whomever the listmaster is, and the listmaster (after considering the list guidelines rationale) can block further posts from that address (or something). [or should complaints go to the list, so everyone knows whats happening?] -- - Gus -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
