> More thinking out loud...

> Would it make sense to namespace repos by username?  Currently, if I  
> make a repo "foo", nobody else can make a repo "foo".  This even  
> applies if I want to make my repo private.  I'd have to make a repo  
> ashleymoran-foo instead.  If repos were divided by user, eg

> ashleymo...@patch-tag.com:/r/ashleymoran/foo

> this wouldn't be a problem.  It also means I can have a fork of a repo  
> in my account namespace to use as a remote backup, without having to  
> fudge a name for it.  eg if I'm working on repo "happstack", I don't  
> want to have to call it "ashleymoran-happstack".

> Thinking ahead, this would also make "organisation accounts" more  
> logical.  I've never been fond of GitHubs way of forcing all repos to  
> belong to a human being.  For a company project, I'd prefer their to  
> be nominal account, eg

> ashleymo...@patch-tag.com:/r/patchspace/project1-stable

> and have me and my hundreds of highly-skilled code monkeys* have  
> access (admin or otherwise).  I suppose you can get around this by  
> just signing up a "patchspace" account and authorising users, but I'm  
> a data modelling freak.  I guess the real feature here is the ability  
> for users to administrate other accounts.  Hoping one of my clients  
> will sign up tomorrow (he's already a big darcs fan) so I can test  
> repo joining/sharing on production code then.

> WDYT?

> Please ask for clarification if I don't make sense =)

> Ashley

> * yet to be hired, shaved and trained

> --http://www.patchspace.co.uk/http://www.linkedin.com/in/ashleymoranhtt...