RE: [PHP] PHP RFC # 0001 --- List Etiquette [SOLVED]
[snip] So the summary of my proposal is as follows: 1.) An issue has been identified with the list whereby improper archival will likely lead to repeat questions and unnecessary traffic to the list. 2.) I propose that we discontinue the act of subject modification to indicate a change in status of the issue (SOLVED, ALSO, ANOTHER PROBLEM, etc.) unless a completely different problem is reached or question is asked. This will allow a step-by-step document (of sorts) to be created and made searchable on the web. [/snip] This has been the expected behavior (adding [SOLVED]) for a long time though it does not occur as often as it should. It has been in the NEWBIE GUIDE for a long time and has been a de-facto standard on IT or computer related mailing lists like this for years. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: RE: [PHP] PHP RFC # 0001 --- List Etiquette [SOLVED]
[snip] I have absolutely no objection to using it, but there's nothing de-facto standard about it. [/snip] OK -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: RE: [PHP] PHP RFC # 0001 --- List Etiquette [SOLVED]
Jay Blanchard wrote: [snip] I have absolutely no objection to using it, but there's nothing de-facto standard about it. [/snip] OK Jay, just out of curiosity - you also chose to start a new thread, rather than reply to the old one - why is that? If anything, that is the core issue we should be addressing. /Per Jessen, Zürich -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: RE: RE: [PHP] PHP RFC # 0001 --- List Etiquette [SOLVED]
[snip] Jay, just out of curiosity - you also chose to start a new thread, rather than reply to the old one - why is that? If anything, that is the core issue we should be addressing. [/snip] It is my e-mail client. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] PHP RFC # 0001 --- List Etiquette [SOLVED]
Jay Blanchard wrote: This has been the expected behavior (adding [SOLVED]) for a long time though it does not occur as often as it should. It has been in the NEWBIE GUIDE for a long time and has been a de-facto standard on IT or computer related mailing lists like this for years. I have been on mailing lists such as this since the early 90s - adding [SOLVED] to anything is by far a rare exception, not the rule. Current examples of project-lists where it has not been seen for at least a month: opensuse clamav spamassassin syslinux crm114 ntp rrdtool nut asterisk postfix lvs raid jfs I have absolutely no objection to using it, but there's nothing de-facto standard about it. /Per Jessen, Zürich -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] PHP RFC # 0001 --- List Etiquette [SOLVED]
On Wednesday 28 November 2007, Jay Blanchard wrote: [snip] So the summary of my proposal is as follows: reached or question is asked. This will allow a step-by-step document (of sorts) to be created and made searchable on the web. [/snip] This has been the expected behavior (adding [SOLVED]) for a long time though it does not occur as often as it should. It has been in the NEWBIE GUIDE for a long time and has been a de-facto standard on IT or computer related mailing lists like this for years. It has been the de-facto standard for mail clients to prefix quoted lines with . Please fix your mail client or use a better one! -- Crayon -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] PHP RFC # 0001 --- List Etiquette [SOLVED]
On Thu, 2007-11-29 at 09:24 +0800, Crayon Shin Chan wrote: This has been the expected behavior (adding [SOLVED]) for a long time though it does not occur as often as it should. It has been in the NEWBIE GUIDE for a long time and has been a de-facto standard on IT or computer related mailing lists like this for years. This is OK, as long as you don't go breaking threads or starting a new thread for something like Thanks! I think that the spirit of the post is not around the use of [SOLVED] or not, but around archive integrity and searchability, especially on the known long tedious dead-horse-whipping threads like Best IDE et al. It has been the de-facto standard for mail clients to prefix quoted lines with . Please fix your mail client or use a better one! This bring up another point. Clients like Novell Group(un)Wise (which we use at our institution (I don't because its evil), and many many others don't do a bunch of things that mail clients should, by law, have to do. Some M$ variants of clients don't even do threading at all! (Does gMail?) This IMHO is tantamount to spamming, as it destroys archival integrity and raises my blood pressure. I think that anyone that participates in any list should invest the 20 minutes it may take to download and install a decent mail client (there are plenty of excellent Free (as in Freedom) ones out there - just ask if you need help). For our own project mailing list(s), I have come up with similar rules - and working and living in a bandwidth starved country/continent, these rules have to be enforced quite strictly. The basic rule set can be found here: http://avoir.uwc.ac.za/avoir/index.php?module=wikiaction=wikilinkpagename=MailingListRules Obviously not all of them can be enforced strictly (like the disclaimer one) as some institutions (mine included) add huge HTML disclaimers to all mail on its way out. There are a few things that can be done to make lists more pleasant for everyone. I suggest we try and put a few in place so as to: 1. Primarily save bandwidth 2. Save time 3. Get more useful archives 4. Be able to say STFW with conviction, because we *know* its there! --Paul All Email originating from UWC is covered by disclaimer http://www.uwc.ac.za/portal/public/portal_services/disclaimer.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
