Searching \ for 'Myke Manners and PICLIST Etiquette' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: massmind.org/techref/microchip/devices.htm?key=pic
Search entire site for: 'Myke Manners and PICLIST Etiquette'.

Truncated match.
PICList Thread
'Myke Manners and PICLIST Etiquette'
1997\09\02@125440 by myke predko

flavicon
face
Hi Folks,

I'm finally getting around to doing a web page for myself and in it I'm
referencing the List.  I wanted to put in just a few rules for posting to
the list and like anything I do, it became a huge undertaking.

I'm posting my List Etiquette rules here for everybody peruse and comment
upon or add.  When I set up my web page, these rules of etiquette will be
placed before the instructions on subscribing (as is implied in this cut and
paste):

>Subscribing to the PICLIST
>
>The PICLIST is a very busy listserver - over 100 messages per day is not
>unheard of. Occasionally discussion can get off topic and become somewhat
>heated. To avoid problems and becoming innundated with messages suggesting
that >your ancestors skipped an evolutionary step, there are a few informal
rules of >PICLIST "netiquette" you should be aware of:
>
>   1.Don't subscribe to the List and then immediately start sending questions
>     to the List. Instead, wait a day or so to get the hang of how messages
are
>     sent and replied to on the List and get a "feel" for the best way of
>     asking questions.
>
>   2.If you are changing the "Subject" line of a post, please reference the
>     previous topic (ie put in "was: '...'"). This will help others keep track
>     of the conversation.
>
>   3.When replying to a previous post, try to minimize how much of the
previous
{Quote hidden}

what is
{Quote hidden}

requesting
{Quote hidden}

upon
>     yourself. If you feel it is appropriate to send an off topic message, put
>     "[OT]" in the subject line, some members of the list use mail filters and
>     this will allow them to ignore the off topic posts automagically.
>
>  10.Posts referencing Pirate sites or sources of "cracked" or "hacked"
>     software is not apporiate and may be illegal. If you are not sure if it
>     is okay to post the latest software you've found on the 'Net, then DON'T
>     until you have checked with the owners of the software and gotten their
>     permission. It would also be a good idea to indicate in your post that
you
{Quote hidden}

your
>     posts and legitimate questions ignored in the future by others on the
list
{Quote hidden}

signing
>off the list as well as instructions on how to access
>more advanced functions.
>
>To sign off the list, send a note to the same address
(.....listservKILLspamspam@spam@mitmva.mit.edu)
>with the message:
>
>  signoff piclist
>
>Once you have subscribed to the PICLIST, you will begin receiving mail from
>piclistspamKILLspammitmva.mit.edu notes can be sent to this
>address directly or can be replied to directly from your mailer.

myke

"One must invoke enough raw truth to punch a hole in the world" - Darl Af

1997\09\02@133058 by Eric van Es

flavicon
face
Hiya Myke!

I added a few things I thought relevant. (Sorry for posting your entire
message! :=))

myke predko wrote:

{Quote hidden}

track
> >     of the conversation.
> >
> >   3.When replying to a previous post, try to minimize how much of the
> >     previous
> >     note is copied in your note and maximize the relevance to your reply.
This
> >     is not to say that none of the message should be copied or referenced.
> >     There is a very fine balance between having too much and too little. The
> >     sender of the note you are replying to should be referenced (with their
> >     ID).
> >
> >     My rule of thumb is, if the original question is less than ten lines, I
> >     copy it all. If it is longer, then I cut it down (identifying what was
cut
> >     out with a "SNIP" Message), leaving just the question and any relevent
> >     information.
> >
> >   4.If you have a program that doesn't work, please don't copy the entire
> >     source into a note and then post it to the List. As soon as I see a note
> >     like this I just delete it and go on to the next one (and I suspect that
> >     I'm not the only one).
> >
       Ask first and them (maybe) send your code. Or keep it short.

> >     People on the list are more than happy and willing to answer specific
> >     questions, but simply putting complete source code in the note and
asking
> >     a question like "Why won't the LCD Display anything" really isn't useful
> >     for anybody. Instead, try to isolate the failing code and describe
> >     what is
> >     actually happening along with what you want to happen. If you do this,
> >     chances are you will get an answer literally within minutes.

       Your code is useless to the piclisters if they don't know your hardware
setup.
       Ie: My keyboard and yours work differently, so do my display.
> >
> >   5.You may find a totally awesome and appropriate web page and want to
share
> >     it with the list. Please make it easier on the people in the list to cut
> >     and paste the URL by putting it on a line all by itself in the format:
> >
> >     http://www.awesome-pic-page.com
> >
> >   6.If you have a new application, graphic, or whatever you would like to
> >     share with everyone on the List, please don't send it as an attachment
in
{Quote hidden}

just
> >     been sent to the PICLIST and not you personally. Sending a note directly
> >     back to the Spammer gives them your ID.
> >
> >     I know it's frustrating, but if you want to minimize how much you are
> >     bothered in by spammers in the future, ignore all spams.
> >
> >   9.Off topic messages, while tolerated will probably bring lots of abuse
> upon
> >     yourself. If you feel it is appropriate to send an off topic message,
put
> >     "[OT]" in the subject line, some members of the list use mail filters
and
{Quote hidden}

off.
{Quote hidden}

positive
> >          experience for you. Sending a note listing your problem and what
> >          you've done to try to resolve it will be met with a much more
> >          positive response.
> >
> >  12.Lastly, please try to be courteous to all on the PICLIST. Others may not
> >     have your knowledge and experience or they may be sensitive about
> >     different issues. There is a very high level of professionalism (for
lack
> >     of a better word) on this List, please help maintain it.
> >
13.     When a discussion (this usually happens with off topics) eventually
gets so strung out that there is only two people left responinding to
the mails - stop it entirely or go 'private'. You can obtain the other
persons e-mail address from the header of the message - send your
message to him/her and not to the entire list. They would have lost
interest a long time ago.

{Quote hidden}

Hope you don't mind! I thought you wouldn't mind. For the rest of it -
excellent idea. I hope this fixes some kind of etiquette.

~CIAO!

--
Eric van Es               | Cape Town, South Africa
@spam@vanesKILLspamspamilink.nis.za | http://www.nis.za/~vanes
LOOKING FOR TEMPORARY / HOLIDAY ACCOMODATION?
http://www.nis.za/~vanes/accom.htm

1997\09\04@070052 by peter

flavicon
face
myke predko wrote:
>
> Hi Folks,
>
> I'm finally getting around to doing a web page for myself and in it I'm
> referencing the List.  I wanted to put in just a few rules for posting to
> the list and like anything I do, it became a huge undertaking.
>
> I'm posting my List Etiquette rules here for everybody peruse and comment
> upon or add.  When I set up my web page, these rules of etiquette will be
> placed before the instructions on subscribing (as is implied in this cut and
> paste):
snip

Looks fine to me but perhaps (suitably rephrased) a reference to that
antisocial heap of doggie poo left at the end of messages by some mailer
programs (permision granted to send a copy to microsoft)

KILLspampeterKILLspamspamcousens.her.forthnet.gr

1997\09\05@095600 by paulb

flavicon
face
myke predko wrote:

> Hi Folks,

> I wanted to put in just a few rules for posting to the list and like
> anything I do, it became a huge undertaking.

> I'm posting my List Etiquette rules here for everybody peruse and
> comment upon or add.  When I set up my web page, these rules of
> etiquette will be placed before the instructions on subscribing (as is
> implied in this cut and paste):

 Don't ask general questions (unless you REALLY want more discussion
than solution) such as "How do you use the grommit port on the 12C666?".

 If you want a solution to a problem, SPECIFY the problem:

 "I am designing a steam-driven toaster to operate on a 200PSI live
steam line with a DS1234 Peltier Generator.  I propose to use a grommit
port for feedback control, and the 12C666 seems to have the optimum
hardware.  On my trial system, I am finding leakage with pressures over"
... etc.  Real numbers, components and code sections make it practical
for inconsisencies and incompatibilities to be observed and suggestions
made.


 ... Reworded ad lib.

 Cheers,
       Paul B.

More... (looser matching)
- Last day of these posts
- In 1997 , 1998 only
- Today
- New search...