Infrastructure
  1. Infrastructure
  2. INFRA-5631

Move Apache Roller to the Apache CMS and/or svnpubsub

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: Initial Clearing
    • Component/s: CMS
    • Labels:
      None

      Description

      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

        Activity

        Hide
        Glen Mazza added a comment -
        Looks nice! Many thanks.
        Show
        Glen Mazza added a comment - Looks nice! Many thanks.
        Hide
        Joe Schaefer added a comment -
        All set.
        Show
        Joe Schaefer added a comment - All set.
        Hide
        Joe Schaefer added a comment -
        Answer #1: yes that is the correct url.

        Answer #2: only roller committers can publish the site, but I would encourage
        you to experiment with granting all committers write access to your site's sources.

        With that I will now proceed to svnpubsubify your site. Enjoy.

        Show
        Joe Schaefer added a comment - Answer #1: yes that is the correct url. Answer #2: only roller committers can publish the site, but I would encourage you to experiment with granting all committers write access to your site's sources. With that I will now proceed to svnpubsubify your site. Enjoy.
        Hide
        Glen Mazza added a comment -
        OK, staging is fine, thanks! Please publish it, replacing the old roller.apache.org in the process.

        Question #1: in the future, after I commit a change (as I see, http://roller.staging.apache.org/ nicely updates a few seconds later), what is the URL I go to publish it to roller.apache.org? My guess is "https://cms.apache.org/roller/publish" (based on what JSPWiki has)--correct?

        Question #2: When I went to the "https://cms.apache.org/roller/publish" URL (I didn't publish it), it asked for my Apache ID and password under a Realm of "ASF Committers". I'm assuming (hopefully) that only Roller committers (besides Infra people) can publish the Roller website, right, or is it *any* Apache committer who has that permission?
        Show
        Glen Mazza added a comment - OK, staging is fine, thanks! Please publish it, replacing the old roller.apache.org in the process. Question #1: in the future, after I commit a change (as I see, http://roller.staging.apache.org/ nicely updates a few seconds later), what is the URL I go to publish it to roller.apache.org? My guess is " https://cms.apache.org/roller/publish " (based on what JSPWiki has)--correct? Question #2: When I went to the " https://cms.apache.org/roller/publish " URL (I didn't publish it), it asked for my Apache ID and password under a Realm of "ASF Committers". I'm assuming (hopefully) that only Roller committers (besides Infra people) can publish the Roller website, right, or is it *any* Apache committer who has that permission?
        Hide
        Joe Schaefer added a comment -
        Staging builds are working: http://roller.staging.apache.org/
        Let us know when you have things ready for production use.
        Show
        Joe Schaefer added a comment - Staging builds are working: http://roller.staging.apache.org/ Let us know when you have things ready for production use.
        Hide
        Glen Mazza added a comment -
        Show
        Glen Mazza added a comment - Done: http://svn.apache.org/viewvc/roller/cmssite/ Thanks!
        Hide
        Joe Schaefer added a comment -
        The first problem you need to address before I can start making progress on this ticket
        is to ensure your source tree resides within a directory named "trunk". So you probably
        want to reverse trunk/cmssite with cmssite/trunk.
        Show
        Joe Schaefer added a comment - The first problem you need to address before I can start making progress on this ticket is to ensure your source tree resides within a directory named "trunk". So you probably want to reverse trunk/cmssite with cmssite/trunk.
        Hide
        Joe Schaefer added a comment -
        I'll put together a standard CMS staging site for you at http://roller.staging.apache.org/
        for you to work on until you're ready for full publication.
        Show
        Joe Schaefer added a comment - I'll put together a standard CMS staging site for you at http://roller.staging.apache.org/ for you to work on until you're ready for full publication.
        Hide
        Glen Mazza added a comment -
        Hi, I *think* I have a working Apache CMS site for Roller now, it's located here: http://svn.apache.org/viewvc/roller/trunk/cmssite/ . Problem is, when I build it locally and view it from the browser using these instructions: http://apache.org/dev/cmsref.html#local-build , the CSS stylesheets aren't being incorporated in (I'm just seeing the HTML but no formatting). I don't know if that's because local generation won't bring in the formatting (I'm not hosting it on a local Apache server, just viewing the HTML files from a browser), or if there's something wrong with my coding of the site causing that problem.

        Could the above link be temporarily hosted on a staging site (say, roller2.apache.org), so I can better test it out to make sure it's working prior to getting it moved to & replacing our present roller.apache.org?
        Show
        Glen Mazza added a comment - Hi, I *think* I have a working Apache CMS site for Roller now, it's located here: http://svn.apache.org/viewvc/roller/trunk/cmssite/ . Problem is, when I build it locally and view it from the browser using these instructions: http://apache.org/dev/cmsref.html#local-build , the CSS stylesheets aren't being incorporated in (I'm just seeing the HTML but no formatting). I don't know if that's because local generation won't bring in the formatting (I'm not hosting it on a local Apache server, just viewing the HTML files from a browser), or if there's something wrong with my coding of the site causing that problem. Could the above link be temporarily hosted on a staging site (say, roller2.apache.org), so I can better test it out to make sure it's working prior to getting it moved to & replacing our present roller.apache.org?
        Hide
        Joe Schaefer added a comment -
        roller.apache.org looks amenable to a CMS site that uses ant as its underlying build system. You will need to make a few cosmetic modifications to your tree first- see http://www.apache.org/dev/cmsadoption#ant
        for details on the changes needed to convert the incubator main site to the CMS (which also uses ant).

        Confluence as a wiki is unaffected unless you are rsyncing autoexport pages to your roller.apache.org site. If you are not, then no changes are required to continue usage of the cwiki site.
        Show
        Joe Schaefer added a comment - roller.apache.org looks amenable to a CMS site that uses ant as its underlying build system. You will need to make a few cosmetic modifications to your tree first- see http://www.apache.org/dev/cmsadoption#ant for details on the changes needed to convert the incubator main site to the CMS (which also uses ant). Confluence as a wiki is unaffected unless you are rsyncing autoexport pages to your roller.apache.org site. If you are not, then no changes are required to continue usage of the cwiki site.

          People

          • Assignee:
            Joe Schaefer
            Reporter:
            Glen Mazza
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development