Carsten Ziegeler wrote:
>
> Stefano Mazzocchi wrote:
> >
> > Ok guys,
> >
> > I'm turned my picky-mode on and I'm going to be a pain in your ass for a
> > while :)
> >
>
> Hmm, I have to find the "turn-off" button somehow.
:)
> > I'm sure all of you will be delighted to hear this :)
>
> Yupp, absolutely. Life would be so boring without it! Really!
well :)
> > 1) let's rename "scratchpad" into "whiteboard"!
> >
> > 2) each cocoon developer has the right to ask for a "whiteboard area"
> > without requiring a votation, thus the directory structure will be as
> > such
> >
> > /src/whiteboard/[area]/
> >
>
> Hm, I'm not sure if this is a good idea. Perhaps it will work, perhaps
> we end up by having even more areas with individual code as everyone
> starts his one area then.
good point.
> > 3) the /whiteboard directory contains an XML file that indicates the
> > 'owner/s' of the area, along with a brief description of what is
> > supposed to do.
> >
>
> +1
>
> > 4) each area contains an 'INSTALL' file that indicates how to install
> > the 'area' on top of Cocoon and try it out.
> >
>
> +1
>
> > What do you think?
> >
>
> I don't believe that renaming the directory, writing an INSTALL doc and
> separating the scratchpad into different areas will really decrease the
> individualism of this area.
yes, good point.
> The main problem is that the components contained in the scratchpad are
> not so easy to install and test. Now the usual procedure is to build
> the normal webapp, "deploy it somehow" and then manually add the
> configuration
> for the scratchpad component you want to look at. Now if you change
> something,
> you propably have to do this all over again. This is very time consuming.
>
> Even worse, for some components you have to change classes from the
> main area. You can't do these changes in the main area for obvious reasons,
> but how can you maintain it in the scratchpad area? Duplicate code?
> I really don't know. So in order to integrate new functionality and to
> share it, it seems much easier to start developing in the main area.
Oh, one doesn't rule the other out.
> Put putting experimental code in the main area will perhaps break the
> application for a period of time, it might be that the interfaces change
> etc.
>
> And another question is, when can things be moved out of the scratchpad?
when the community decides so, after a votation.
> So, now after I have turned around 360 degrees, we could try your proposal
> and see what we end up with. We can then later on still change the rules.
>
> Anyway, I would suggest that we try to minimize the changes until we have
> 2.0.1 out.
yes.
Ok, I'll try to come up with 'rules for somewhat-evolutionaries' real
soon.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
