-
Notifications
You must be signed in to change notification settings - Fork 3
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
Ensure code-of-conduct contact email is monitored #65
Comments
Would it be appropriate to also include contact information for the UW Ombud office? I thought I'd seen that included in past event codes of conduct. The idea is to have another contact that is external to the hackweek organizers and eScience. I'm not sure how that might work given participants coming from other institutions to an event at UW. That might actually be a question for the Ombud office. |
Yes, for clarity, we have two codes of conduct!
Here are two examples that go to a google group email address so that more than one person can be on it.
I think we want to switch both of these to |
Thanks for working on this! Agreed we should use Mark and I can work on updating the form. We can revert back to Google forms I think, or use Qualtrics. We'll share an updated link after that. The 2023 icesat-2 CoC version matches what we've been using for at least the past 5 years. It includes Ombuds, Title IX and UCIRO as external-to-us entities. Happy to include any other updates but I think it is good to go. We should confirm all the links and phone numbers are currently up to date. |
Changes are in uwhackweek/jupyterbook-template#175 |
Closed with uwhackweek/jupyterbook-template#175 |
hackweeks-as-a-service/CODE_OF_CONDUCT.md
Lines 61 to 63 in 178171d
For Icesat-2 2023 we used
[email protected]
(https://icesat-2-2023.hackweek.io/CoC.html)Going over both this repository and our event jupyterbook templates I'd like to make sure the correct email contact is listed. I don't believe the old gmail account is still monitored, but not sure if there is a generic one across events we can use?
cc @aaarendt @markweldensmith
The text was updated successfully, but these errors were encountered: