Almost all of our end-user communication is now exclusively on the mailing lists. We do have a few 'trickle' posts being made to the forums on the existing jsecurity.org website, but those have reduced quite a bit in the last 6 months.
So now the only time the site is really updated with any level of regularity is when we make some announcement or make a release, both of which don't happen very often. Because of this, I'd like to discuss (again) the possibility of the website being static that one or a few of us update via a tool like Dreamweaver, which does automatic content sync'ing, instead of the convoluted Confluence-to-HTML export mechanism that we were trying to do previously. I think it was a painful process for Allan and he just stopped trying since he didn't have a full day or two to spend on it. I really like the idea that we can totally customize anything we want with HTML tools (however we want) and was never happy with how the Confluence export mechanism worked, especially with having to deal with ASF permissions for site templates, and all that. So, if I personally spend my time working on website setup, I'd like to spend it going this route, pending team consensus. What do you guys think? Les P.S. Why the heck doesn't ASF support Tomcat hosting for its own project websites? It sounds totally bizarre to me that we can't deploy a .war for a dynamic website...
