[ccan] CCAN and Google Summer of Code

[Rusty Russell]

On Wednesday 07 May 2008 15:00:34 Adam Kennedy wrote:
> 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.

I think I'll move the repo around anyway, just for my own clarity.  How we 
extract that information into the mirror is a movable feast (I don't like 
modules by authorship/maintainership, as authorship is a variable, but that 
may be overruled by the "if in doubt, copy CPAN" rule).

Cheers,
Rusty.