Also, I'm interested in how TWiki would fit into a CMM Level 3 culture, which presumably is very process and quality centric - we have a quality and process initiative in my company but TWiki raises concerns with the Quality people about possible uncontrolled creation and duplication of information. Perhaps we could spin this off into a TWikiAndProcesses topic?

We are using TWiki to maintain processes in an ISO 9000 environment (I'm still in the process of convincing this bunch of hardware designers that CMM can apply to ASIC development as well as to software development). Currently we have a process web with limited access and the usual change control/documentation, etc. This works as well as anything else I've used but doesn't take advantage of the strengths of TWiki. E.g. if a user sees a problem in the documentation or wants to suggest an improvement they must fill out a problem report... That is to say, most suggestions don't get made.

I was thinking about a compromise between the convenience of wiki and the change control requirements that the Quality types insist on and came up with the idea of a parallel comments web. For example, if the controlled web is named 'process' then I'd create a web named processcomments with unrestricted access. Then, using a plugin perhaps, override header formatting to insert a link to a comment topic for each heading in a controlled topic. For example replace

---+++ Very Important Heading

with

---+++ Very Important Heading  [[%WEB%comment.%TOPIC%VeryImportantHeading][Comments]]

-- DaveAlsup - 11 Mar 2002

NotePlugin might be possible smart implementation of this idea.

-- PeterMasiar - 30 Mar 2002