The sum of all things speaks for itself. We have an excellent product and a written statement about how all current developers are bound by a religious covenant. And no contributors accepted. If you want to create a fork and welcome lots of contributors, then I don't see how the CoC as written would stand. Of course this has to change.
> That is a lot of effort to complain about SQlite's Code of Conduct.
Anyways, given that the super-majority of the blog post was about features and the different directions that sqlite is being pulled in, and the only singular mention of the CoC was a paragraph at the very end of the blog, I don't really see the summarization of the blog post as just about the CoC as honest.