On Fri, Aug 3, 2018 at 11:33 AM, Nelle Varoquaux <nelle.varoqu...@gmail.com> wrote:
I think what matters in code of conduct is community buy-in and the > discussions around it, more than the document itself. > This is a really good point. Though I think a community could still have that discussion around whether and which CoC to adopt, rather than the bike-shedding of the document itself. And the reality is that a small sub-fraction of eh community takes part in the conversation anyway. I'm very much on the fence about whether this thread has been truly helpful, for instance, though it's certainly got me trolling the web reading about the issue -- which I probably would not have if this were simply a: "should we adopt the NumFocos CoC" thread... By off-loading the discussion and writing process to someone else, you are > missing most of the benefits of codes of conducts. > well, when reading about CoCs, it seem a large part of their benefit is not to the existing community, but rather what it projects to the rest of the world, particularly possible new contributors. > This is also the reason why I think codes of conduct should be revisited > regularly. > That is a good idea, yes. I'll note that at least the Contributor Covenant is pretty vague about enforcement: """ All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. """ I'd think refining THAT part for the project may provide the benefits of discussion... -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
