Skip to content
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

Add an incident response guidance to handbook #517

Open
2 tasks
benhylau opened this issue Feb 16, 2023 · 3 comments
Open
2 tasks

Add an incident response guidance to handbook #517

benhylau opened this issue Feb 16, 2023 · 3 comments
Assignees
Labels
comms Back office communications tasks governance operations Back office operations tasks

Comments

@benhylau
Copy link
Member

This initial comment is collaborative and open to modification by all.

Task Summary

📅 Due date: N/A
🎯 Success criteria: Add these bits to handbook.

At the moment, we have no official guidance on how to handle public incidents involving staff. There are related items like CoC and Conflict Transformation, but "public incident" fall out of these scopes and we are left to "figure it out" without org-wide shared expectations.

The guidance is to:

  • report incident to Strategy WG
  • use Signal if triage is urgent
  • give sufficient bg context
  • refer to non-violent comms guidance in the process

There may be some bits about how staff should represent Hypha in public spaces.

To Do

  • Add bits to handbook
  • Bring up this new guidance document at All Hands
@benhylau benhylau added the operations Back office operations tasks label Feb 16, 2023
@LexaMichaelides
Copy link
Contributor

What is a 'public incident'? A nasty Twitter fight?

I guess that's part of the work of establishing this sort of guidance.

@tripledoublev tripledoublev added the comms Back office communications tasks label Sep 12, 2023
@tripledoublev
Copy link
Member

Were any guidelines generated?

Curious if there is any update on this

@writerly03
Copy link
Contributor

I think we need some specifications around what kind of incidents this would cover. i.e. it must be a public, negative, and potentially harmful to the co-operative. Then we can create some kind of triage system

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comms Back office communications tasks governance operations Back office operations tasks
Projects
None yet
Development

No branches or pull requests

4 participants