[ruby-talk:12620] The Ruby Way

Thanks for your last post.

Now I understand why this is *not* the way I should reply!

I didn't realize it was bad netiquette and generally inconsiderate to
put replies to posts before the material you are referring to. What
was I thinking?

It somehow never occurred to me that *other* people at *other* times
and *other* contexts might also be reading this stuff. It also somehow
never occurred to me that there was a reason that others were putting
things in a logical, user-friendly order.

Anyway, I will be a good Ruby citizen and practice good netiquette
from now on.  :-)


Ruby Fan Number 3,141,592 wrote:

> As a member of the "Big 8" newsgroups, "The Ruby Way" (of posting) is to
> follow USENET Netiquette when posting to comp.lang.ruby or to the
ruby-talk
> mail list (which is mirrored to comp.lang.ruby).
>
> The following reminder is taken from the comp.lang.ruby Newsgroup FAQ. And
> please note the paragraph that starts "PLEASE NOTE!".
>
> 2.2 Tell me the posting guidelines for comp.lang.ruby.
>
>     (You should also follow these guidelines for the ruby-list mail
>     list, since it is mirrored to comp.lang.ruby.)
>
>     (1) Keep your content relevant and easy to follow. Try to keep
>         your content brief and to the point, but also try to include
>         all relevant information.
>
>         (a) The general format guidelines (aka USENET Netiquette) are
>             matters of common sense and common courtesy that make life
>             easier for 3rd parties to follow along (in real time or
>             when perusing archives):
>
>             - PLEASE NOTE! Include quoted text from previous posts
>               *BEFORE* your responses. And *selectively* quote as much
>               as is relevant.
>             - Use *plain* text; don't use HTML, RTF, or Word. Most
>               mail or newsreader program have an option for this; if
>               yours doesn't, get a (freeware) program or use a
>               web-based service that does.
>             - Include examples from files as *in-line* text; don't
>               use attachments.
>