Updated: Code of conduct #467
Conversation
Update to bring website in line with the approved OMF Code of Conduct that was adopted in Oct 2023. This also should address current GitHub issue openmodelingfoundation#382
|
In revision line 100, can we have a more generic email address than Charlotte? Better that this goes to the EC officially than to an individual. |
|
I am not opposed to a different address - however, this version and wording is what was approved by the Members in the vote - and there is clarification in the following sentence that the administrative coordinator is point contact. |
You are correct. IIRC, however, there was discussion about having such an email and we opted to keep yours until we had a generic one. If we don't have one, then I guess indeed use yours. If we can get a more generic email, I think we can make the change without consulting the MC. We could ask the EC to approve perhaps. |
|
I just set up conduct@openmodelingfoundation.org to forward to you Charlotte.We could also go shorter like coc@openmodelingfoundation.org but I think I prefer |
|
I sort of like conduct. coc sounds a bit odd and confusing (though perfectly reasonable once you know what it is). |
|
Thank you @alee for the forwarding email address. Do I need to make the associated change to the commit/request (remove my asu email and add that one)? I think I prefer the fuller version - conduct rather than coc |
|
Great, let's go with conduct@openmodelingfoundation.org then - please feel free to adjust the email address in a commit, I will squash all the commits into a single one before merging since this should be a self-contained change. |
|
email updated - pull request should be good to go for checks/review and integration |
email address for reporting code of conduct issues is now conduct@openmodelingfoundation.org Co-authored-by: Allen Lee <alee@users.noreply.github.com>
content: updated OMF Code of Conduct to ratified version from Oct 2023
fix: minor spacing issues and formatting
resolves #382