Need hints for Repository structure

[Masklinn]

On 2 Nov 2009, at 18:38 , Alan Boudreault wrote:
> Sorry Masklinn, I'm not sure to understand the following point:
> "at the interface/ social level but none at the physical level"

You could present your repositories in client-specific pages/groups  
(instead of a flat list of all the repositories in the same hgwebdir  
view), but that's purely presentational, it doesn't have any impact  
(or source) in the structures of the repositories themselves.

Due to their flexibility, DVCS — I think — tend to encourage moving  
social concepts into the social sphere (rather than the technical  
one): DVCS don't have a (technical) notion of "central repository" the  
way CVCS do for instance, but most projects do have some kind of  
foremost/primary repository/source. It's a purely social construct  
(and it could change if need be). Well the view I suggest above is  
just that, not really technical but depending on the way your teams  
work (e.g. teams are client-based or something) it might make sense to  
build keep the concept of client at the social/interface level even  
though as far as the repositories go (the technical level) it doesn't  
really exist anymore.