search

NOAA-FIMS / collaborative_workflow

contributors guide to FIMS, managing collaborations
https://noaa-fims.github.io/collaborative_workflow/
4 stars 1 forks source link

establish a Code of Conduct #3

Closed kellijohnson-NOAA closed 2 years ago

kellijohnson-NOAA commented 3 years ago

Problem

No established Code of Conduct for FIMS.

Potential solution

Reference an established Code of Conduct for the FIMS project.

There are many Codes of Conduct out there and, unless necessary, guidance suggests not writing bespoke codes. Ethics.org lays out why organizations should have a code of conduct, Open Source Guides provides links to some examples of Codes of Conduct that are widely used, and GitHub provides a means to add a Code of Conduct to your repository. Some options include

Feel free to edit this comment to include more links.

Tasks

kellijohnson-NOAA commented 3 years ago

Suggestion is to use Contributor Covenant 2.1. 👍 if you agree. I will leave this issue open until December 01, 2021; so, please comment before then.

cmlegault commented 2 years ago

I find the Contributor Covenant 2.1 too focused on enforcement. Everyone in the project is either a Federal Employee or Contractor, so there are already many enforcement actions available/required if the need arises (which I certainly don't expect). My preference is for a Code of Conduct that focuses more on expected behavior, such as the Django or Openscapes ones.

kellijohnson-NOAA commented 2 years ago

@cmlegault thanks for the comments. I am wondering if you will feel the same way if you think FIMS 5 years into the future, where development has slowed down and we are thinking about user support and integrating wish list items from power users that are not on the development team? But perhaps we should worry about the best Code of Conduct for right now with the thought that if the need arises we could vote to change at a later date.

cmlegault commented 2 years ago

@kellijohnson-NOAA Good point. I had not thought that far down the road to when non-NOAA folks would become part of the team making contributions directly. I'm fine with your original suggestion for the Contributor Covenant 2.1 to address this point. Thanks for thinking further ahead than I did.

kellijohnson-NOAA commented 2 years ago

@kristanblackhart-NOAA and @ChristineStawitz-NOAA is there a particular Science and Technology email or other email that we should point people to when they have questions / comments that pertain to topics covered under the Code of Conduct. Much like how FIT has a generic email. But, I am not sure if we want to use the FIT email. I think it is important to have a somewhat neutral party that is willing to provide potentially anonymous information to FIMS leaders when comments are received about the Code of Conduct.

kellijohnson-NOAA commented 2 years ago

The last task remaining in this issue is to decide on how to let people know that FIMS and its underlying projects use the Contributor Covenant Code of Conduct. Should this be on the FIMS landing page, which doesn't exist yet, and/or in every repository? Also, what do we do about updating the version? Contributor Covenant uses semantic versioning with permanent links. Parties that use the Code are not notified when a new version exists. If every repository has a link to the Code I worry about the links becoming out of sink when we agree to adopt a new version or never looking to see if a new version exists.

kellijohnson-NOAA commented 2 years ago

I just found guidance on how to create community files so you don't have to put the file in every repository.