You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by cr...@apache.org on 2005/06/16 03:46:47 UTC
svn commit: r190848 - /forrest/trunk/site-author/status.xml
Author: crossley
Date: Wed Jun 15 18:46:47 2005
New Revision: 190848
URL: http://svn.apache.org/viewcvs?rev=190848&view=rev
Log:
The "type" attribute was recently made required.
So add a default type=fix to all <todo><action> elements.
Modified:
forrest/trunk/site-author/status.xml
Modified: forrest/trunk/site-author/status.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/status.xml?rev=190848&r1=190847&r2=190848&view=diff
==============================================================================
--- forrest/trunk/site-author/status.xml (original)
+++ forrest/trunk/site-author/status.xml Wed Jun 15 18:46:47 2005
@@ -2034,20 +2034,20 @@
<todo>
<actions priority="high">
- <action context="code" dev="open">
+ <action type="fix" context="code" dev="open">
<!-- Please leave this action at the top -->
Please see our Jira
<link href="site:bugs">issue tracker</link> for tasks to be done.
Note that the Todo list below is old. We need someone to move those
tasks over to the issue tracker.
</action>
- <action context="code" dev="open">
+ <action type="fix" context="code" dev="open">
Rework the menu generation system to make it more flexible. See thread
<link
href="http://marc.theaimsgroup.com/?w=2&r=1&s=Fixing+menus&q=t">Fixing
menus</link>
</action>
- <action context="code" dev="open">
+ <action type="fix" context="code" dev="open">
Define an 'object model' for Forrest sites, in the form of a Cocoon
pipeline, that defines
- The directory structure of a site
@@ -2059,28 +2059,28 @@
attributes) and the stylesheets (through
<code>document(cocoon:/...)</code> calls or inlined with source XML).
</action>
- <action context="code" dev="NKB">
+ <action type="fix" context="code" dev="NKB">
Finalise the project-definition DTDs, like status.xml and module.xml;
try to come up with a common format with others on community.at.apache.org.
</action>
</actions>
<actions priority="medium">
- <action context="code" dev="NKB">
+ <action type="fix" context="code" dev="NKB">
Finish the RSS feed for status.xml.
Aggregate status.xml and project.xml to have all needed project data.
</action>
- <action context="docs" dev="open">
+ <action type="fix" context="docs" dev="open">
Add stylesheets to render the enhanced status.xml file contents.
</action>
- <action context="code" dev="JT">
+ <action type="fix" context="code" dev="JT">
In skinconf.xml, change 'disable-search' to 'enable-search'.
</action>
- <action context="code" dev="NKB">
+ <action type="fix" context="code" dev="NKB">
Enhance the initial forrest toolbar for Mozilla.
See email discussion <link href="http://marc.theaimsgroup.com/?l=forrest-dev&m=102471820523388">draft forrest toolbar for Mozilla</link>.
</action>
- <action context="code" dev="open">
+ <action type="fix" context="code" dev="open">
Fix things so docs can be edited in src/*, and have the changes appear
immediately in the webapp. Involves creating/using an InputModule for
passing 'forrest.skin' and other properties to the sitemap, so we can
@@ -2089,7 +2089,7 @@
of in-place modification. Perhaps a @token@-to-value Transformer could
be the same ${variable}-to-value Transformer mentioned in the RT [3].
</action>
- <action context="code" dev="open">
+ <action type="fix" context="code" dev="open">
Act on <link href="http://marc.theaimsgroup.com/?t=104099660500001&r=1&w=2">'Entities in XML docs' RT</link>.
I can implement Stefano's
suggested solution quite easily, but is such limited functionality
@@ -2097,55 +2097,55 @@
Best short-term alternative seems to be using the XNI XInclude
processor for pre-validation inclusion.
</action>
- <action context="docs" dev="open">
+ <action type="fix" context="docs" dev="open">
A lot of the info on the website is outdated.
</action>
- <action context="docs" dev="open">
+ <action type="fix" context="docs" dev="open">
Using metadata
from site.xml, it would at least be possible to indicate how old the
doc is, and perhaps indicate its relevance from a small controlled
vocabulary.
</action>
- <action context="design" dev="open">
+ <action type="fix" context="design" dev="open">
Develop a mechanism for supporting legacy URLs.
See email discussion -
<link href="http://marc.theaimsgroup.com/?l=forrest-dev&m=102390892524750">redirects with static sites</link>
</action>
- <action context="code" dev="open">
+ <action type="fix" context="code" dev="open">
Fix up and integrate the Forrest Maven plugin.
</action>
</actions>
<actions priority="low">
- <action context="code" dev="open">
+ <action type="fix" context="code" dev="open">
Ensure that PHP-like stuff can be embedded easily in Forrest files and
document it.
</action>
- <action context="code" dev="open">
+ <action type="fix" context="code" dev="open">
Continue the development of the <link
href="site:v0.70//libre-intro">Libre</link> facility - replacement for
*/book.xml
</action>
- <action context="docs" dev="open">
+ <action type="fix" context="docs" dev="open">
Start a community doc where we list tools such as "code".
</action>
- <action context="code" dev="open">
+ <action type="fix" context="code" dev="open">
Migrate to a decent schema language, primarily so that we can use
namespaces in XML docs, allowing things like XInclude,
<link href="http://www.xml.com/pub/a/2002/10/30/rdf-friendly.html">in-line metadata</link>,
in-line SVG, Jelly snippets, or anything else users can make a
Transformer for.
</action>
- <action context="code" dev="open">
+ <action type="fix" context="code" dev="open">
Streamline the process of adding support for new schemas. Ideally we'd
have an auto-download system, e.g. 'forrest-update docbook' would fetch
and install the Docbook DTDs, create catalog entries, sitemap mods etc.
</action>
- <action context="code" dev="NKB">
+ <action type="fix" context="code" dev="NKB">
Make a CSS Generator and a stylesheet to serialize it to text.
</action>
- <action context="docs" dev="open">
+ <action type="fix" context="docs" dev="open">
Add a document about authoring in XML for beginners..
</action>