haveno-dex / .github Goto Github PK

So it's automatically on all repos (https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file#about-default-community-health-files)

...

Apologies for the brand-new account! I just made it for some anonymous dev work now that I’m out of college and may not want contributions to crypto projects to be linked back to me in my country! Hope you understand!

I’m very happy to see that Haveno is getting a Code of Conduct, but am worried that initial implementation of the Contributor Covenant may inadvertently cause friction in the Haveno community and exacerbate the very toxicity we’re trying to avoid. The Contributor Covenant was designed for large, public facing open source projects with full-time non-anonymous developers, like the Linux kernel, or other large projects primarily maintained and used by institutions and teams.

Monero is a unique project. Many of our core developers are anonymous, and usage of the Monero software is legally contentious in many of the places in which it is developed. Likewise, like most cryptocurrencies, Monero is permissionless, often run and used by individuals clandestinely. Monero’s community is broad and heterogeneous, and I worry that implementation of a generic code of conduct like the Contributor Covenant may fail to adequately address the unique needs of this project and open up rifts in the community that could be exploited by bad actors. Already I have seen concerns on forums about what this code of conduct could mean for community-created art, CCS proposals and even cooperation with law enforcement, and the comments on these threads have sadly quickly devolved into toxicity and paranoia.

To that end, I’ve written up a unique Code of Conduct solely for use in Monero projects, which I believe sums up the positive aspects of this community and hopefully achieves the stated goals of the Contributor Covenant without causing friction and infighting that could be exploited by bad actors.

I would love to hear feedback and would be happy to open a pull request with this document if that would facilitate comment! I know the code of conduct in this repo is new, so now seems to be a good time to get it right.

So we have it for all repos

https://github.com/haveno-dex/haveno/blob/master/.github/workflows/label.yml