Open raulk opened 5 years ago
My recommendation would be to just copy it into your org so that you can add contacts to it for remediation that are specific to libp2p
. I’m not sure who is on that reporting email for IPFS but it is probably project specific folks.
It feels odd to reference the IPFS Code of Conduct from libp2p modules, e.g. https://github.com/libp2p/go-libp2p-peerstore#contribute. This is a vestige from when libp2p used to be inside IPFS.
I don't see the libp2p CoC diverging too much from the IPFS one. We do have some peculiarities to cater for around the RFC/specs process, and the heterogeneity of downstream implementations and implementers. However we won't be focusing on that now.
In the meantime, can we promote this CoC to an interplanetary level so that other top-level projects can reference it without causing confusion?