Finish initial website. Follow procedure in How-to Forrest Update versions of external DOM/SAX/JAXP code to best-possible that still passes TCK-JAXP-1.2. making TCK-compliant API's common (Actually is neilg,ilene) Establish efficient distribution mirrors and change the download link on the xml-commons website. See doc Making your downloads mirrorable Fix broken links in resolver-article.xml ... only three, but important ones: download, copyright, and apidocs. Decide how to build separate distributable docs for each "component", and how they will also be published to xml-commons website (since resolver, which, etc. will get shipped as individual components, even though they live in the same project). Best if xdocs content can remain in /java with their code. See email: draft website for xml-commons using Forrest and a website with separate distributable components Basic consensus building/comments about explicitly shipping various portions of xml-commons as separate components. See email: [PROPOSAL] xml-commons project organization: several subprojects Decide directory layout. See email: Repository layout Replace the README file at http://xml.apache.org/commons/dist/ Move the distribution area to be more mirror-friendly (see infrastructure@ list) Better overview doc of why xml-commons has it's own sets of DOM/SAX/JAXP; also basic docs on TCK compliance etc. Discussion and concensus on packaging of external DOM/SAX/JAXP interfaces (xml-apis.jar etc.). Note that this release number is only really the release number of the forrestized-docs, not of the individual components or code. Added experimental building of the Resolver component docs using DocBook DTDs and XSL. Added some ToDo items and noted some issues in How-to Forrest. Added some content as overview for each component. Added some ToDo items. Added placeholder docs and tabs for components. Built demo website using Forrest. Gleaned content from xml-commons/README.html