Code of Conduct: we need one (… in parallel / in addition to HBR)

[Bradley M. Kuhn]

HBR is, ultimately, not a Code of Conduct — it's a useful addendum to a Code
of Conduct.

We need a Code of Conduct (CoC) for the project.  As we start to open up
contributions via so many methods (fediverse, forgejo instance, mailing list)
— inevitably we'll get some folks showing up who are completely new to FOSS
contribution and we'll need the formalization of a CoC to deal with it.  We
don't want it to happen but we're fooling ourselves if we think it never
will.  (Have you seen the Internet lately? 😩)

It's my firmly held belief that a CoC does make tricky and tense community
moments easier because you have a formal process to deal with the situation.

That said, one frustration I have is that CoC's are like technical standards
— they're great because there are so many to chose from.

I'm curious if folks have a particular CoC template that they particularly
like and think would be good for copyleft-next?

I did some poking around and discussion with colleagues well-versed in this
area, and frankly there is no clear standard, and I don't think (other than
the HBR addendum) that we should write our own from scratch.

I'll spend time this weekend reading over CoC recommended templates to see if
one looks a particular good fit, but curious if anyone else has already done
that work.
--
     -- bkuhn, noting: IANAL & TINLA