diff options
Diffstat (limited to 'comms.html')
| -rw-r--r-- | comms.html | 19 |
1 files changed, 6 insertions, 13 deletions
diff --git a/comms.html b/comms.html index 4a7f1fc..5116fab 100644 --- a/comms.html +++ b/comms.html @@ -1,17 +1,17 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en"> <head> - <title>Communication Guidelines</title> - <link rel="stylesheet" href="/style.css" /> + <title>Tips for Communications</title> + <link rel="stylesheet" href="/oldstyle.css" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" /> <meta charset="utf-8" /> </head> <body class="indent"> - <h1>Communication Guidelines</h1> - <p><a href="/contact.html">A few ways to contact me</a></p> + <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. + 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> @@ -20,16 +20,9 @@ <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 36 characters. Non hard-wrapped emails should <a href="https://www.ietf.org/rfc/rfc3676.txt">specify format=flowed as per RFC3676</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> - <p> - Additionally, please: - </p> - <ol> - <li><a href="./wechat.html">Don't use WeChat to contact me</a></li> - <li><a href="./contact.html">Use these instead</a></li> - </ol> <div id="footer"> <hr /> <p><a href="/">Runxi Yu's Website</a></p> |