Adds a code of conduct

[MarcSkovMadsen]

Requested in #2891

You can see the latest version of the PR here https://github.com/holoviz/panel/blob/code-of-conduct/CODE_OF_CONDUCT.md.

Todo

• [] Identify and appoint community leaders responsible for (enforcing) the code of conduct.
• [] Take the time to discuss enforcement with trusted members of the community.
• [] Thoroughly read the Enforcement Guidelines section of the document and adapt if necessary
• [] Assign code of conduct email.
• [] Add a link to this document in the HoloViz Discourse FAQ

[jbednar]

Thanks for kickstarting this! Should we maybe do this at the HoloViz.org level rather than Panel? Many issues and discussions cross multiple github repositories and share the common discourse server, gitter, and other forums, so having separate codes of conduct in those different spaces seems unwieldy. Of course, the code should be prominently linked from each site in any case.

[jbednar]

Any suggestions for an appropriate contact method?

[MarcSkovMadsen]

coc@holoviz.org or something similar. But I think it requires forming a code of conduct team/ council.

[MarcSkovMadsen]

Thanks @jbednar . I was thinking the same. I think we should take the time to discuss and set this up. But I also think its important for a project like HoloViz to have a code of conduct. Both as a signal but also the just in case for the day when its needed.

One thought I had was that maybe we could find users interested in shaping/ steering this effort?

[philippjfr]

Very much in favor of this, so thanks for getting this started. I'd like to consult with a few other projects on what the best template for a CoC is before deciding to go with this particular one. Also a strong +1 to ask around in the community if anyone is interested in joining this effort.

[jbednar]

I'm happy with the Pandas approach to the COC, which is to have a mailing list pandas-coc@googlegroups.com and a public declaration of who is on that list. I'd go one further and add a sentence "If your complaint involves anyone who is on this list, please reach out separately to one or more members of the list who have not been involved in the behavior in question". Otherwise I don't see how to raise an issue privately if it involves someone on the COC mailing list. I'd suggest putting the master version of this document in the holoviz/holoviz repo, either copying the same one to all the other repos (via a github action, maybe?) and having a notice to that effect in the file, or else having the CODE_OF_CONDUCT.md simply point back to that master version. Otherwise we'll end up with a huge number of different files to update whenever we have to update the list of council members, across our dozen or so repos.

[philippjfr]

Working on setting up the CoC email address, for now I'd suggest @MarcSkovMadsen, @jbednar and I to be on that list. Will also ask around on the Discourse if anyone else is interested in joining the CoC committee.

[philippjfr]

@MarcSkovMadsen @jbednar and @philippjfr are now on the CoC committee. Future appointees will be discussed at HoloViz meetings, which we will open to the public going forward.

[philippjfr]

Thanks @MarcSkovMadsen for getting the ball rolling.