neos team mailing list archive

[Daniel Kulesz <daniel.kulesz@xxxxxxxxxxxxxxxxxxxxxxxxxxx>]

Public bug reported:

Currently, the Review protocol implemented is quite *too* verbose, this
is, it needs to many pages to present the relevant information. It uses
a table for each Finding, and repeats the following information too many
times:

- the word "finding" before the finding's number
- date and time for the session (a table with all sessions would be sufficient, the number could be just referred)
- the word "severity" before each severity

etc.

Another concern: I think, most organizations might already have a review
template, that is already in use since several years (if we assume they
DO reviews actually). Therefore the least intrusive way to introduce
RevAger into such an organization would be to re-use those templates.

To address these concerns, I propose to re-write some parts of the
Protocol export functionality in order to make it template-based. I
suggest we should use some format that allows for filling text marks -
maybe RTF? Does it support that? (I am pretty sure at least OpenDocument
does that, but RTF is more compatible)

** Affects: revager
     Importance: Undecided
         Status: New


** Tags: feature-request protocol

-- 
(FR) Simplify protocol / Offer user-customizeable protocol templates
https://bugs.launchpad.net/bugs/496534
You received this bug notification because you are a member of Team
N.E.O.S., which is the registrant for RevAger.

Status in RevAger: New

Bug description:
Currently, the Review protocol implemented is quite *too* verbose, this is, it needs to many pages to present the relevant information. It uses a table for each Finding, and repeats the following information too many times:

- the word "finding" before the finding's number
- date and time for the session (a table with all sessions would be sufficient, the number could be just referred)
- the word "severity" before each severity

etc.

Another concern: I think, most organizations might already have a review template, that is already in use since several years (if we assume they DO reviews actually). Therefore the least intrusive way to introduce RevAger into such an organization would be to re-use those templates.

To address these concerns, I propose to re-write some parts of the Protocol export functionality in order to make it template-based. I suggest we should use some format that allows for filling text marks - maybe RTF? Does it support that? (I am pretty sure at least OpenDocument does that, but RTF is more compatible)