diff options
Diffstat (limited to 'comms.html')
| -rw-r--r-- | comms.html | 45 |
1 files changed, 0 insertions, 45 deletions
diff --git a/comms.html b/comms.html deleted file mode 100644 index a6cd65e..0000000 --- a/comms.html +++ /dev/null @@ -1,45 +0,0 @@ -<!DOCTYPE html> -<html lang="en"> -<head> - <meta charset="UTF-8" /> - <title>Tips for Communication</title> - <link rel="stylesheet" href="./style.css" /> - <link rel="icon" href="./favicon.ico" sizes="any" /> - <!--link rel="icon" href="./icon.svg" type="image/svg+xml" / --> - <meta name="viewport" content="width=device-width, initial-scale=1.0" /> - <meta name="theme-color" content="#241504" /> - <meta name="color-scheme" content="light dark"> - -</head> -<body> -<header> - <h1><++></h1> -</header> - -<article> - <h1>Tips for Communications</h1> - <p>See also: <a href="/#contact">contact information</a></p> - <p> - These are some general recommendations that I believe make communicating with me, at least, easier and/or more effective, including communication conventions that make my life easier. Please note that what I prefer may not be what others prefer and shall not be treated as a general guideline for communications, although many of these are common in the free software community. - </p> - <ol> - <li>Write a descriptive subject for emails. Do not send emails with an empty subject or no subject header. The subject should be give the receiver a brief idea of what the email is about.</li> - <li>Send complete information. When telling me something or requesting something, please provide complete background information, knowledge required, and other relevant context. This prevents back-and-forth communication along the lines of "and now I need to know ... but you didn't tell me that so can you please give that to me". Providing context defragments conversations which increases efficiency.</li> - <li>When using instant messaging such as IRC, do not split one sentence into multiple messages (unless, of course, if your message exceeds the character limit). Fragmentation reduces readability.</li> - <li>Do not use excessive emojis.</li> - <li>Be direct rather than polite. As the sender, do not use polite expressions like "you did quite well in that presentation" when in reality, the sender believes that the presentation is not "quite well". Direct critique and suggestions are very welcome here. Politeness is acceptable if it does not interfere with honest conveying of information.</li> - <li><a href="./ask.html">Don't ask to ask.</a></li> - <li>Use plain text email. Both hard-wrapped and non-hard-wrapped emails are acceptable. If you do hard-wrap, please wrap at 72 characters for English. Chinese, if hard-wrapped, should be at approximately 36 characters. Non hard-wrapped emails should <a href="https://www.ietf.org/rfc/rfc3676.txt">specify format=flowed according to RFC3676</a>.</li> - <li>Interweave the original message with the response when replying to an email and remove irrelevant parts (i.e. greetings, closings, signatures, etc.) of the quoted original email.</li> - </ol> -</article> - -<footer> - <ul role="list"> - <li><a href="./">Home</a></li> - <li>Runxi Yu</li> - <li><a rel="license" href="./pubdom.html">Public Domain</a></li> - </ul> -</footer> -</body> -</html> |