Noisebridge-discuss-faq

From Noisebridge
(Difference between revisions)
Jump to: navigation, search
(Communication)
(Communication: fullstop.)
(2 intermediate revisions by 2 users not shown)
Line 9: Line 9:
  
 
* Announcing and discussing projects, classes, and events related to Noisebridge.
 
* Announcing and discussing projects, classes, and events related to Noisebridge.
* Inciting responses form the many experienced and knowledgeable regular contributors to the community.
+
* Inciting responses from the many experienced and knowledgeable regular contributors to the community.
 +
* Proposing project or class ideas.
 +
* Asking general questions about things related to Noisebridge, including, classes, the wiki, events.
  
 
=== Appropriate Behavior ===
 
=== Appropriate Behavior ===

Revision as of 22:39, 23 April 2013

Noisebridge Discuss FAQ

Contents

Inspiration over Rules

Communication

The direction of communication is one-to-many. It is up to the poster to consider the many.

Valid reasons for making posts to Noisebridge discuss include

  • Announcing and discussing projects, classes, and events related to Noisebridge.
  • Inciting responses from the many experienced and knowledgeable regular contributors to the community.
  • Proposing project or class ideas.
  • Asking general questions about things related to Noisebridge, including, classes, the wiki, events.

Appropriate Behavior

Posts about appropriate behavior, while inevitable, can become quite unnerving to the large number of list recipients. This document serves to minimize such nuisance.

Do not make posts of whines, emotion, drama, accusations, personal complaints, including complaints disguised as questions. Do not retaliate to such posts on the list. Do not start a new thread to complain about other threads or people.

Be considerate.

Posting Style

Posting style in messages intended as responses to other messages can make or break a discussion.

Interleaved Replies

Material quoted from the previous message is attributed to its author and indented with a marker character (usually >). It is trimmed down to just sufficient to provide the context in which the response is made (marking the fact that an edit has been made with one of several common notations, such as: <snip>, [snip], [ ... ], etc.) and the responding text is placed below the quoted material to which it is responding, separated from it by a blank line. (from comp.lang.javascript FAQ)

Bottom Posting

Although less desirable, bottom posting has the advantage over top posting in that chronological order is maintained.

iOS Replies

Bottom posting can be made by selecting the text quote in the reply. See also [Some Quick Interleaved Reply Tips for iOS and Mail.app Users]

Top Posting (don't)

Top posting is a common cause of communication failure and is often a tactic to rudely ruin a discussion.

Personal tools