On 2019-03-19 14:52:41 +0100 (+0100), Thierry Carrez wrote:
Jim Rollenhagen wrote:
[...] Of those 3 options, (2) is a community-oriented view (openstack or not openstack), (3) is a developer-oriented view (organized by project teams, which really only matter to developers), and (4) is a user-oriented view (organized by what users are looking for).
This makes sense in general, but we're talking about git repositories and only git repositories.
Who looks for git repositories most often, users or developers? :)
Developers, of course. But developers can easily find their way to the repository that they want to see. While users or first-time developers might get confused by a hierarchy defined after how work is organized rather than the result of that work.
But I get your point... we should definitely not make the hierarchy "weird" for developers and contributors. If (4) really is too alien, maybe (2) is the right trade-off.
To reiterate, the namespaces and repository names in Gerrit/Gitea do not have to 1:1 match their counterparts on external services. We can totally have team-oriented namespaces in OpenDev but functional namespacing in places like GH and BB. But perhaps that too would be confusing? -- Jeremy Stanley