Gregor J. Rothfuss wrote:
we now have the means to use lenya (on our zone) to feed our
documentation. i think we should do some experiments as to how we
could eat our own dogfood to create the docs for the site.
sure
there are lots of nice bells and whistles, but i would like us to get
started with something simple and then extend the solution as we use
it more and more.
we just have to write a xdoc based publication which has the same
site-structure as
Forrest and then export it statically into SVN, whereas the xdocs should
also be added
to SVN
as you may have noted elsewhere, this currently a hot topic both on
the cocoon project, and overall. the asf has resurrected the site-dev
list to coordinate requirements, and there is a common site-build zone
that we may end up using for staging and deployment. i have attached
one of the key emails from that list below.
i am not yet totally clear how this will all work together, but we
should definitely get started as soon as possible (keeping in mind
that we now have two community members, solprovider and jon, who
regularly write useful documentation)
WDYT?
without being cynical, it's just a matter of doing it.
we could start such a publication within the sandbox and based on 1.4-dev
which would hopefully help to stabilize 1.4
Michi
-------- Original Message --------
Subject: mission
Date: Wed, 11 May 2005 00:12:44 +1000
From: David Crossley <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
I suppose that we should first clarify our purpose,
then send an email to pmcs@ asking for people to help
from the beginning and so enable ownership.
There was a recent flurry of discussion on infrastructure@
when Noel suggested we finally have the machinery to establish
a site build and staging server. ...
Noel J. Bergman wrote:
Justin Erenkrantz wrote:
> I don't see the need for a zone dedicated to creating the apache.org
> sites. Why can't each PMC have their own zone and create their
> site in it however they want to do it?
We need a single place for infrastructure to restore from if we have a
problem, right? And we are trying to move away from having to keep huge
quantities of generated artifacts in source control just for the
purpose of
restoring the web-site.
So the primary goals are:
- have a means to build all of the web sites from source control
- provide for human review of the staged content
- push the approved content to a publishing area
- have the live web servers sync from the publishing area
So, we reduce the need for shell accounts related to publishing,
remove the
need to keep generated sites in source control, improve disaster
recovery.
--- Noel
This has been discussed many times before on infrastructure.
I tried to summarise some of the needs at one stage.
http://forrest.apache.org/0.7/proposal-asf-publish.html
Here is the first paragraph ...
All ASF projects need to be able to concentrate on their projects
and the content of their websites, rather than get tangled up in
arcane website publication procedures.
I presume that we need a site-build.zones.apache.org
where we would run the various documentation tools, e.g.
Maven, Forrest, Anakia, Ant, etc. There is also the web interface
for the Forrestbot which enables project committers to trigger
their build and review logfiles. It would need Tomcat.
Add to that mechanisms to generate javadoc and other code docs.
Without going into details too much, are those our aims?
--David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
