On 9/9/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
>
> Wow! It is great to see how much you (and Bernd)
> have done in so little time... Congratulations!
>
This is what we can base our documentation on, the question is: do we
convert it into doctools or keep as html?
Or put it in a wiki.
API references are one kind of documentation. Sadly, it seems it
really has to be written by programmers. If the docs are to have any
true insight, the writer has to be able to read C code fluently.
It makes perfect sense to keep this kind of document in CVS. Either
the API doc accurately reflects the code it is bundled with, or it
does not. The two should be in sync, and are written by the same
people.
Then there's the other stuff. It's higher level, it crosses the
boundaries of many APIs, and unlike the API docs some of it can be a
matter of perspective. This really needs to be as inclusive and as
low-barrier as possible. CVS is just too much effort for this. It's
not *that* hard, but the barrier doesn't have to be very high before
people just won't bother. Hey, we're all busy and lazy, right?
Assuming a wiki, there's still the question of which one. I think
I've convinced myself that the Tcl wiki is a good idea. I think we
(people on the 'Net in general) have reached a point where it's not
'cool' any more to have your own domain name, run your own services
etc. -- you go where the people are. You want to talk photography?
Post your photos to flickr.
I added the simple place-holder page about naviserver to the Tcl wiki
just because there was nothing there about us already. In one day:
On 9/8/06, Michael A. Cleverly <[EMAIL PROTECTED]> wrote:
I just discovered the existence of NaviServer last night (courtesy of
http://wiki.tcl.tk/2090). I don't know where I've been living for the
past year... but wow, I'm seriously impressed and extremely excited
about the existance of this project/fork!
Wiki's work. And so does going where the people are.
