Hi all guys, I don't see a lot of issues on managing the site with mvn, since svnpubsub is not something that concerns us directly - we just have to create the svn space, then requesting INFRA to enable the svnpubsub for that location.
The only side-effect is, ATM, the deploy procedure <http://markmail.org/message/mdlr3iruo6xzk4ab> But at Maven they are working on an internal plugin to automate all the process <http://markmail.org/message/ryytdbhy534c7z3q> HTH, have a nice day! Simo PS just if you want to see fluido in action at ASF <http://incubator.apache.org/any23/> http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ 2012/2/16 Francesco Chicchiriccò <[email protected]>: > On 16/02/2012 10:29, Emmanuel Lécharny wrote: >> Hi guys, >> >> regarding the web site, I wanted to let you know that the >> Infrastructure Team has decided to modify the way it will handle the >> projects web site publishing. We will have 2 options by the end of >> this year : >> - either we use teh CMS they have implemented (see >> http://www.apache.org/dev/cms.html) >> - or we publish the generated website on svnpubsub >> >> I'm looking for the Infra mail, can't find it right now, but it would >> be a sane idea to migrate to the internal CMS at this point, before >> the site becomes too complex. >> >> Thoughts ? > > Hi Emmanuel, > I must admit that I don't know how the INFRA CMS looks like and that I > am not sure I understand the details about "svnpubsub", but if the > latter means to generate the website via maven site plugin, I have a > little preference for this, especially because this would imply to keep > the site pages in SVN. > > ...and we can profit from a well known "fluido skin", right Simone? :-P > > Anyway, if there are solid reasons for preferring the CMS approach, I am > also available to this. > > Regards. > > -- > Francesco Chicchiriccò > > Apache Cocoon PMC and Apache Syncope PPMC Member > http://people.apache.org/~ilgrosso/ >
