-
Notifications
You must be signed in to change notification settings - Fork 4
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 wei to CoC -- update discord chat #14
base: main
Are you sure you want to change the base?
Conversation
Why did you set the link as single use? |
To keep reports as anonymous as possible. That way once a complaint is filed, that reporter can see other future complaints. Do we think this is a bad idea? Anything else to consider or try? |
Ah. I don't think we should use discord channel for reporting. The reporter would see whole history of the channel. |
Good point. Come to think of it, the reporter should probably have 1 point of initial contact -- the outside member. Then that outside member should direct it to us 3 on the CoC (assuming it doesn't pertain to us). |
i think the outside member is really there if it pertains to one of us, so someone could report to any of us. That way we can definitely hit our 72 hour mandate. (so all of us are available to receive reports) |
good point |
Geopandas has one Google groups email for reporting that goes to all 3. That is a good model imho. |
Yeah, we already have that as an option. So probably OK just to drop the whole Discord bit. |
From the document yes. I'd keep the channel for internal discussion. |
This PR:
governance
& clear out backlog #12updates the chat channel from gitter to Discord (update Gitter to Discord across ecosystem pysal#1296)