Discuss reporting strategy

[AlannaBurke]

Think about how we can allow people to report harassment or issues within DDI/slack, or if this is something we want to do.

We want to let everyone feel safe, and not all issues may be seen as "CWG-worthy," or folks may need help figuring that out, or knowing where to go.

If we did decide we want to implement reporting, how would this work? A separate team? Someone who can always be contacted? A custom slackbot command that goes to the moderator channel?

I want people to know where they can go when they have an issue.

[gdemet]

I think it makes a lot of sense for DD&I to have its own moderation team and channel-specific rules. CWG is generally "second-tier" support for issues that can't be resolved by individual moderation teams or involve issues that might have impact beyond just the channel.

[AlannaBurke]

@gdemet We are definitely going to have a moderation team and rules, and we've laid out consequences for violating those rules in the channels and whatnot. The question is, what happens if a DDI member comes to us and says "so and so is harrassing me in DM/on twitter/etc." How do we create a safe, quick, easy, confidential way for that person to tell us, and where do we go from there? The moderation guidelines are much more straightforward, in terms of "a moderator observes X behavior and does Y."

[AlannaBurke]

Think about it as a member of DDI - if someone harasses you and a moderator doesn’t see it, what would be an ideal flow for you to report it?

Should this be immediate - ie, slack? Or a google form? Both? Should it be personal or anonymous? Both?

[AlannaBurke]

I think we should have two ways to report: Immediate and personal (Slack) and through a form, with the option to be anonymous. Making the form is easy enough, and we can set up a gmail account for that. How should Slack work? I'd like them to ping the moderator on duty, if we can make that as clear as possible. What if the moderator/slackbot reminded the channel every hour who is on duty? We could also put in the reporting guidelines that if no one is on duty, default to reporting to me.

[cleverington]

@drnikki already has a gmail acct for D&I. I would definitely support having a simple form which includes some general criteria for follow-up and research:

• Time and Date of Occurrence
• Names of parties and witnesses (that they are willing to provide, with notes that no names need to be provided, if necessary)
• Venue of Occurrence (Spoken, Slack, private-Slack, unsolicited PMs, etc.)
• Comments

Something simple and direct seems efficient.

[AlannaBurke]

@drnikki would you mind sharing those creds with me so i could make the form?
@cleverington this makes me wonder if it could be worthwhile to consider setting up google accounts on our domain. just a thought.

[cleverington]

Have to get the domain registered first, but I would probably lean against adding more bloat on the tech-debt side from that level. As it is we've expanded across GitHub, GitHub Pages (both, possibly, in trade for GitLab in the future), Google Drive/Email via a Leadership administrated account, MailChimp, Twitter, and more.

The more software we expand into, the larger the scope of support and, currently, we only truly need a single email address (again, in my opinion). If the group overall thinks we need more collaborative resources....?

[drnikko]

@AlannaBurke if you want to DM me your lastpass email address, I can shoot you creds.

[AlannaBurke]

@drnikki thanks! i'll work on this form later/this weekend