Mailing-List: contact docs-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: docs@cocoon.apache.org
Date: Tue, 28 Oct 2003 15:00:04 +0100
Message-Id: <200310281400.h9SE04a15940@otsrv1.iic.ugent.be>
From: stevenn@outerthought.org
To: docs@cocoon.apache.org
Subject: [WIKI-UPDATE] WoodySample Lenya Doco Tue Oct 28 15:00:04 2003

Page: http://wiki.cocoondev.org/Wiki.jsp?page=WoodySample , version: 10 on Tue Oct 28 13:48:54 2003 by 168.209.98.67

- !!!!A simple Woody example
? -

+ !!!A simple Woody example


Page: http://wiki.cocoondev.org/Wiki.jsp?page=Lenya , version: 42 on Tue Oct 28 13:58:25 2003 by MichaelWechner

+ * [LenyaIssues], [Lenya1.2]
- * [Lenya1.2]
- * [LenyaIssues]


Page: http://wiki.cocoondev.org/Wiki.jsp?page=Doco , version: 1 on Tue Oct 28 13:59:32 2003 by MichaelWechner

New page created:
+ !!Contents
+ *Description
+ *Features at a glance
+ *Architecture at a glance
+ *Mail Threads
+ *"Details"
+ 
+ 
+ 
+ !!Description
+ The proposal is about the creation of a content management system for 
+ apache projects, codenamed "Doco", whereas the priorities should be 
+ *Ease of use
+ *Security
+ 
+ !!Features at a glance
+ # super-easy editing (should satisfy wiki lovers)
+ # minimal, efficient and secure workflow (should satisfy board@ security concerns)
+ # should allow the creation of static content (should satisfy infrastructure@ and mirror@ concerns)
+ # should not be a distributed product (should avoid sensations of forking from existing projects)
+ # should reuse more than reinvent
+ # should come up with structured XML content well organized in a repository
+ 
+ 
+ !!Architecture at a glance
+ {{{
+              +----------------+       +-----------------------------------------------+                    
+              | www.apache.org |       |                                               |
+          --->|                | wget  |+---------------+  publish +------------------+|
+  Browser     | httpd | CVS    |------>|| Forrest | SVN |<---------| FS/SVN  |  Lenya ||<--> Browser
+          <---|                |       |+---------------+          +------------------+|(public authoring)
+              |                |       |                                  ^ |     ^ |  |
+              +----------------+       |                                  | v     | |  |
+                                       |                           +-----------+  | |  |
+                                       |                           |  James    |  | |  |
+                                       |                           +-----------+  | v  |
+                                       +-----------------------------------------------+
+                                                                         ^          ^
+                                                                         |          | committer authoring
+                                                                         |          | (approve/reject, etc.)
+                                                                         v          v
+                                                                     Mailclient   Browser
+ }}}
+ 
+ 
+ 
+ !!Mail Threads
+ 
+ __Lenya Dev:__\\
+ [http://news.gmane.org/onethread.php?group=gmane.comp.cms.lenya.devel&root=%3C3F97CC8A.3040102%40apache.org%3E]\\
+ \\
+ \\
+ [http://news.gmane.org/onethread.php?group=gmane.comp.cms.lenya.devel&root=%3COFACF489EA.B74EF621-ON80256DC9.002C873F-80256DC9.002D77F5%40slc.co.uk%3E]
+ \\
+ \\
+ __Cocoon Dev:__\\
+ [http://news.gmane.org/onethread.php?group=gmane.text.xml.cocoon.devel&root=%3C3F97CC8A.3040102%40apache.org%3E]
+ \\
+ \\
+ __Forrest Dev:__\\
+ [http://news.gmane.org/onethread.php?group=gmane.text.xml.forrest.devel&root=%3C3F97CC8A.3040102%40apache.org%3E]\\
+ [http://news.gmane.org/onethread.php?group=gmane.text.xml.forrest.devel&root=%3COFC1978CA9.BBD6B5F3-ON80256DCD.002E80FE-80256DCD.002EF321%40slc.co.uk%3E]\\
+ 
+ \\
+ __James Dev:__\\
+ [http://news.gmane.org/onethread.php?group=gmane.text.xml.forrest.devel&root=%3CNBBBJGEAGJAKLIDBKJOPEEJGEOAB.noel%40devtech.com%3E]
+ 
+ 
+ !!"Details"
+ 
+ !Workflow
+ # If document is being edited and saved, then email is sent to the 'doco committer' list (which is a private list)
+ # Committer will receive an email similar to moderate ezml moderate emails and diff between published and authoring/working document are being shown. , e.g.
+ **lenya-dev-accept-1067323167.74085.bhhdiekdcmdijjeaiknc@cocoon.apache.org
+ **lenya-dev-reject-1067323167.74085.bhhdiekdcmdijjeaiknc@cocoon.apache.org.
+ # If diff is accepted then the page will be published
+ # If diff is rejected then ...?
+ 
+ !Workflow Issues
+ # reply and reply-all ... what about showing them as a "mailto" link within the email?
+ # sniffing and spoofing ... what about a 4eyes approach, i.e. at least two committers need to approve, although doesn't really make it bulletproof ...
+ # Content needs to be checked after being approved (images, code snippets, etc.) ... what about checking content during saving already?
+ 
+ 
+ !Editing
+ # The public-authoring interface will only have a "EDIT" button
+ # By clicking on "EDIT" Linotype will be opened
+ # New documents could be inserted via "Wiki style", but instead of using Wiki syntax one could use <a href="NewDocument">...</a> where Lenya would need to parse the page and highlight non-existing links
+ # Lenya can provide a committer-authoring interface, where workflow (also history), revisions, editing could be stuffed within the Lenya menubar.
+ 
+ !Staging to Live
+ # every 12 hours www.apache.org is retrieving the data from the staging server. What if the staging system is being cracked five minutes before the actual retrieval time? Maybe Lenya could keep each document in a publish queue for at least 12 hours. Also every retrieval could set a CVS flag, such that changes can be easily reverted.
+