Noel J. Bergman ha scritto: > Removed the [VOTE] since this is discussion. > >>> 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? > > OK. And an agreement before we publish? Not sure that we'll need formal > votes, but until we establish some pattern (and perhaps boilerplate), we'll > want to agree before committing the feed, right?
We always published website edits/updates using CTR. I changed the xml files, built, commit, updated. For major changes I asked a review before the last "svn up", but for news and similar things I always did a single step. We trust each other and if something is wrong can be fixed in few hours by reverting it after the review has been done. >> Then the svn is mainly for backup/disaster management > > Uh ... the CWIKI isn't supposed to be exposed to the public. The public > goes to static pages, which were moved to the site from SVN. Did I > misunderstand you? Yes you misunderstood. I never intend to expose CWIKI to public. I simply say that autoexport at every change directly to the website will work and that we can commit the exported site from time to time because the svn repository will be our backup and disaster management. If one day both CWIKI and WWW get lost the infra team will have to take the svn content to republish our website without talking with us. > I'm still expecting a detailed process, unless you're just agreeing with the > basic outline above. > > --- Noel If you know what the "auto export" plugin for confluence is this should be clear enough, otherwise just ask what step I should detail. Stefano
