Opened 16 years ago

Last modified 14 years ago

#913 new enhancement

Wiki page states

Reported by: bgoedel Owned by: anybody
Priority: normal Component: Request-a-Hack
Severity: normal Keywords:
Cc: Filipe Correia Trac Release: 0.10


We would like to use Trac Wiki pages to write specifications, for instance detailed design specifications for SW components, test plans, etc. There are also a lot of mandatory documents describing the project setup as a Configuration Management Plan, a Quality Assurance Plan, a Resource Plan, etc.

The project developing process foresees that each of these documents is reviewed by a defined set of team members. Thus, each document has a number of states:

in progress
The (version of the) document is currently written by the Author.
available for inspection (AFI)
The document is frozen and reviewed by a pre-defined set of team members. Each reviewer has to write comments about the objections she/he has (we have already a tool for this). The review comments are worked in into a new version of the document which is then in the state
inspected, updated, stored (IUS)
The version of the document that is valid for the project.
This version of the document is not valid anymore due to the availability of a newer IUS version of the document.

For "living documents" it can happen several times during the project development that the document is subject of change. In such a case the old IUS version is valid until a new IUS version is released. After releasing a new IUS version the preceeding IUS version enters the state "outdated".

Currently these specifications are written as Text Document (e.g. MS Word) which is not very convenient. Such documents are "too far away" from the SW developer. Additionally they cannot be easily referenced by tickets or changeset comments.

Thus, I would like to ask for a mechanism in Trac supporting different states of Wiki pages.

Attachments (0)

Change History (3)

comment:1 Changed 16 years ago by Noah Kantrowitz

You may want to look at using tags for this.

comment:2 in reply to:  1 Changed 16 years ago by anonymous

Replying to coderanger:

You may want to look at using tags for this.

I've already installed the TagsPlugin but I think this can be used as workaround for different states of Wiki pages.

My vision of the Wiki page states mechanism is:
When a user clicks onto a link to a Wiki page, she/he should get the IUS (most recent valid) version even if there is a newer version in the state "in progress" or "AFI". The user should be able to edit an IUS page but the resulting new page is not immediately visible for all others. Instead, the created version of the page should be in the state "in progress". It should become accessible for others not until it was reviewed and has become IUS.
If there is already a version "in progress" of this document, the user should edit this version.

With the TagsPlugin I can tag documents to be in a certain state, e.g. I could introduce tags like InProgress, AFI, IUS and Outdated. But as soon as someone follows the link to a page, she/he will get automatically the most recent version even if it is tagged with InProgress.

comment:3 Changed 14 years ago by anonymous

Cc: Filipe Correia added; anonymous removed

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain anybody.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.