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

Update Code of Conduct to v2.1 #1754

Merged
merged 5 commits into from
Feb 15, 2022
Merged

Update Code of Conduct to v2.1 #1754

merged 5 commits into from
Feb 15, 2022

Conversation

seisman
Copy link
Member

@seisman seisman commented Feb 13, 2022

Description of proposed changes

Address #1739.

The original markdown text is available at https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md

Reminders

  • Run make format and make check to make sure the code follows the style guide.
  • Add tests for new features or tests that would have caught the bug that you're fixing.
  • Add new public functions/methods/classes to doc/api/index.rst.
  • Write detailed docstrings for all functions/methods.
  • If wrapping a new module, open a 'Wrap new GMT module' issue and submit reasonably-sized PRs.
  • If adding new functionality, add an example to docstrings or tutorials.

Slash Commands

You can write slash commands (/command) in the first line of a comment to perform
specific operations. Supported slash commands are:

  • /format: automatically format and lint the code
  • /test-gmt-dev: run full tests on the latest GMT development version

@seisman seisman marked this pull request as ready for review February 13, 2022 14:40
@seisman seisman added the documentation Improvements or additions to documentation label Feb 13, 2022
@seisman seisman added this to the 0.6.0 milestone Feb 13, 2022
@maxrjones maxrjones added the final review call This PR requires final review and approval from a second reviewer label Feb 14, 2022
Copy link
Member

@weiji14 weiji14 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @seisman!

Just want to double check though if @leouieda and @PaulWessel are still happy to be listed as contacts? Or we can nominate a new person (e.g. @meghanrjones) as an additional contact.

@PaulWessel
Copy link
Member

I think for pyGMT it makes more sense to have @meghanrjones listed than me.

@maxrjones
Copy link
Member

I can be listed. My SOEST directory page is https://www.soest.hawaii.edu/soestwp/about/directory/meghan-jones/ for people to find out how to get in touch.

@seisman
Copy link
Member Author

seisman commented Feb 15, 2022

I can be listed. My SOEST directory page is soest.hawaii.edu/soestwp/about/directory/meghan-jones for people to find out how to get in touch.

I just removed Paul and added Meghan to the list.

@seisman seisman merged commit c1f1887 into main Feb 15, 2022
@seisman seisman deleted the code-of-conduct branch February 15, 2022 10:40
@seisman seisman removed the final review call This PR requires final review and approval from a second reviewer label Feb 15, 2022
@leouieda
Copy link
Member

I know this is merged to but just wanted to confirm that I'm happy to be listed there as a contact. 👍🏽

sixy6e pushed a commit to sixy6e/pygmt that referenced this pull request Dec 21, 2022
* Update Code of Conduct to v2.1
* Update the badge in README
* List Meghan as a contact
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants