Unsubscribe
-----Original Message-----
From: RBG7-L [mailto:[EMAIL PROTECTED]
Sent: Friday, July 30, 2004 12:56 PM
To: [EMAIL PROTECTED]
Subject: Welcome to RBG7-L
Welcome to the RBG7-L mailing list.
To post a message to the list, send e-mail to:
[EMAIL PROTECTED]
To unsubscribe from the list, send a message to [EMAIL PROTECTED] with
just "Unsubscribe" (no quotes) in the subject.
[Last updated on: Tuesday, October 01 2002 16:50:28]
RBG7-L is the official list server for application developers and
users of R:BASE 7.0 from R:Base Technologies, Inc. (www.rbase.com)
To post a message to the list:
=====================
In the "To:" field, address your message to: [EMAIL PROTECTED]
In the Subject field, put a short heading the describes the feature
or issue you are writing about.
==============================
Etiquette and Usage Guidelines
==============================
This list server is to be used for ALL productive exchanges between
subscribers to discuss R:BASE issues related to programming,
applications, technical issues and the like. Job solicitation is
permitted as this list is a great source of opportunity to all of its
members.
Behaviors that are NOT acceptable on this list are as follows,but not
limited to:
* Exchanges of subjects that are deemed to be offensive or personal
in ANY way by either RBTI or the list manager.
* Advertising by ANY subscriber related to their personal
organizations or business affiliations. While we invite the
formation of new R:BASE list groups and training classes to help
spread the word about the product, this is not the place to solicit
for recruitment. RBTI will also respect this rule by limiting its
advertisements to periodically posting messages of sales events or
new product releases. We do not intend to use, or have the RBG7 List
used, as a device for SPAM. If anyone wishes to contact RBTI
directly about an event that they are organizing, we will be happy
to construct an official announcement on their behalf.
* The disclosure of ANY information which was intended to be a
private correspondence between two or more individuals who are
members of this list. This is NOT the place to hold spectacles of
personal display, as it is counterproductive to the purpose of the
list, and is not appreciated by the other members. The bottom line
is that if a message was sent privately, it was intended to be so,
and the RBG7 List will not be a billboard for personal disputes.
* Any forms of retaliation or insubordination that is exhibited
against either the list manager, any member of RBTI, or any other
subscriber to this forum. ALL decisions that are made by the list
manager are final, and at his/her discretion, and will NOT be held to
a public vote or petition. If the person who was the recipient of
the list manager's decision would like
to appeal the decision, he/she MUST contact the list manager OR RBTI
privately regarding this issue.
Our goal is to provide a productive and informative environment, for
ANY person wishing to participate, to discuss their R:BASE 7.0
related achievements, experiences, and other information that is
relevant to the R:BASE subject. This forum is open to ALL who abide
by the rules that are in place, which are designed to protect the
rights of the entire group, not just a particular
individual.
=====================
Posting your Messages
=====================
The following suggestions are a guide to the creation of efficient
and effective messages to other R:Base users and developers.
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 are suggested by members. Please review these suggestions for
usage
and etiquette:
* Use "plain text." Suppress HTML effects from your posts to list
servers. Many subscribers are using email readers that cannot make
any sense of your HTML. 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. HTML style settings can
add many kilobytes to the size of your message, and easily can swell
your message size to the point where it will exceed the limits for
this plain text email list server. If you are using MS Outlook
Express, for example, in your contact list, right click on
[EMAIL PROTECTED], select "properties," click the "name" tab, and
put a check in the
box for "send plain text message."
* 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.
Quote 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, do not attach them
to your list server messages. Direct readers to a web page from
which they can download it, or ask them to email you directly -- off
the list -- with personal requests. Large attachments will probably
cause your
message to be blocked by the list server administration settings.
Even 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.
* Never attach an executable file. Most companies' mail servers or
virus checkers will bar your message from being delivered, for fear
it contains a virus.
* 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 let your email client ask for a receipt for mail you post to
a list server.
* 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.
* Use your real name, not a "screen name" or "handle," and use both
your first name and last name in your email "from" settings, (unless
you have a really distinctive name like Razzak, Sami, or Oma.) There
are many people named Dan and Ben and Jim and Mike and Bill on the
list server. Help everyone keep each other straight.
* The RBG7-L 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
mailto:[EMAIL PROTECTED]
We hope you find membership in the RBG7-L list server useful!
