A Conversation for Transgressions Procedure for h2g2

[insert more details of why this breaks the rules here]

Post 1

Martin Harper

>> [insert more details of why this breaks the rules here] <<

Obviously the details sent by email and the details posted on site should be identical - might be worth making this explicit.

The 'final decision' version, by contrast, ought to be reasonably extensive, I feel - you'll have had a week to think about it, so I think this is reasonable. Also might mention extenuating circumstances which were considered and judged not extenuating enough.

Also worth including would be a link to the 'Suspension of Researcher X's h2g2 Account' page. I feel that you should allow the researcher to provide a forwarding email and/or website address (provided both obey the house rules) if they desire so that people can continue to get in touch.

I'm more divided on whether allowing the banned researcher to leave a final message would be worthwhile. It would be a nice courtesy, but I can see that it could be abused. (and offensive parting shots would of course be in breach of the house rules). Perhaps something to make available at the discretion (ick) of the editors?


[insert more details of why this breaks the rules here]

Post 2

Martin Harper

ahh - my bad - misread the 'final decision' bit. I mean to say, in that case, that the personal space should not be hidden, but instead simply add a line to the top of the entry 'Researcher X has been banned for life from h2g2', and a link to the entry. I don't think there's anything to be gained from hiding the home space, unless

A) the researcher requests it be hidden
B) it is against the house rules/terms
C) there are 'exceptional circumstances'


[insert more details of why this breaks the rules here]

Post 3

Dancer (put your advert here)

Yap, I also don't think it is necessery, It might even help if it is not hidden, so that researchers who don't know the researcher in question may go and look and investigate. Kind of a network of smiley - geeky Private Ies.

smiley - hsif
Dancer


[insert more details of why this breaks the rules here]

Post 4

The H2G2 Editors

"Obviously the details sent by email and the details posted on site should be identical - might be worth making this explicit."

Done!

"The 'final decision' version, by contrast, ought to be reasonably extensive, I feel - you'll have had a week to think about it, so I think this is reasonable. Also might mention extenuating circumstances which were considered and judged not extenuating enough."

In cases with much discussion, this is true, so we've added a line "[Insert details of the Editors' reasoning here, if applicable]" to the final decision text. In some cases, like kiddie porn, this won't be required, but in most cases you're right, we'd put this in and it would be relatively comprehensive.

"Also worth including would be a link to the 'Suspension of Researcher X's h2g2 Account' page. I feel that you should allow the researcher to provide a forwarding email and/or website address (provided both obey the house rules) if they desire so that people can continue to get in touch."

OK, that's a good idea, and ideally it would go on the Researcher's Personal Space once they are banned. However, currently the Personal Space is hidden purely as a consequence of the way the system bans people. We're looking into sorting the system out, but until then we will have to stick to hiding pages (though we'll check this technically)... but we can put the contact details on the decision page as a starter (which we've added to the process).

We don't much like the idea of a final message, though. A contact address is perfectly acceptable.


[insert more details of why this breaks the rules here]

Post 5

Martin Harper

Well, I can imagine the case where the banned researcher accepts that they made a mistake, apologises, and says a brief goodbye to hir friends on h2g2, and an invitation to email. In which case, including that final message might help to close the matter - people are unlikely to contest a decision if the person it effects the most has accepted it... also, allowing the banned researcher to say goodbye properly will make them less likely to try and gatecrash back onto h2g2. In many cases it may be unhelpful, but having the option there can't hurt, I reckon.

Thanks for the other changes - as you say, hopefully the procedure will never be needed, but there's no harm in having a safety net... smiley - smiley


[insert more details of why this breaks the rules here]

Post 6

The H2G2 Editors

That's a fair point, but it might not be an idea to promise such a message, as then we'd be obliged to publish messages from those who simply wanted to tell everyone they argued with to take a hike.

We'll add something to the entry, though, to make the point that it's not guaranteed.


[insert more details of why this breaks the rules here]

Post 7

MaW

It looks pretty good to me all told. Plenty of opportunity for misunderstandings, etc. etc. to be rectified... yes, I think it's pretty good.


Key: Complain about this post

[insert more details of why this breaks the rules here]

Write an Entry

"The Hitchhiker's Guide to the Galaxy is a wholly remarkable book. It has been compiled and recompiled many times and under many different editorships. It contains contributions from countless numbers of travellers and researchers."

Write an entry
Read more
https://h2g2.com/entry/A642296/conversation/view/F78003/T145317
h2g2.com
crawl=CC-MAIN-2019-47
21868
application/http; msgtype=response
sha1:3G3BGOSNIHELDXXHWFRELABVXDEM3LUD
<urn:uuid:58a68b8a-e841-402d-9011-6f68d2498d62>
2019-11-22T02:47:20Z
104.25.214.14
text/html
sha1:DD34HUR7LCZG2YQ5LTVJRBJCULHPSFD7
<urn:uuid:a144cd75-f34b-453f-a1be-517e8daf4ba1>
https://h2g2.com/entry/A642296/conversation/view/F78003/T145317
response
<urn:uuid:5d53660e-dc75-44a5-a89b-5a32e60f6878>
isPartOf: CC-MAIN-2019-47
publisher: Common Crawl
description: Wide crawl of the web for November 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-5.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/