Noel J. Bergman ha scritto: > Stefano Bagnara wrote: >> the ASF restricts the use of Confluence; it is used only as an editor, >> then static pages are exported, and served by httpd. > >> This works perfectly for many ASF projects, and I think it would work >> perfectly for us, too. There is no need to provide the pages dynamically >> when we can have them autoexported (being it an rss, a wiki page, or a >> blog). > > So you want to periodically run Confluence to pull the atoms, generate HTML, > publish that to SVN, and update the site from SVN? I just want to be clear > on the process you envision.
The CTR oversight can be done via notifications from confluence to our site-dev list (at the same level of svn notifications), right? Then the svn is mainly for backup/disaster management: a good solution would be to manually update the svn after major changes, or once in a while. THis is only for disaster management. The probability that ASF loose both the exported website and the confluence database at the same time should be very low (IMHO), so I think we can afford the risk for minor edits/news. > I'm actually OK with the above, although I believe that we can (eventually) > do better, and that it would be temporary. What I voted against against is > going off site. Everything's temporary but death :-) Stefano
