cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <>
Subject Re: [proposal] Removing the scratchpad
Date Fri, 21 Feb 2003 15:35:13 GMT

Stefano Mazzocchi wrote, On 21/02/2003 16.02:
> The scratchpad was born as a place where things can be worked-on on 
> alpha status, but it because a place where things are dumped and forgotten.
> A scratchpad is against the continuous integration concept. In short, 
> it's an individualistic short-cut but doesn't help the community, nor 
> the project.
> I propose to dump it and to move the code into 'alpha blocks'.
> Each block is currently described into the 'project-info.xml' descriptor 
> and has an attribute that marks it 'alpha' and the build system shows that.
> Of course, that also means that those blocks are marked as such in the 
> properties files and removed from the official distribution. if you want 
> the experimental code, you have to turn it on one by one by yourself 
> (like in compiling the linux kernel, so to speak)
> This will solve several issues we currently have in the build system and 
> things will be much more organic at the end.
> Thoughts?

It makes me think about Avalon Excalibur (*shiver*).

First of all, what do you want to achieve?

If you want code not to be forgotten, this IMO is not going to work. 
Look at excalibur, it's basically all "blocks", or cornerstone. Our 
scratchpad is more lively than those.

Also, how can we make trials with things that are not blocks? Branches?

There is only one thing that I see the need of: a block scratchpad. This 
is a different thing that what you propose.


In this way we can keep scratchpad stuff packaged as blocks but still 
*clearly* marked as scratchpad. I've seen that it's just too easy for 
users to be confused by things that are in the same place. Do you know 
what packages in Excalibur are alpha or not? I don't. A single 
scratchpad space is less indivudualistic than many small projects.

I feel it's wrong to close a space like the scratchpad, and even more to 
make a similar thing that is even more individualistic.

Hence -1

But I'd propose that we make the


And that code that is older than X months is wiped out from it, so that 
cruft doesn't accumulate.

Nicola Ken Barozzi         
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)

View raw message