Reinhard Poetz wrote:
Daniel Fagerstrom wrote:
<snip/>
We also need to decide where we should put the blocks in the SVN, we could follow Reinhard's approach in the block-builder and moving the trunk/src/blocks/ directory to the top level and inserting a trunk directory:
/cocoon/blocks/forms/trunk/ ...
However IMO we should as a service to our users and ourselves, be a little bit more explicit in how much trust one can put in the various blocks and have something like:
core-blocks supported-blocks unsupported-blocks
Where everything goes to unsupported-blocks and promotion to core and supported is based on votes. OTH, moving the blocks out of trunk and indicating community support level are different concerns so we could do one at a time and I think moving out the blocks should have highest priority.
WDYT?
What about
/cocoon/blocks/core/
/cocoon/blocks/supported/
/cocoon/blocks/unsupported/
+1
I like the structure but which one of the three directories would be the appropriate one for the templating block?ATM it should be part of /cocoon/blocks/unsupported/ graduation to supported or core should be the result of a vote IMO. We could probably replace the original JXTG with the refactored right now if somebody have the time to take care of it (I'm on some tight deadlines, so I can't prommise to do it right now). The internal Java APIs will not be stable for some time, but that shouldn't matter as the JXTG/1.0 template language AFAIK is respected.
As soon as we replace the original JXTG with the templating block, the templating block should IMO be part of /cocoon/blocks/core/.
I also want to emphasize that IMO it is the level of community support that is important, not the level of stability. Something that neither is used nor developed will have a very stable APIs, but it doesn't make it a good choice to start depending on it.
/Daniel
