I'm not sure I buy this argument. It is a delicate balance between having a coherent vision and collective ownership of a code base. Ideally we'd all be egoless programmers and not take things personally when our architectural decisions are called out. What I've observed in the field is that without an architect driving decisions and keeping things consistent the codebase invariably falls into disarray. Treating it as a collective asset encourages and sometimes accelerates how quickly things fall into disarray.
In my opinion you need a clear owner. The buck must stop somewhere. Ideally it should stop somewhere egoless and not necessarily blameless.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.