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

code-of-conduct.md: Add CoC #153

Closed
wants to merge 1 commit into from
Closed

code-of-conduct.md: Add CoC #153

wants to merge 1 commit into from

Conversation

ashcrow
Copy link
Member

@ashcrow ashcrow commented Sep 4, 2019

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 4, 2019
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ashcrow
To complete the pull request process, please assign steveej
You can assign the PR to them by writing /assign @steveej in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ashcrow
Copy link
Member Author

ashcrow commented Sep 4, 2019

/cc @steveej @crawford

@lucab
Copy link
Contributor

lucab commented Sep 4, 2019

I think there is a need for a proper CoC covering OpenShift (+COS) projects.

Major problems with the one in this PR:

  • it is missing any contact points
  • it is missing a designed (and trained) responsible to mediate issues
  • it reads like a quick sed-replace of the original CoreOS one
  • there is no such a thing like "cincinnati events" and "cincinnati entity"

Instead, we'd like to have an umbrella CoC and just point to it, like https://github.com/prometheus/prometheus/blob/master/code-of-conduct.md.

@ashcrow
Copy link
Member Author

ashcrow commented Sep 4, 2019

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 4, 2019
@steveej steveej removed their request for review September 4, 2019 14:38
@ashcrow ashcrow closed this Oct 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing code of conduct file.
3 participants