All, What is the future of our website in relation to content management?
With that I mean do we: 1 - continue generating our sites using maven, and put them on Apache turf 2 - use confluence and export it into some static format and put them on Apache turf 3 - use joomla and export it into some static format and put them on Apache turf 4 - use joomla and host it on our servoy server, and use that as our main site (forward from wicket.apache.org)? 5 - some other option? How does Apache look at option 4? Is it just frowned upon, is it something that is explicitly forbidden in the policies/bylaws/rules? Does it conflict with ownership of domains and brand names of Apache)? The problem we face and many Apache projects imho is that the sites are rarely updated with new info and documentation. Having a static site and some elaborate means to update the front page/site, is preventing people from adding content to the site. We have experienced that first hand with our current Wicket setup. This is an issue as we have to decide what to do with the site design Vincent came up with. And of course since we need some web presence in the future. Martijn -- <a href="http://www.thebeststuffintheworld.com/vote_for/wicket";>Vote</a> for <a href="http://www.thebeststuffintheworld.com/stuff/wicket";>Wicket</a> at the <a href="http://www.thebeststuffintheworld.com/";>Best Stuff in the World!</a>
