> I think it's time that we switch over from Confluence to the CMS > > http://www.apache.org/dev/cms.html > > Looks like the CMS is going to be SVN regardless >
Something Github adopted for their project wikis. > I'm hoping someone can volunteer to spearhead this; if not, I'll look > into it in a week or so. As I am not an Apache Comitter, you might not count me in on this, but I could assist you in the process, if you like. > > The docs kind of presume a lot of knowledge of some version of Django, > which I certainly don't have. > AFAIK it is about the markup being used for templating. The implementation itself seems to be in PERL -- see the mod-perl reference *sic*. > I'm not quite sure what we'll do about published JavaDocs (and, > potentially, other reports, such as JavaScript/CoffeeScript docs). > Possibly, we'll need to generate those into an SVN folder and check > them into SVN for publishing to the site. As the docs go, one can package them using targz and then publish the archive to the CMS, but I have not read into that any further. > I'm hoping the result will be something faster and easier to maintain, > and more customizable as well. Hm, how about using the maven site plugin? *duck*... Regards, Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
