Update to Contributor Covenant 3.0#3
Conversation
| minimize harm. | ||
|
|
||
| When an incident does occur, it is important to report it promptly. To report a possible | ||
| violation, email ``leouieda at gmail dot com`` or ``max dot jones at hawaii dot edu``. |
There was a problem hiding this comment.
@leouieda and @maxrjones, just checking if still ok to leave your emails here? Or we can find other folks who might be willing to step up.
There was a problem hiding this comment.
I'm ok with it, but my email is maxjones@hawaii.edu. I'm not sure if the alias used to work, but it doesn't anymore and this wrong version is in a lot of places 😞
There was a problem hiding this comment.
Oof ok, let me change that. Hopefully we didn't miss any reports 😅
There was a problem hiding this comment.
I'm OK with being a point of contact. 👍🏽
|
Any comments on whether to adopt this or make changes? I'll merge this once there's at least 2 approvals, or will ping again by end of April-ish. |
Co-authored-by: Yvonne Fröhlich <94163266+yvonnefroehlich@users.noreply.github.com>
|
Thanks for the quick approvals! I'll give this until end of the week and merge on my Saturday/Sunday if there are no other concerns. |
|
Apparently I don't have write access to this repo, so someone else needs to merge this 😂 |
5 participants
Proposing an update of our code of conduct from Contributor Covenant 2.1 to 3.0 (originally released 28 Jul 2025).
Cc @GenericMappingTools/gmt-team, @GenericMappingTools/pygmt-team. The sections has been reorganized quite a bit, but you can check out the references below for what the main changes are.
References: