search

E4S-Project / e4s

E4S for Spack
https://e4s.readthedocs.io
MIT License
30 stars 13 forks source link

Create CODE_OF_CONDUCT.md #61

Closed zbeekman closed 2 years ago

zbeekman commented 2 years ago

Add the Contributor Covenant Code of Conduct

Addresses #14

Feedback welcome.

shahzebsiddiqui commented 2 years ago

so i found according to https://github.com/EthicalSource/contributor_covenant/releases/tag/2.1 they added caste and color in the document.

This is the first sentence

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

zbeekman commented 2 years ago

@shahzebsiddiqui Thanks for the feedback. I'll update the document to match 2.1.

zbeekman commented 2 years ago

@shahzebsiddiqui Take a look at

Also, I think some of us on the ParaTools side were wondering about:

  1. Scope, and
  2. Enforcement

Would the CoC just apply to this repository and interactions of PT personnel with others? Or more broadly to the E4S project?

Also, depending on the scope, we might not have any direct enforcement mechanism available to us (if it's broader than just ParaTools personnel and/or this repository) but we could, presumably, help to file or direct reports/complaints with an appropriate PoC of the entity in question. Thoughts?

shahzebsiddiqui commented 2 years ago

@shahzebsiddiqui Take a look at

Also, I think some of us on the ParaTools side were wondering about:

  1. Scope, and
  2. Enforcement

Would the CoC just apply to this repository and interactions of PT personnel with others? Or more broadly to the E4S project?

Also, depending on the scope, we might not have any direct enforcement mechanism available to us (if it's broader than just ParaTools personnel and/or this repository) but we could, presumably, help to file or direct reports/complaints with an appropriate PoC of the entity in question. Thoughts?

I think the CoC applies to per project but i think you can adopt the same template for all projects within the E4S-Project organization but i think it gives each project the freedom to decide how to plan to lay out the Code of Conduct and perhaps in future you may decide to use a different standard.

shahzebsiddiqui commented 2 years ago

Also, depending on the scope, we might not have any direct enforcement mechanism available to us (if it's broader than just ParaTools personnel and/or this repository) but we could, presumably, help to file or direct reports/complaints with an appropriate PoC of the entity in question. Thoughts?

For now i think Paratools should be the entity that will enforce these rules but in future you may want to consider having a governing body if there are many stakeholders in the E4S project that may potentially contribute back to this project. If E4S is going to be a product that provides commercial support by entity such as Paratools then i think the governing body would be Paratools.

Take a look at https://opensource.guide/leadership-and-governance/. For instance node has a https://github.com/nodejs/node/blob/master/GOVERNANCE.md that outlines how project is operated including a steering committee. Right now this project is not at point where we have a steering committee but i think its something worth looking into. Something to consider @maherou @sameershende