You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2012/12/11 05:05:21 UTC

[jira] [Created] (INFRA-5631) Move Apache Roller to the Apache CMS and/or svnpubsub

Glen Mazza created INFRA-5631:
---------------------------------

             Summary: Move Apache Roller to the Apache CMS and/or svnpubsub
                 Key: INFRA-5631
                 URL: https://issues.apache.org/jira/browse/INFRA-5631
             Project: Infrastructure
          Issue Type: Improvement
      Security Level: public (Regular issues)
            Reporter: Glen Mazza


Hello, I'm with the Apache Roller team.  We've been on the latest "Santa's Naughty List" email sent to the PMC's and would like to rectify that situation.  We have two sites and are unsure which ones are invalid:

1.) The Roller website currently at http://roller.apache.org/ presently hosted at people.apache.org's /www/roller.apache.org, whose documentation source code is stored here:  http://svn.apache.org/viewvc/roller/trunk/site/.  Is this site invalid?  If that's the case, I'd like to move it to the Apache CMS.  I have some experience with Apache CMS due to patches supplied to the incubating Apache JSPWiki project page, but am unsure of the process (i.e., do you guys create a folder structure for me that I subsequently fill up with CMS pages and then tell you guys to activate the website, or do I create a CMS-compatible site within the Roller repository now and then ask your team to switch to it?)

2.) We have a Confluence Wiki at https://cwiki.apache.org/confluence/display/ROLLER/Roller+Wiki.  I guess svnpubsub is best for Confluence; I know Dan Kulp of Apache Camel/Apache CXF has an svnpubsub process for Confluence sites: http://www.dankulp.com/blog/2012/03/svnpubsub-for-confluence-sites/  I guess we can just switch to that without any action from Infrastructure?

Thanks!
Glen

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira