> On Thu, Nov 29, 2007 at 06:09:56PM -0500, Peter Memishian wrote: >> Now I'm confused -- do we end up with a fork once it's wikified? If so, >> how will this be managed? If not, please elaborate. > > I think this will represent a fork. The problem for both the DTrace and MDB > answer books is that there has been a torrent of new functonality -- none of > which has been documented because of the inaccessibility of the documentation > tools. In these two particularly egregious examples its important to finally > get them updated, and if this requires a fork so be it.
As Adam says, it's really important that the publicly available documentation keeps pace with the implementation so that users can actually use what we release. By wikifying it we are just enabling this as we now have an easy method for contributors of all types to keep the docs up to date. Not only this but we have a mechanism to integrate many other types of material into a central repository for these technologies. In doing so we can create a rich source of material for all types of consumers and contributors. I understand the need for people to have a single unified document that they can take around with them. I know, for example, that a lot of DTrace practitioners carry the DTrace guide around in pdf and in printed copy. Various people are thinking around how we can still make that happen with a new model like this. Jon.
