Mitchell Baker wrote: > Alex > > Specific suggestions for documentation from the session are below. Of > course, everyone bascially wanted more and better documents. > > 1. A document annotation system as discussed earlier, where > one could add a comment/edit at the end of a doc > viewers could see the comments even if the doc owner hasn't > revised he doc to include them > the comments would be delted after the doc owner has decided > what to do with the comment > > 2. Better (much better) indicators for out-of-date info. > 3. A way for people to note errors, corrections, improvements without > needing to pull and build the CVS doc tree, and without having to get > CVS write access. > 4. A way for the info in the weekly status reports to be more accessible. > > Mitchell
Hah! It's very nice to know that the trends we've been following in our discussions here recently almost exactly match your comments here. We have to date missed item 4 in this list, however. (2) is something I brought up quite a while ago, using special fields in a database-driven catalog to indicate when a document was last reviewed and its status. We were looking, most recently, to ZOPE for that support, but even without ZOPE, we think we can do it by adding a database layer below the hard-coded catalog. I believe John Keiser was doing some work on that; not sure what the status is right now, but it's not too far along afaik. (3) we have definitely discussed frequently and recently, but we haven't figured out in what ways yet we want to angle for it. As I see it, this goes back to our discussion of developing tools specifically to support documentation. We haven't gotten very far yet, though John Keiser has gotten wikis working (he had me playing with them briefly yesterday). Alex
