[ccan] Moving modules to vanity naming?

[Rusty Russell]

On Wed, 3 Nov 2010 11:13:15 am david at lang.hm wrote:
> On Wed, 3 Nov 2010, Rusty Russell wrote:
> 
> > On Wed, 3 Nov 2010 10:39:06 am david at lang.hm wrote:
> >> I think it would be better to group by similar functionality, and within
> >> that grouping add author names.
> >
> > Isn't that simply adding another level of indirection?  I'm really unsure
> > what the popular groups would be, so I figured that by-author was the
> > least-sucky way of side-stepping that.
> >
> > As you allude, we'd still need both since by-functionality makes the
> > namespace issues worse.
> 
> it could be <module>-author rather than a separate directory level.

Hmm, I like that.  And according to the gitolite docs, it's still possible
to use regexes to grant per-maintainer perms.

> >> If I'm browsing through things, having the first-level split be by author
> >> provides (almost) no useful information.
> >
> > That's true, and I find it personally annoying.
> >
> > Yet I hope that we will get thousands of modules.  That means the utility of
> > browsing the git repository will diminish, so I don't believe we should
> > optimize for that case.
> >
> > The website listing won't be by author (at least, the main list), just the
> > actual layout in the repo.
> 
> won't the website suffer the same problem?

Yes, but it's easier to change the website to offer different views than to
wrangle the source layout so I'm less concerned.

Maybe not a FaceBook "Like" buttons on each module, but some "popular
modules" view seems a more practical way to browse.

> don't think of it as browsing git, think of it as getting a tree that's 
> all the modules checked out and browsing through the source files.

When I look at CPAN, I find it hard to imaging drinking from such a
firehose:
	http://www.cpan.org/modules/01modules.index.html

Cheers,
Rusty.