forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bert Van Kets <>
Subject Re: Apache Trove
Date Mon, 09 Dec 2002 20:40:27 GMT
Where do you want to get with this information?  I can see the link between 
this "trove" document and Forrest, but please elaborate.

 From what I read between the lines it would be a great opportunity to use 
the restructuring to get people into Forrest, or to adapt Forrest to 
reflect the structure and make the transition for the projects to Forrest 
as easy as 123.

Do I read you correctly?


At 23:29 8/12/2002 +0100, you wrote:
>Hi all,
>due to the recent and upcoming reorgs in terms of the 
>'federation'/project/subproject structure and the assumed increased 
>difficulty for people finding their way around ASF projects, I have been 
>playing around with a draft 'trove' application, which isn't much more 
>than some XML & XSLT glued together, running on top of Cocoon.
> (warning: data entry hasn't been 
>completed yet)
>This 'app' runs on top of a very free-formed XML document currently:
>   <federation name="XML">
>     <keyword name="XML"/>
>     <site uri=""/>
>     <description>[...]</description>
>     <project name="FOP">
>       <keyword name="XSL-FO"/>
>       <keyword name="Java"/>
>       <site uri=""/>
>     </project>
>   </federation>
>   <project name="BCEL">
>     <site uri=""/>
>     <description>[...]</description>
>     <federation name="Jakarta"/>
>     <keyword name="Java"/>
>   </project>
>   [...]
>and should be maintained by the respective project communities. I already 
>went searching what Gump could offer me in terms of available data, but 
>Gump is for obvious reasons limited to Jakarta and XML (Java) projects. 
>Adding the Gump people to add a 'keyword' element to their descriptors 
>wouldn't cause too much harm, but the problem is that I also store the 
>project hierarchy in my data file, and this is slightly orthogonal to 
>Gump's structure. So adding extra data to Gump's descriptors would help, 
>but not enough and not for everybody (including perl/php/...)
>Another approach might be to store a small trove file per project in the 
>committers cvs module, where assumably everybody has access too, and me 
>aggregating those.
>The (XML) structure being required would be something like:
><project name="">
>   <site uri=""/>
>   <description></description>
>   <keyword name=""/>
>   (<federation name=""/>)
>Projects can contain projects, and can be grouped into 'federations', aka 
>httpd, xml, jakarta and others. I tried to set up the stylesheets to do 
>something meaningful without many strict requirements on the hierarchy of 
>the datafile.
>Anyway, this is just a heads-up. I don't know where I could move it too 
>since it falls a bit in-between projects. The presentation is by no means 
>finished, but should be easy to tweak. I can nurture this thing on my own 
>on my own server, but if other people would be interested in playing 
>along, just gimme a yell.
>Steven Noels                  
>Outerthought - Open Source, Java & XML Competence Support Center
>Read my weblog at    
>stevenn at                stevenn at

View raw message