XML version of feature plan

[CP Hennessy]

Is it possible to add some more information to the TODO status
for example : 
	TODO:RFC
	TODO:design  
	TODO:infrastucture
	TODO:testing
	TODO:make public

This might help get other developers interested, and to lend a hand
especially for the larger/complex features.

For myself I like the way password register works in Mozilla. 
If there was some description about the current status and what had to
be done I would like to contribute - the same can be said of the HTTP 
pipe-lining feature. I know that both of these have been in the TODO
list for quite a while ( pre 3.0 ?) 

CP

On Tuesday 03 December 2002 23:47, Cornelius Schumacher wrote:
> I have just committed an xml version of the feature plan and a
> corresponding php script to generate the known html version on the fly.
> Credits for the php stuff go to Mario Andres Yepes C. Thanks Mario.
>
> Generating the html from an xml source has a couple of big advantages:
> - Changing the status of a feature just means changing an attribute, not
> moving around html code.
> - Moving a planned feature from one version to another is also done by
> just changing an attribute.
> - The hierarchy is only defined once, being the same for all versions
> and status values.
> - All features of an application are in one block, not distributed over
> the document depending on the status.
> - All features for all versions are in one file.
>
> The XML can be found at
> developer.kde.org/development-versions/kde-features.xml and the
> php page at
> developer.kde.org/development-versions/kde-3.2-features.php.
>
> The information is not yet complete. There are a few things missing
> which are present in the current html version, because the perl script
> I used to convert the html to xml didn't get them.
>
> If there is agreement that the xml file is preferable for storing the
> feature plan I will add the missing information, clean it up a bit and
> remove the html files.
>
> I think this would make it much more easy to maintain the planned
> features document because it's less work and less error-prone to update
> the information.
>
> What do you think?