-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call the house rules something else #1663
Comments
There is previous discussion on this point at: A concern raised was the language "House Rules" could be elitist. I think it's unusual language and using more common, plain English, would be preferable. I think:
was my contribution, see eg. https://gds.blog.gov.uk/social-media-house-rules/ I don't think we should be following Government trends like this, doing something different would help show our independence. Other Services
|
I've added a PR - #1671 - which adds a couple of different |
WalesOnline uses "house rules", but that links to a "Community Standards" page. I like "Community Standards" as that's kind of what we're getting at – understanding that WDTK is a shared "place" and that we should be respectful of others while "in" it. GitHub uses "Community Guidelines", but I think "Standards" sets the tone in a better way; it implies there are minimums that should be met. |
Linking to #1665 which includes commits to use "Conditions of use". |
“Conditions of use” probably fits our requirements a bit better. We will need to ensure that we don’t break any links against what is already there - as |
Although I tend to use "site rules" when writing to users, conditions of use would also work. |
The BBC's terms of use are written in a way that is fairly easy to understand: https://www.bbc.co.uk/usingthebbc/terms-of-use/ |
Whilst looking at strengthening the language around unacceptable behaviour, there's been a suggestion that we change 'House rules' to 'Conditions of use'.
I'm strongly in favour of changing the name. I tend not to use house rules when talking to users, and prefer to call them 'site rules' instead.
The text was updated successfully, but these errors were encountered: