CF Conventions Support at PCMDI Kyle Halliday June 19, 2006 UCRL-PRES-XXXXXX

GO-ESSP 2 Overview l Inventory of current CF Website l Requirements for new CF Website l General Approach

GO-ESSP 3 Inventory of Current CF Website l News l Documents —CF Conventions —CF Standard Name table l Conformance —Requirements & Recommendations —CF Compliance Checker l Mailing List —Archives

GO-ESSP 4 Requirements for New CF Website l Primary Goals: —Enhance the discussion capability —Collaborative editing capabilities —Document revision tracking

GO-ESSP 5 Enhanced Discussion Capability l Current Mailing list —Simple and powerful —But… –Archives are not readily searchable –All message are sent to all members –Concept of “discussion thread” is loosely defined –Concept of “discussion state” is loosely defined l Replace with Trac – issue tracking system that can be customized to CF

GO-ESSP 6 Collaborative Editing Capability l Content Management System (CMS) —Distributed community can directly contribute to the website l Plone CMS —Easy to use, open-source

GO-ESSP 7 Document Revision Tracking l Revision Control System l Subversion —Designed for source code management, but can handle any plain text file (or binary file, though it’s harder to visualize binary diffs) —Documents can be maintained in DocBook XML or LaTeX, then “compiled” to PDF, PostScript, HTML, etc… —Integration with Trac

GO-ESSP 8 Plone Website – Home Page

GO-ESSP 9 Plone Website – GUI Editor

GO-ESSP 10 Plone Website – Standard Names

GO-ESSP 11 Trac – Discussions

GO-ESSP 12 Trac – Partial Discussion

GO-ESSP 13 Trac – Subversion Repository

GO-ESSP 14 Trac – Revision History

GO-ESSP 15 Links l PCMDI — l Current CF Website — l Prototype CF Website — l Plone — l Trac — l Subversion —