1. 2

      “a) if people really cared enough about this, and it was a hill worth dying on, we’d see outright forks of all the core stuff, under a less constrained editorial process, which were “community” maintained and managed.

      b) the “community” would test the implicit hypothesis that they can do it better than the constrained process Rich implemented (same or better quality, same consistency and backwards compatibility, all with lower latency).”

      This is what I always think. And, if really putting community first, they can use Pieter Hitchens’ Collective Code Construction Contract that they described here. First description I found in Google anyway…