[ccan] Moving modules to vanity naming?

[david at lang.hm]

I think it would be better to group by similar functionality, and within 
that grouping add author names.

If I'm browsing through things, having the first-level split be by author 
provides (almost) no useful information.

David Lang

On Wed, 3 Nov 2010, Rusty Russell wrote:

> As CCAN grows (slowly!) the problem of name collisions keeps rearing its
> head.  So after some discussion on IRC I think we should switch to
> author-named subdirectories.  I'd like to see if anyone feels strongly
> about it before doing so, however.
>
> How It Would Work
> ----------------
> The modules move one level down, by maintainer, eg:
> 	#include <ccan/rusty/alignof/alignof.h>
>
> The modules themselves won't change, only the #include lines
> (and _info depends printfs.)
>
> Benefits
> --------
> 1) No risk of namespace poaching: I can have my alloc module and you can have
>   yours too.  If someone wants to use both together, they'll have to run
>   namespacize on one (or both).
>
> 2) git commit access to the whole subdir can be granted, so authors get
>   complete control and don't need to ask anyone to create (or delete,
>   rename) modules.
>
> 3) Some extra kudos for authors.
>
> Costs
> -----
> 1) Another sublevel.
>
> 2) Too much vanity, particularly for me as I have seeded the most modules in
>   ccan.
>
> 3) Symlinks or global changes required when module maintainer changes.
>
> If noone strongly objects, I'll make this change at the end of the week.
>
> Thanks,
> Rusty.
> _______________________________________________
> ccan mailing list
> ccan at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/ccan
>