Wicket
  1. Wicket
  2. WICKET-25

Create Wicket web presence on Apache turf

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: site
    • Labels:
      None

      Description

      We don't have much to show on http://incubator.apache.org/wicket which will be our Apach based website while during the incubator. This site has to be published through the use of svn, and has to be static (i.e. generated).

      Until now we used the maven xdoc format for generating the website of Wicket and related projects. This is very cumbersome to make it work, not only because of the format but also due to the intermediate steps necessary to get the thing published. Publishing news, blogs, etc. should be very easy and straightforward in this day and age of Content Management Systems. Heck, there are tons of great php or Java based CMS systems available in general, and only moin moin or confluence at Apache.

      Using one system as our CMS will enable us to create and add content to our website quickly, and will help integrating user content with the website seamlessly.

      In some discussions on our dev list, we decided to use confluence as our CMS and are willing to lend a hand to support confluence as part of the infratax.

      Confluence uses a special plugin to constantly generate a website after an update, so that the site is static, and not backed by a database. This is rather overkill for a project of Wicket's stature, but for a bohemoth like the whole of Apache, it actually makes sense to use a static website rather than a dynamically generated one.

      This issue is used to track the progress of our migration from the maven generated website to a confluence based website. See the subtasks for more information on what is and needs to be done.

        Activity

        Hide
        Upayavira added a comment -

        A few comments:

        1) The reason for using static sites is because of the amount of traffic Apache serves (of the order of 5Tb per month). We simply don't have the servers to have that much traffic be dynamically generated.
        2) It has (reasonably) been proposed to use Confluence to host our website. We need to somehow link this in to the incubator.apache.org/wicket URL. This can be done in one of two ways:
        a) We create a stub site there that has links to the Confluence generated pages
        b) We work out how to get data from Confluence box into SVN, and from there onto incubator.apache.org/wicket

        Show
        Upayavira added a comment - A few comments: 1) The reason for using static sites is because of the amount of traffic Apache serves (of the order of 5Tb per month). We simply don't have the servers to have that much traffic be dynamically generated. 2) It has (reasonably) been proposed to use Confluence to host our website. We need to somehow link this in to the incubator.apache.org/wicket URL. This can be done in one of two ways: a) We create a stub site there that has links to the Confluence generated pages b) We work out how to get data from Confluence box into SVN, and from there onto incubator.apache.org/wicket
        Hide
        Gwyn Evans added a comment -

        There appears to be a discontinuity, in that if we take the incubation requirements strictly, they impose an extra step beyond the requirements for non-incubating projects, specifically the SVN stage.
        Reading http://cwiki.apache.org/confluence/display/CWIKI/Index shows how to use the cwiki space as the main site source, but not via SVN....

        Show
        Gwyn Evans added a comment - There appears to be a discontinuity, in that if we take the incubation requirements strictly, they impose an extra step beyond the requirements for non-incubating projects, specifically the SVN stage. Reading http://cwiki.apache.org/confluence/display/CWIKI/Index shows how to use the cwiki space as the main site source, but not via SVN....
        Hide
        Martijn Dashorst added a comment -

        I've contacted the project lead for openejb on how they do this. Apparently they have things working out great: http://incubator.apache.org/openejb looks great, and is generated using confluence.

        Show
        Martijn Dashorst added a comment - I've contacted the project lead for openejb on how they do this. Apparently they have things working out great: http://incubator.apache.org/openejb looks great, and is generated using confluence.
        Hide
        Upayavira added a comment -

        Really, we are in unchartered territory for the ASF (there is a site-dev@a.o list which is intended for discussing these issues).

        One group want to have all HTML stored in SVN for easy recovery. They want the 'publish' stage to be manual and intentional (i.e. not a cron doing svn up). Another group want it to be easy to edit HTML (eg using Confluence). We are currently trying to work out how to satisfy both parties.

        I do not see any additional requirements for incubating projects. The issues are the same for all ASF projects.

        Show
        Upayavira added a comment - Really, we are in unchartered territory for the ASF (there is a site-dev@a.o list which is intended for discussing these issues). One group want to have all HTML stored in SVN for easy recovery. They want the 'publish' stage to be manual and intentional (i.e. not a cron doing svn up). Another group want it to be easy to edit HTML (eg using Confluence). We are currently trying to work out how to satisfy both parties. I do not see any additional requirements for incubating projects. The issues are the same for all ASF projects.
        Hide
        Martijn Dashorst added a comment -
        Show
        Martijn Dashorst added a comment - we have a site on http://incubator.apache.org/wicket

          People

          • Assignee:
            Unassigned
            Reporter:
            Martijn Dashorst
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development