> - I've always liked the PHP manual's style of having the documentation > only editable by the project, but allowing anyone to add comments > with examples, clarifications, best practices, etc. for instance: > http://us.php.net/manual/en/function.preg-replace.php > Could we do something similar with OpenSolaris documentation? Should we?
MySQL docs do the same. I really like it. I find the comments left by other users are often very useful. > - One of the things I've always hated about docs.sun.com is that the process > always seemed to be stuck in the paper manual era - the docs were written > and released with the product, and then not changed until the next release > of the product. (I've heard this may have gotten better lately, since > I'm > not involved with any docs published on docs.sun.com, I haven't followed > it closely.) If bugs were found or customers had issues with the > product that should be documented, we didn't take advantage of the power > of > the web to update them immediately in place - how do we do better for > docs.opensolaris.org? (Could be as simple as the PHP example mentioned > above, or could be something else.) This has been suggested to the docs team, but as yet the site doesn't/can't support it. ~mm
