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

feat: add a Contributor Covenant Code of Conduct #35

Closed
wants to merge 1 commit into from

Conversation

bufferoverflow
Copy link
Member

@fmoessbauer
Copy link
Member

Hi @bufferoverflow , thanks for bringing this up. As discussed internally, I prefer to have the CoC on the GitHub Siemens OU (if possible), instead of having one per project. By that we can keep things consistent across all our repos. @jan-kiszka WDYT?

@bufferoverflow
Copy link
Member Author

@fmoessbauer I agree having it at org level is much better. I was not aware that this is possible.

@jan-kiszka
Copy link
Collaborator

Org-level, and projects can override it, just like with the security.md? That would be useful. We need to make sure "inventing" CoC for projects that already have one, e.g. for upstream forks like Linux.

@nejch
Copy link
Member

nejch commented Sep 23, 2024

Org-level, and projects can override it, just like with the security.md? That would be useful. We need to make sure "inventing" CoC for projects that already have one, e.g. for upstream forks like Linux.

@jan-kiszka we copied the approach from the security policy, so yes we have a little Scope section where we mention this (exclude forks and projects with existing CoC). See siemens/.github#17

@fmoessbauer
Copy link
Member

Closing in favor of siemens/.github#17. Anyways, thanks for bringing this up.

@fmoessbauer fmoessbauer deleted the feat/add-code-of-conduct branch September 27, 2024 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants