Repos namespaced by user

[Ashley Moran]

Hi

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

ashle...@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

ashle...@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/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran

[thomas hartman]

This seems like a good idea to me. I think I thought about
implementing it this way originally, but it just sort of fell through
the cracks.

Namespaced repos fall fairly low on our to-do queue though, just
because there are a lot of things we want to do.

However -- if any other users ++ this suggestion I will consider it
even more seriously than I currently am.

Particular feelings for (or against), anybody? Chime in :)

On Mar 8, 11:35 am, Ashley Moran <ashley.mo...@patchspace.co.uk>
wrote:

> Hi
>
> 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

[Ashley Moran]

On 10 Mar 2009, at 06:25, thomas hartman wrote:

> Namespaced repos fall fairly low on our to-do queue though, just
> because there are a lot of things we want to do.

That's fair enough, I'm assuming it would not be complex, ignoring the
day-to-day complications, to do this later anyway.

Thanks

[Daniel Dickison]

On Mar 10, 2:25 am, thomas hartman <thomashartm...@googlemail.com>
wrote:

> Namespaced repos fall fairly low on our to-do queue though, just
> because there are a lot of things we want to do.
>
> However -- if any other users ++ this suggestion I will consider it
> even more seriously than I currently am.
>
> Particular feelings for (or against), anybody? Chime in :)

Not to bring up a dead thread, but I just wanted to add my ++ vote for
this. Since darcs "branches" are their own repos, I can see there
being a situation where I'd want to use some trivial repo name that
could easily conflict with somebody else's trivially-named branch.

[Thomas Hartman]

It's not dead ;)

Since my last comment, I have rethought this issue and now getting
namespaces is quite high on the priority queue.

The only thing blocking this is a major release of the repo browser,
which will be not so strongly based on gitit as it is at present, and
will hopefully be a lot easier to use.

Thomas.

--
Thomas Hartman

Darcs hosting: patch-tag.com
Build a webapp with haskell: happstack.com

[Matthew Elder]

agreed, this is something we are definitely looking into. we are trying to make the browsing interface more flexible and useful as well. stay tuned.

--
Need somewhere to put your code? http://patch-tag.com
Want to build a webapp? http://happstack.com

[Ashley Moran]

On 22 Apr 2009, at 06:45, Matthew Elder wrote:

> agreed, this is something we are definitely looking into. we are
> trying to make the browsing interface more flexible and useful as
> well. stay tuned.

Cool - I've been hoping you hadn't abandoned this one.

Cheers
Ashley