[ccan] CCAN status update

[Luis Araujo]

Adam Kennedy wrote:
> This somewhat depends on what exactly we're talking about as the 
> "repository".
>
> I am mostly referring to a version control repo that will hold the 
> website content, the indexer and mirroring and etc code, and so on.

Something like PAUSE?
>
> The master CCAN repository should be a simple FTP-mirrorable directory 
> structure containing the release tarballs, with a database of some 
> sort to hold all the metadata and master indexes.
Yes, using FTP would be simple and nice, we could even probably use wget 
for fetching these tarballs too?

Also, what do you mean by database? , postgre, mysql stuff? , if it is 
so, I think that might be too bloated.

>>  
>>> Where each individual author, or collection of authors, choose to store
>>> their modules should not need to be important.
>>>     
>>
>> It's a good point, but I'd like to do this without dropping back to 
>> svn on the main server.
> As I understand decentralized version control (bzr, mercurial, etc) 
> there's no way I can commit to the project?
>
> I have to send every single change to you by email as a patch file?
>
> So lets assume we hit the first scaling threshold of 100 modules and 
> 20-50 developers, exactly how many patch files is that one central 
> person going to need to manage a day?
>
> Or am I seeing this wrong?
>
I would favor using SVN , or if we would like something new and radical, 
probably Git?, this is about the CCAN project repo right? :-)

Though, as I follow the conversation, I can't see clearly the purpose of 
these repositories , you mean, a repository for the CCAN project, a 
repository for the CCAN packages modules , or anything else?

Regards,