###### tags: `admin` # CoC ### collection * https://gist.github.com/dstansby/6a8a914e5bbae7024525d8219d4d7c63 - https://gist.github.com/tacaswell/a58998ea143a5ed3cb33ef7ea374f4fc Purpose of meeting ------------------ - To decide on a process for selecting CoC for matplotlib So far ------ - Proposed CoC was opened at https://github.com/matplotlib/matplotlib/pull/18538 - Based on the Python Software Foundation CoC - Left open for 2 weeks for comments Feedback -------- - Lots of minor points - Major feedback was (repeating https://github.com/matplotlib/matplotlib/pull/18538#issuecomment-701096244 and paraphrasing): - Consider Jupyter's and nteract's CoC as they have had greater success in inclusion and training re: CoC - Try to resist the urge to word-smith a whole new code of conduct vs. using an existing one. Sort of like security - rolling your own is seldom a wise idea. Going forward -------------- - We at least need to choose a base CoC within development team - Options are: - Python: https://www.python.org/psf/conduct/ - Jupyter: https://github.com/jupyter/governance/blob/master/conduct/code_of_conduct.md - Scipy: https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html (derives from jupyter) - Numpy: https://numpy.org/code-of-conduct/ (derives from scipy) - nteract: https://github.com/nteract/nteract/blob/master/CODE_OF_CONDUCT.md - Django: https://www.djangoproject.com/conduct/ - Open to feedback or not after choosing? Choosing a CoC -------------- ### What is it supposed to accomplish? - clearly describe - expression of conduct we think is appropriate - provide reporting and potentially enforcement mechanisms - thing to point to when need to enforce mechanisms (not arbitrary) - is signpost that we care about these issues ### Who is going to read it? - existing community members who we expect already know the norms - new community members to get oriented to community standards ### What characteristics will be productive? - concise & clear ### where should we add links: * add link to contributing guide * often contributors pointing folks to it ### critical things: * copy we control * clear reporting criteria ### minor tweaks: * enumerate who gets the report/is on the committee * add headings ### enforcement chain enumerate: - private message, public message, time out, banning - ### choices down to * jupyter - potentially educational * covenant - is more of a code - adopt cov but link out to jupyter as supplement * carpentries: https://carpentries.org/ * values - positive version of what we want * code of conduct - actions & enforcement #### resolution * https://www.contributor-covenant.org/version/2/0/code_of_conduct/ * reporting: * - matplotlib@numfocus.org * - (run through NumFocus:) https://numfocus.typeform.com/to/ynjGdT * - escalation is to https://numfocus.org/code-of-conduct