The only item I found in the sling export so far (which all the exported
spaces have) is -
/www/confluence-exports/SLING/resources/space.css
which looks like the standard CSS from Confluence without any license
info included.
It looks like for images, the pages are just referring back to the
Confluence hosted files instead of copying them, like index.html -
http://cwiki.apache.org/confluence/images/border/border_bottom.gif
So, I think we'd be okay to check-in the files. Guess our
Geronimo/OpenJPA www areas have stale copies of the Confluence images
due to an older autoexport plugin copying them over during the space
export....
-Donald
Bertrand Delacretaz wrote:
On Thu, Oct 8, 2009 at 4:25 PM, Donald Woods <[email protected]> wrote:
Should there be any concern for checking in the images and css files that
the autoexport plugin is pulling from Confluence? There are a lot of images
that get included in the exported space that come directly from the
Confluence installation....
Licensing concerns you mean?
http://sling.apache.org/ is generated from Confluence, using a custom
template, do you think it contains anything that could belong to
Confluence license-wise?
-Bertrand
For Geronimo and OpenJPA, we still rsync the files over and keep custom
logos/graphics in svn (along with backup copies of the custom autoexport
template) and just manually copy them over when they change.
-Donald
Bertrand Delacretaz wrote:
Hi,
On Wed, Oct 7, 2009 at 3:50 PM, Guillaume Nodet <[email protected]> wrote:
...the autoexport confluence plugin exports the web site automatically at
http://cwiki.apache.org/ARIES/
It's actual location is:
/www/confluence-exports/ARIES/
This directory is simply rsynced to the aries web site using the
following cron job:
0 * * * * (/usr/local/bin/rsync -r /www/confluence-exports/ARIES/
/www/incubator.apache.org/aries/)
So I don't think we can put anything in svn unfortunately....
There would be a way to have the website in svn:
1. Let autoexport generate site at /www/confluence-exports/ARIES (or
trigger it)
2. Aries committer rsyncs that folder to their local svn workspace and
reviews
3. Commiter commits, and svnpubsub [1] quickly copies content to live
website (setup by infra)
Compared to the current setup, all the content is in svn, which makes
it easier to post-process or mix that content with generated content
(javadocs etc). The activation to the live site is also very quick,
compared to scheduled currently. The downside is step 2. above.
-Bertrand
[1]
https://svn.apache.org/repos/infra/infrastructure/trunk/projects/svnpubsub/svnpubsub.py
