I think root of the problem is, do we want a site that reflects in-the-trenches Ruby developers' reality, or a site that reflects the Ruby core team's vision?

I think root of the problem is, do we want a site that reflects in-the-trenches Ruby developers' reality, or a site that reflects the Ruby core team's vision? It seems that there's room in the world for both, they are different needs and perhaps trying to satisfy them with one website is a mistake.