The part about the SQLITE code of conduct at the end is unnecessary imo.
With so many highly talented developers coming from marginalized backgrounds -- nonwhite, gay, trans, gender-nonconforming, and/or neuroqueer -- not providing these assurances alienates a prime talent pool.
How will SQLite enforce good behavior of a developer, in perpetuity? Will it remove code contributed 10 years ago by now an open bigot? Is it pertinent only to communication platforms related directly to SQLite? Would it void and null a safety certification or audit done by such a person?
These and other questions come to mind when seeing a CoC of such an undefined form. It is important for the document to answer them. This particular one seems to answer that the CoE is irrelevant to anything as nobody can follow these rules, if read strictly. So why have it at all?
The single sentence list can be interpreted in multiple contradictory ways, which is how we got many religions and even monk orders. It is a code of conflict not ethics.
Most importantly, I would not sign this, even if I were not an atheist. It is incompatible with rules of modern Catholic Church, Islam and probably more. It is probably not compatible in a strict form with whichever branch of christianity the founder follows as well.
Is this any project's policy?
> So why have it at all?
The code of ethics explains why they adopted it. Some customers required suppliers have codes of conduct.
I had no idea harassment and inclusiveness were problems so easy to solve that simply writing a manifesto would suffice. Silly schools for not thinking of it earlier.