[ccan] CCAN and Google Summer of Code

[Adam Kennedy]

If we're talking the mirror structure, at the moment I'm assuming it
will probably be vaguely CPAN-derived...

mirror.json (mirror list, repository path auto-discovery and
validation, see Mirror::YAML on CPAN for the concept)
mirror.yml (potentially in multuple formats)
index/
index/junkcode.json
index/junkcode.json.gz
index/junkcode.sqlite (index available in multiple formats, potentially)
index/stable.json (indexes for multiple levels of sanity)
author/R/RU/RUSTY/
author/R/RU/RUSTY/release-1.00.tar.gz
tools/maybe???

Please note this is (obviously) COMPLETELY different to the repository
structure we currently have, where the repo serves as BOTH the
development environment and the release environment.

The structure above assumes the move to the model that separates
development (anywhere)  ==>  CAUSE  ==>   Mirror Master.

Obviously, this is a much bigger step that just reorganising the repo
directories.

For now, I'm happy to leave the repository with what it has, because I
don't want to interfere with what currently works.

Adam K

2008/5/7 Rusty Russell <rusty at rustcorp.com.au>:
> On Wednesday 07 May 2008 12:51:29 dinesh g wrote:
>  > Hi Rusty,
>  >       As number of modules in the repository evolve, is directory structure
>  > for those modules is going to change? Basically i want to ask, is current
>  > directory structure is going to change for modules?
>
>  I think they will change, Adam certainly wanted to shuffle things around.
>  Although the presentation in the repository is not necessarily the
>  presentation on the mirror or web pages.
>
>  Adam, how about top-level ccan/ junkcode/ and tools/ dirs for a start?
>
>  Cheers,
>  Rusty.
>