Hello all!
Here’s our new draft of the proposed Code of Condcut for the OCaml community. The link in the original post is updated to reflect the latest version of the draft. Many thanks to everyone for the thoughtful suggestions. After taking into account the feedback we received here and in private, we’ve decided to go with the Coq Community Code of Conduct as our base text.
We’ve retained the section on strained situations from our previous draft. The text is due to @bobot, who wrote it for a previous iteration of the Code of Conduct text. We’d like to make it clear that this part of the text was not derived from contributor covenant. This section was written during the times of covid lockdowns and made a lot of sense to include, with many people having limited contact with the outside world. Thankfully we’re past the lockdown stages at most places, still we believe it’s useful for people to reach out to us in difficult situations even if there isn’t a clear code of conduct violation.
Scope
As mentioned in the document, the Code of Conduct is currently proposed to be enforced at:
- OCaml github org
- discuss.ocaml.org forum
- caml@inria.fr mailing list
- OCaml IRC
and other spaces managed by the OCaml development team and OCaml Software Foundation.
Next steps
Any comments and ideas regarding the text are appreciated. We kindly request everyone to keep the discussions relevant to the proposed text and OCaml community. If there are no strong objections, the Code of Conduct will be enforced in the spaces listed above. The admins and moderators of those spaces have kindly approved to the idea.
We’d very much appreciate more maintainers following suit and implementing the Code of Conduct for their projects. It’s completely up to the maintainers to decide to do so for their projects. The maintainers can also choose to list the contact details of the Code of Conduct committee, at the discretion of the committee members. We will come back with more details on this process soon.
Happy inclusive camling,
@Khady, @mseri, @rjbou, @c-cube, @pitag, @sudha