Editing Noisebridge-discuss-faq

Noisebridge Discuss FAQ

== 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 Behaviour, Personal Attacks ===
Posts about appropriate behavior, while inevitable, can become quite unnerving to the large number of list recipients. It's also archived forever on a publicly searchable forum. Noisebridge has a very strong cultural reticence to delete or censor content once posted.

The best place to sort out concerns about personal behaviour at Noisebridge is face-to-face, either with the person you're concerned with, or at our weekly Tuesday meeting. Remember, you can always ask someone to leave and come back to weekly meeting.

It is best not to make posts of an emotional nature, post accusations, personal complaints. That includes complaints disguised as questions. Do not retaliate to such posts on the list (a simple acknowledgement and encouragement to meet at meeting is often best). Do not start a new thread to complain about other threads or people.

Even if your complaint (or defence) is perfectly polite and factual, it is almost inevitable that others' comments will not be.

=== 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 [[http://brooksreview.net/2011/01/email-tips/ 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.