Hi!

I want to ask you for your opinion on a few things:

a) Documentation
AFAIK the status was to ask Andreas Kupries for (small?) modification of the 
doctools to be able to make smart C-Function documentation. 
Zoran: Can you tell if your suggestions will be (or are) accepted?

To me it would make sense to make the documentation effort now top priority, 
regardless of the format. Later we can copy and paste it from whatever source 
to our preferred target, but we should aim for the source now. Even the fresh 
NaviServer commands are not documented and only available for the skilled C 
developer (and see current discussion on AOLserver mailinglist).

In the first step documentation must not be perfect and long, as long as it 
respects some formal template documentation style and presents things the way 
they work. Strategy?
Two possible ways:
(A)
1. Construct list of all current commands (C and TCL), mark the deprecated 
ones.
2. Categorize commands.
3. We distribute documentation work among each other (small bunch of commands 
for everyone; and we know who documents what command); and everyone on the 
mailing list is a volunteer per se and likes to contribute :-)
(B)
- Update the '/doc' dir in CVS using current templates OR
- Update the '/doc' dir in CVS using doctools OR
- use Wiki for easy peer review and parse the Wiki structure later to 
transform the docs to whatever format (would be very simple step)

b) Intermediate-Release, Beta-Release
This was also the intention for 4.99.0.
There should be a release, downloadable!, so we have a visible result of the 
current status and efforts. It should be clearly marked or named as 
intermediate or beta release, open for testing and reviewing.
Along with a statement or Roadmap that says: This release will become a 
default stable release - the next target is VFS, caching, etc.
Do we want Version 5.0.0 to be the one with VFS, caching etc. or the first 
stable release? 

What do you think?

Bernd.

Reply via email to