From cristina at coin-or.org Fri May 28 10:15:33 2021 From: cristina at coin-or.org (=?UTF-8?Q?Cristina_Mu=C3=B1oz?=) Date: Fri, 28 May 2021 09:15:33 -0500 Subject: [Coin-discuss] new Code of Conduct Working Group seeking volunteers Message-ID: Hello friends, My name is Cristina. I'm a long-time open source contributor, and relatively new to the COIN-OR community. A few weeks ago I opened an issue ( coin-or/CoinUtils#172 ) about adding a Code of Conduct (CoC) to a COIN-OR repository. Another COIN-OR contributor took this issue to the board, and there was consensus that the Contributor Covenant would be a good starting point, and should be adopted across the organization. If you have any feedback or concerns about COIN-OR adopting the Contributor Covenant as the default CoC, please comment on that issue. While we wait for more feedback about rolling out the Contributor Covenant , I'd like to get a sense of who might be interested in volunteering in a working group dedicated to the enforcement of a prospective CoC, as well as expanding or updating the content in the selected CoC. This is anticipated to be a low-commitment opportunity primarily focused around ensuring that COIN-OR remains a friendly and inclusive community. Volunteers will be added to a mailing list where community members can report CoC violations. These volunteers will then investigate the alleged violations and follow up with the reporter and reported person to communicate remedies.This is all entirely new for COIN-OR, but other open-source organizations have adopted similar practices and have published helpful resources for addressing CoC violations (e.g. handling conflicts of interests, reporting procedures, etc). I found the following guides to be particularly illuminating: - https://www.mozilla.org/en-US/about/governance/policies/participation/reporting - https://www.python.org/psf/conduct/enforcement/ This is all to say that this group won't be starting completely from scratch, and will be able to flexibly craft policies in response to issues as they arise. No prior experience with CoCs or anything else in the above text is required; just a willingness to address community concerns, and the ability to respond within a reasonable time frame. Thanks for reading and please post on this Github Discussion if you'd like to volunteer or have any questions! -------------- next part -------------- An HTML attachment was scrubbed... URL: