#960 closed defect (fixed)

Revamp two-strike & friction policy to require much more documentation of events

Reported by: m Owned by: m
Priority: minor Milestone: devhack: reboot
Component: Policy Keywords:
Cc:

Description

Due to the events of the past month, a lot of the pain could have been avoided with consistent documentation about members' complaints about other members or guests, potential warnings and strikes following those complaints, ATLs invoked, moderation action, other incidents of note.

This sucks because I don't want "HR" or whatever name we come up with that may be the moderation team, may be the board, or may be some other name or people to exist solely to just accrue shitlists of people's behaviour. but here we are.

unsure about if this should be public or not. strikes should probably be publicized first with the option to announce that they happened without announcing who they happened on on request & at "HR"s approval. the shitlists should absolutely not be public. probably. maybe even write-only.

there's been lots of issues about folks perceiving the board as not doing anything and strikes being opaque, and this is the overcorrection for that.

Change History (12)

comment:1 by a@…, 12 months ago

under the current policy, first strikes aren't public.

comment:2 by nc@…, 12 months ago

if strikes are public, should there be norms about discussing them? i think most people don't like long, public, all-encompassing discussions about the drama they're in, whether they are the one who recieved the strike or one of the ones who reported the behavior that caused it.

comment:3 by nc@…, 12 months ago

as for the shitlist -- it was brought up the other day that a flat (non-)hierarchy is only possible if people bring up their disputes with each other, and i thought about how the existing friction policy is pretty counter to this. i agree that the shitlist shouldn't be public, so maybe we can ask that you inform someone if you mention them on it? (maybe you can even grep the shitlist for your own name/member ID/etc)?

comment:4 by a@…, 12 months ago

this is one of the discussion topics slated for the next member meeting, the two strikes policy and ATL revision

comment:5 by m, 12 months ago

oh, also clarify whether the board publicizes ATL stuff maybe?

comment:6 by m, 12 months ago

so maybe we can ask that you inform someone if you mention them on it?

this unfortunately raises the barrier to bringing up issues you have with someone else, I'm not particularly ecstatic that folks aren't being confrontational with eachother but I would rather people be communicative to us in private than keep all of their problems to themselves.

comment:7 by nc@…, 12 months ago

oh hmm yeah

comment:9 by m, 12 months ago

Owner: set to m
Status: newassigned

comment:10 by m, 11 months ago

Milestone: reboot

comment:11 by m, 11 months ago

Milestone: reboot/dev/hack: reboot

Milestone renamed

comment:12 by m, 11 months ago

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.