Differences

This shows you the differences between two versions of the page.

--- vikings:communication_robustness_principle [2026/04/12 09:02] – removed - external edit (Unknown date) 127.0.0.1
+++ vikings:communication_robustness_principle [2026/04/13 07:48] (current) – [Branding] removed thum
@@ Line 1: / Line 1: @@
+======= Communication Guidelines =======
+These guidelines are intended for # VIKINGS staff.  Your communication style may differ from these guidelines, and that is fine!  However, as ambassadors of our association, we ask that you apply the following guidelines.  We invite everyone, especially those associated with us, to contribute comments to help improve these guidelines.
+======= Apply the robustness principle / Postel's law =======
+//> Be conservative in what you do, be liberal in what you accept from others.//
+See also:
+  * [[https://www.rfc-editor.org/rfc/rfc760|RFC 760: DoD standard Internet Protocol]]
+  * [[https://en.wikipedia.org/wiki/Robustness_principle|Robustness principle]]
+guidelines.  We invite everyone, especially those associated with us, to contribute comments to help improve these guidelines.
+======= Choosing the right medium =======
+Choose the right medium for the message: use phone for urgent conversations, IRC/chat for quick coordination, and email for decisions, documentation, and external communication.
+====== Email ======
+===== Formatting =====
+==== Use plain text email ====
+A properly written and formatted plain text email works much better across devices and systems. **Use plain text at all times**.
+=== Text mail formatting ===
+Text-based email should not exceed 80 columns per line of text. Consult the documentation of your email client to enable proper line breaks around column 78.
+=== Do not use HTML email ===
+HTML email - even when it is a multipart mail with a corresponding plain/text section - is often unconditionally rejected by mailing lists. The plain/text section of multipart HTML email is generated by email clients and often results in unreadable gunk.
+=== Do not use multipart email ===
+Again, use plain/text email and not some "magic" format.
+When sending patches via email refrain from attaching patches as that makes it impossible to reply to the patch directly.
+===== General hygiene and etiquette =====
+//this section should probably apply to all communication//
+You don't want your emails to have bad breath, do you?
+  * Make sure you write a clear subject line when starting a conversation.
+  * Use proper spelling and grammar.
+  * Use the local spelling of the recipient (e.g. UK vs. US, AT vs DE spelling/use of vocabulary) if this is well within your capabilities.
+  * Say more with less: be efficient, brief and results-oriented without sounding robotic.
+  * Be polite and courteous.
+  * Avoid sarcasm and emotional language in written business communication. Use them only in informal exchanges with well-known colleagues, and never in external communication.
+  * Avoid technical jargon unless you are in a clearly technical conversation with someone who has demonstrated knowledge of the subject.
+  * Stick to the facts, when in doubt mention it clearly.
+  * Avoid expressing personal political opinions. If the topic is relevant, refer to the association's official position.
+  * Before sending, proofread for spelling, grammar, and tone.
+===== Email signatures =====
+Use the standard email signature provided to you.
+You shall not add additional text (confidentiality disclaimers (//why would you!?//), funny quotes, slogans, MOTD's, ASCII art etc.) to your signature, unless this has been signed off by someone responsible for the guidelines.
+Please do not remove (parts of) the signature; certain content is required by law in our current jurisdiction, often for each and every email that leaves our internal systems, so it's better to be safe than sorry.  This may be annoying (to you *and* the recipient) and counterintuitive at times, as some laws can be.  Relying on the template provided to you will ensure that these legal requirements are met at all times.
+===== Carbon copies (Cc) =====
+Trimming Cc lists is considered a bad practice. Replying only to the sender of an email immediately excludes all other people previously involved and defeats the purpose by turning a public discussion into a private conversation.
+===== Top-posting =====
+If you reply to an email do not top-post. It is considered bad form. It also is evil and every time you do that, a cute little kitten dies. It may be the preferred style in most corporate environments, but that does not excuse it as these examples show:
+> A: Because it messes up the order in which people normally read text.
+> Q: Why is top-posting such a bad thing?
+> A: Top-posting.
+> Q: What is the most annoying thing in email?
+> A: No.
+> Q: Should I include quotations after my reply?
+Of course, you can and sometimes should add your own comments at the beginning of the text as a preface and continue inline below.
+See also: http://daringfireball.net/2007/07/on_top
+===== Trim replies =====
+When you reply to an email, trim unneeded content from the email you're replying to. Quoting an entire message is as bad a style as top posting.
+===== Different rules? =====
+If you participate in an external mailing list or similar, please apply the rules applicable there which may differ in detail from our guidelines outlined here.
+====== IRC & other text-based chat systems ======
+  * Assume messages are persistent and public: Treat IRC messages like written records, not casual speech.
+  * Use threads or context: Don't drop short messages without context – make clear what you're referring to.
+  * Respect response times: IRC is not always real-time; don't expect immediate answers.
+  * Keep the same tone standards as in email: the sarcasm and jargon rules apply here too.
+  * Use the right channel: Stay on topic per channel; off-topic discussions belong elsewhere.
+====== Phone ======
+  * Identify yourself immediately: Start the call with your name and organisation (e.g. "This is [Firstname] [Lastname] from [Association]").
+  * Ask if it's a good time: Before diving in, confirm the other person can talk.
+  * Give your full attention: No multitasking – distracted listening is more obvious on the phone than you think.
+  * Summarise at the end: Confirm what was discussed and what the next steps are.
+  * Follow up in writing: For decisions or action items, send a brief written summary after the call.
+  * Consider time zones and availability before calling.