Martijn Dashorst wrote:
On 10/19/06, Upayavira <[EMAIL PROTECTED]> wrote:
Options 1 and 2 are straight-forward within Apache.
Option 3 would be possible, although you would be better asking for
wicket.zones.apache.org (a Solaris zone) and running Joomla there - so
that the source content is stored on Apache hardware.
Then the question is: do we go with 2 or 1 CMS?
Do we go with Confluence or Joomla+Confluence, or do we hook a wiki
module into joomla?
How is the export facilities of confluence, and how can we integrate
it with for instance Woogle? I'd love to have our own Woogle search
engine be integrated with our site (the design already reserved a
place for that).
Option 4 would be difficult - remember that documentation is also part
of the IP that we are creating at Apache, so it needs to be hosted on
ASF hardware. Doing option 4 would almost certainly cause difficulties
upon an attempt to graduate.
Would this mean that the content writers also need to file an ICLA?
This hasn't happened yet with the import we've done for our Wiki.
Regarding the documentation: not all documentation is part of the
Wicket distribution. For instance we don't export the wiki and ship it
with Wicket. As such I *could* defend the position that the
documentation can be hosted outside. Not that I would like it to
though.
So I think the path of least resistence is either option 2 or 3. As we
already have experienced that option 1 is a sure way of not updating
our website. Option 4 seems out of the question, but Frank opted an
interesting idea:
option 6: use joomla on apache machines and have wicket.apache.org
forward to the joomla
I think we could potentially run Joomla on the zone for _editing_, but
we would have to export static pages to some other machine (as Cocoon
does with Daisy).
If this seems like the ASF being difficult and obtuse, just note that
the ASF serves approx 5Tb of data every month - and that doesn't include
downloads which are largely handled by mirrors. Handling this amount of
traffic on dynamic sites would cost more in hardware and maintenance
than is possible at this point in time.
Personally, I think the best option is 2 - use Confluence. We could
easily create a new space - WICKET-DOCS or some such, and have
documentation stored there. The code to export it is already in place.
Alternatively, if you still prefer option 3 (Joomla), we would need some
kind of static export (even if only wget). I would propose that for this
we have the concept of 'documentation release' and a release manager.
That release manager would periodically (every two weeks?) fire off a
script that exports from Joomla and uploads on to the relevant Apache
web server.
The challenge is finding the balance between innovation and following
paths already explored by other Apache projects. Not easy.
As to the Woogle question - I'd propose we focus on the web site tech
first and get that resolved, and come back to woogle as a separate
question (a well-worth-while question).
Regards, Upayavira
