cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Noels <>
Subject Re: Expert pre-defined/community post-defined? [WAS: Community health]
Date Thu, 12 May 2005 15:15:54 GMT
On 12 May 2005, at 16:36, Upayavira wrote:

> To validate whether a document should be published, i.e. to review it, 
> which involves clearly seeing what the author changed.


> A document has been updated:
> Document ID: 37
> Branch: daisydocs-1_3
> Language: en
> Name: User Management (unchanged)
> Document Type: Simple Document (unchanged)
> Updated on: 5/9/05 8:09:07 AM
> Updated by: Bruno Dumon
> A new version has been created, state: publish
> Parts
> =====
> Content
> -------
> This part has been updated.
> Mime type: text/xml (unchanged)
> Size: 5936 bytes (previous version: 5592 bytes)
> Content diff:
>     <html>
>     <body>
>     <p>All operations done on the Daisy Repository Server are done as 
> a certain user
> --- acting in a certain role. For this purpose, the Repository Server 
> has a User
> --- Management module to define the users and the roles. An 
> Authenticator component
> --- is responsible for the authentication.</p>
> +++ acting in a certain role. For this purpose, the Repository Server 
> has a user
> +++ management module to define the users and the roles. The 
> authentication of the
> +++ users is done by a separate component, allowing to plug in custom 
> authentication
> +++ techniques.</p>

>> Again, I'm not pushing, nor offering to run it on our own hardware. 
>> Not that I don't want to administer or help out. Just that I don't 
>> want this to be a solo job.
> ASF infra are just getting solaris zones up and running. Shouldn't be 
> long before we can have one of those for ourselves. Also, there is a 
> new discussion about site publishing ASF-wide that this could fit into 
> - whatever we chose to base our system on daisy, drupal, zope, or xml 
> files.

I was just chatting with Sylvain about this. We don't have time to 
create an xdocs export for Daisy, but if all goes well, we'll be doing 
Daisy Books (aggregation and book-like publishing) over summer. Those 
would target XSL-FO and HTML as rendition formats. Maybe someone can 
track this to see how easy it would be to do an xdocs exporter as well.

Of course, since the Wiki already supports branching, it already 
supports most software documentation needs IMHO. But one could always 
create a barebones skin and run wget over it to produce frozen, 
SVN-able static HTML files.

Steven Noels                  
Outerthought - Open Source Java & XML            An Orixo Member
Read my weblog at  
stevenn at                stevenn at

View raw message