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.

Sign up for GitHub

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

Jump to bottom

Code of Conduct #529

Closed

handrews opened this issue Jan 8, 2018 · 1 comment

Labels

administrative Priority: High

Contributor

handrews commented Jan 8, 2018

We need a written code of conduct. It should reference the relevant IETF code, and include anything we feel that we need here.

In particular, we need some thing around roles:

Definition of what it means to be a project Member, and what behavioral standards Members are held to
Definition of what it means to be a project Collaborator, and what behavioral standards Collaborators are held to
What behavioral standards are expected of all participants

And some things around discussions:

What sort of requirements exist for staying on-topic in an issue
How to bring an end to discussions where it is clear that there will not be consensus (the IETF sets the goal of "rough consensus", acknowledging that sometimes you can't get everyone's buy-in)

I'm going to start this issue off locked until we figure out the best / least likely to explode way to take feedback on it.

handrews added Priority: High administrative labels

json-schema-org locked as too heated and limited conversation to collaborators

Contributor Author

handrews commented May 28, 2022

Closing in favor of json-schema-org/community#162

handrews closed this as completed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.