What you're describing (per-developer 'tribes' of code) is valuable - but it's not a community repo, is it? It's just a convenient place to find people.
In general I observe immature projects are owned by a single developer. These change fast, but they're unstable - all it takes is someone getting married, having a kid, changing jobs, etc for code to die and be orphaned. Those are 'beta' software - at your own risk kinda stuff, with a high tolerance for reinventing the wheel, incompatibility, etc.
As projects stabilize they take in more of the community, and more people are involved. They use standard practices, version well, and are reliable.
I am dubious of the value of calling a loosely connected bunch of developers an 'organization'. Speaking as a developer, even if I am working on a lone-gun project, I don't mix my files in with files related to another driver or app. (I'd take that as a sign of someone who wasn't very organized.) So I'd still want a per-project repo, just owned by me.
I'll go with the flow here, but IME a successful community has community standards and is focused on projects, not people.