[SUCS Devel] [Git][sucssite/sucs-site][master] MW etiquette overhaul

Imran Hussain imranh at sucs.org
Fri Nov 9 22:11:25 GMT 2018

Just want to say that out of all the code of conducts/etiquette/whatever I've seen recently this is worded really well.

Thanks for doing it welshbyte 


On November 9, 2018 7:22:02 PM UTC, Andrew Price <welshbyte at sucs.org> wrote:
>Andrew Price pushed to branch master at sucssite / sucs-site
>a80ce238 by Andrew Price at 2018-11-09T19:20:45+00:00
>MW etiquette overhaul
>- - - - -
>1 changed file:
>- static/Knowledge/Help/SUCS Services/Using Milliways/Milliways
>static/Knowledge/Help/SUCS Services/Using Milliways/Milliways
>--- a/static/Knowledge/Help/SUCS Services/Using Milliways/Milliways
>+++ b/static/Knowledge/Help/SUCS Services/Using Milliways/Milliways
>@@ -1 +1,63 @@
>-<p>Milliways has existed for a very long time and its regular users
>include members both past and present, as such there is a sense of
>community, and like any community a number of rules of etiquette have
>formed over the years.</p><p>The denizens of Milliways are usually
>polite and helpful to strangers and newcomers, but do expect those that
>wish to hang around to familiarise themselves with <em>"the way
>things are"</em> and play nice.  As with most communities,
>newcomers need to show respect for the existing members and not expect
>the community to immediately adapt to accommodate them. </p><p>So the
>following is an attempt to describe some of the more usual pitfalls
>that a new user may come across. <br /></p><p><strong>Nothing
>Personal</strong></p><p>Milliways is a relaxed and informal
>environment, and as such there is often a lot of joking and messing
>around, a part of this that a newcomer may find difficult at first is
>the way that users will often ridicule and criticise each other,
>themselves, and anything else that catches their attention. If you
>happen to become the target of such comments then do not take it as a
>personal attack, it usually isn't.</p><p><strong>Spelling</strong>
> </p><p>Users are expected to express themselves using full and
>valid English sentences and words, the use of "txt spk" is
>not tolerated, and any bad spellings, abbreviations, and general bad
>use of English will typically result in corrections being offered, or
>scorn poured upon, as appropriate.  Not only does proper use of
>English allow you to make yourself better understood, but it is good
>practice in preparation for the Real World (and "txt spk"
>really isn't any quicker than real English if you are
>practiced).<br /></p><p><strong>Meta-Questions</strong> aka Ask or Ask
>Not, there is no "May I" </p><p>If you have a question
>or something that you require help on, just come straight out and ask
>it, be as specific as you can, no asking "can I ask a
>question?". Ask the actual question and anybody that is able and
>willing to help will do so, if you get no answer its because nobody can
>help you.  Don't repeatedly ask the same question if no one is
>replying - if someone was able to help they would do, asking them over
>and over will just annoy and reduce the chance of someone helping in
>future.</p><p>Don't assume people know exactly what you are talking
>about just because your question is obvious in the context of your
>specific course.  For example, a programming question like
>"how do I do $foo" is less helpful than "how do I do
>$foo in $language".  The former is likely to get you answers
>covering C, Python, Haskell, etc. rather than the language you are
>interested in. </p><p><strong>Flooding the
>Channel </strong></p><p>If you have anything that you wish to
>share with the world (for criticism generally ;) that is more than a
>line or two of text then you should make use of the SUCS website
>utilities of  <a href="http://sucs.org/Tools/ShortURI"
>title="ShortURI" target="_blank">ShortURI </a> and <a
>href="http://sucs.org/Tools/PasteBin" target="_blank">PasteBin</a> as
>appropriate, and just paste the resulting url instead.  this saves
>cluttering up the screens of all of the users.  In the case of
>questions on items of coursework it would be a good idea only to paste
>the section around the actual problem, not your entire answer, as
>anybody can see the result.</p><p><strong>Further
>Reading</strong></p><p>Eric Raymond maintains quite a good (but long)
>document on how to ask questions in a technical forum.  It is
>worth a read if you have time: <a
>\ No newline at end of file
>+Milliways regulars include society members from both past and present,
>and some
>+who just like to use Milliways but have never been part of the
>society. There
>+is a unique sense of community, and you will often find passionate
>debate on
>+all sorts of subjects from programming to politics, plus the odd pun.
>+It can be a little daunting when first joining Milliways as the
>community is so
>+well established, but stick around and get to know how things work and
>+soon find out how to get the most out of Milliways. If you find any
>+that Milliways can be improved, let us know. Milliways is an open
>+project developed by SUCS members since 1992 and it changes regularly!
>+Below are a few guidelines that every user should follow so that
>Milliways can
>+be a place where people want to hang out and tell their friends about.
>+<strong>You're Talking To Humans</strong>
>+It's important to keep in mind that there are real people behind the
>+and that they all have their own backgrounds and experiences, and
>perhaps some
>+of them are even having a bad day. Use good judgement as to your
>+with other users and the power dynamic between you before choosing
>your words,
>+especially when using light hearted banter.
>+<strong>Asking Questions</strong>
>+It is tempting to ask if you can ask a question on Milliways, or if
>anyone is
>+around who knows about a certain subject, but if you have a question
>+something that you require help with, the best thing to do is to ask
>+question straight away. Provide as much context as you can. You may
>have to
>+wait for an answer outside of busy hours and if you do not get an
>answer it can
>+be useful to other users to report back when you've found the answer
>+If the question is likely to be answered with a quick web search, try
>+first to save time. Note that students asking for coursework solutions
>+likely encounter silence but asking very specific questions to help
>+understand the concepts you need is highly encouraged.
>+<strong>Answering Questions</strong>
>+Particularly with newcomers, it's important to appreciate that asking
>+question may be a difficult thing to do. We were all new students and
>new to
>+Milliways at one point. If you think the answer is obvious or simple,
>it's best
>+to keep that to yourself to avoid belittling the asker. Not everybody
>has the
>+same knowledge in their head.
>+<strong>Don't Flood the Talker</strong>
>+If you have anything that you wish to share on Milliways that is more
>than a
>+line or two of text then you should make use of a pastebin, such as
>the <a
>+href="http://sucs.org/Tools/PasteBin" target="_blank">SUCS
>PasteBin</a> and
>+there is also a <a href="http://sucs.org/Tools/ShortURI"
>+target="_blank">SUCS URI shortener</a> for posting very long links
>+flooding, although many long URIs can be shortened greatly just by
>trimming the
>+ad tracking elements from them.
>View it on GitLab:
>View it on GitLab:
>You're receiving this email because of your account on

Imran Hussain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sucs.org/pipermail/devel/attachments/20181109/554d06b4/attachment-0001.html>

More information about the Devel mailing list