[Bug-gnubg] Weekly reminder (final version?!)

[Achim Mueller]

I have taken all your suggestions (and shortened it a little, sorry
Jim). Is this one ok for a weekly posting? For my taste it's nearly to
long (people may tend to not reading it).



1. Subscription

You may always change your subscribtion options at
http://mail.gnu.org/mailman/listinfo/bug-gnubg. This is also the place
for unsubscribing.


2. Subject

Please use a meaningfull subject. There is no use in " bug found", 
"gnubg", "help" or "Please help" as subject. If you really want to 
be smart put a 

bug: 
feature request:
position:
documentation:
compiling error:

or any other meaningfull category in front of your own subject.

For example:
  
| Subject: bug: gnubg crashes when loading Snowie .mat file


3. Formatting

Please don't use html e-mails. A few e-mail programs like Outlook
Express send html per default. It' easy to change this in the option
menue. Further information can be found at
http://www.amsat.org/amsat/listserv/express.html


4. Signature

Your signature should be not bigger than four (4) lines and start with a
"-- " (Yes, this are two hyphens (minus signs) followed by a space)

Do *not* include graphics, logos, pictures or other strange images as
part of your signature.

If you qoute text of another posting, it's _not_ necessary to quote his
signature also.


5. Quoting

The object of quoting is to make it possible for a reader to see an
exchange of e-mails as though they were listening to a conversation. The
reader should normally not need to go back and read a previous e-mail to
see what point you are replying to, nor should they need to scroll
backwards and forwards in your e-mail to find the different parties to a
conversation. 

Ideally when responding to someone else's e-mail, you should quote only
enough of that person's e-mail to let the reader know *what* the other
person wrote that you are responding to. Remove any other text that
isn't relevant to your reply. Some topics can develop into threads of 10
or more e-mails and no-one wants to read the same irrelevant portions 10
times while following the thread.

If you are responding to more than one topic in someone else's e-mail,
then quote each of those topics separately and put your responses
immediately below the associated topic. 

Please avoid top quouting and full qouting. What do we mean? A few MS
Windows e-mail programs (like Outlook Express) always quote the original
e-mail in full at the bottom of the reply and put your cursor at the top
when you begin composing a reply. The result is referred to as top
quoting - all the responses come at the top and the reader has to scroll
down to see what it is you are replying to. Failure to remove those
portions of the original e-mail to which you are not replying is
referred to as full quoting. In the worst case, a lengthy exchange of
e-mails could end up with 10 or 15 copies of the original e-mail. Top
quoting and full quoting are some of the most annoying behaviours in
mailing lists. 

With "good" quoting you will greatly enhance the readability of this
list and our liability to help. Here is an example of qouting how it 
should be:

| Adam  wrote:
| 
| > Here is a bunch of text by someone. This was originally a 25 line
| > paragraph, but [snip irrelevant portion]
|
| Now you, as the author, respond to those points, right here.
| If you have more to quote, do so:
|
| > Someone still had a couple more points to which you wanted to
| > reply, so you quote them [but still snip unneded stuff]
|
| and respond to it.
|
| Your sig then typically follows (but DON'T quote Someone's sig,
| unless that is what you are responding to... and if so, you'd better
| make sure that it is relevant to a Lawhead mailing list, or that it
| is a miniscule fraction of your otherwise completely on-topic post.)

When you answer to a posting, please use _always_ the "reply" or "reply
to list" button. This will keep a thread readable like

| ---- original posting A
| --------|-- direct answer to A (B)
| ---------------|-- direct answer to B (C)
| ----------------------|-- direct answer to C
| --------|-- direct answer to A (D)
| ---------------|---direct answer to D

Also write new posts instead of replying to very old posts and change
the subject. This will ensure correct threading.


5. Attachments

No. Don't send attached files to this mailing list if they are bigger
than appr. 10 kb. Exception: You are asked to do so (mostly in a direct
e-mail, very seldom to this mailing list. I.e. it may happen that
someone asks you to send one of your match files.

If you have access to a webpage, put your file on it and send us the
url.


6. Bug reports

Much as the devopers would like to see nothing but praise and
astonishment from the users, bugs do occur and they form one of the main
purposes of this list. A good bug report makes it much easier for a
developer to find and (one hopes) fix a problem. What's needed:

- Operating system you run
- Version of GNU Backgammon
- A short description of the bug
- The occurance (reproducable, sometimes, seldom, once)

You may also use http://savannah.gnu.org/bugs/?group=gnubg for reporting
a bug. If you you are clever (and we know you are) you may search the
page mentioned above or the mailing list archive at
http://mail.gnu.org/archive/html/bug-gnubg/ if your bug already has been
reported and if there is already a solution or workaround.




Ciao

Achim



-- 
achim mueller, anne-frank-str. 25, D-48431 rheine
+49 (0)5971 83767, +49 (0)163 8458340
-------------------------------------------------
pgp/gnupg key: 1024D/5DF3A722 (wwwkeys.de.pgp.net)

signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil