This message is sent to the list periodically, as a guide to the creation of efficient and effective messages to other R:Base users and developers. New bullet points are added from time to time, as they as suggested by members. Following are some suggestions for usage and etiquette: * Use a clear subject, that helps a reader determine whether your message is of interest to him or her. * Do not start your subject with any of these words: HELP, SUBSCRIBE, CANCEL * Quote back enough of a preceding message to orient readers to the context. Not all readers retrieve messages with the same frequency you do, nor do their email readers sort messages in the same order as yours. Don't assume everyone will know what message you are responding to. * Do not quote entire long preceding messages with your answer. (Just enough to set the context.) * Attach only very small attachments. When possible, include code samples within the text, not as attachments, since some people reading your message have email readers that cannot interpret the MIME content. * If you want to share large files with the group, direct them to a web page from which they can download it, or ask them to email you directly with personal requests. Do not try to attach files over about 2kb to your message. First of all, it will probably be prevented from being distributed by the list server administration settings, and secondly, if it does get through, you will be clogging lots of email servers, sending that large attachment to hundreds of people, only a few of whom may have a use for it. * Suppress HTML effects from your posts to list servers. Many subscribers are using email readers that cannot make any sense of your HTML. And the colors and fonts and sizes that look great to you on your workstation can be really ugly or even unreadable on other people's workstations. * Replies that are personal comments, and thank yous, and things that are not intended for 300 people to read, should be replied to the original SENDER of the email, not necessarily to [EMAIL PROTECTED] * Do not mark messages to a list server as "high priority." For most people receiving list server messages, direct personal business mail is always a higher priority than bulk mail. As important as your message may seem to you at the time, list servers are, in reality, distributing bulk mail. * The R:Base List server is not the main system to use to report bugs or make requests for new features, although bringing those items up on the List Server is a great way to discuss workarounds for bugs, and the overall usefulness of feature requests. You should know that there is a separate system set up for problem reports for Beta versions of products. Those items should be reported through www.rbase2000.com\rdcc, the R:BASE Developers' Corner Crew. There is a full bug and feature request reporting and tracking system there. That's the fastest and most effective way to get the problems corrected in production releases. Wayne Erickson and the development programming team are not members of the list server, and don't automatically hear about things reported here. You can email files that illustrate problems to [EMAIL PROTECTED]
