Changes between Version 3 and Version 4 of PeerReviewPlugin/Workflows

Timestamp:

Mar 25, 2017, 1:40:26 PM (7 years ago)

Author:

figaro

Comment:

Further cosmetic changes

PeerReviewPlugin/Workflows

@@ -1 +1 @@
 = Workflows
-PeerreviewPlugin supports workflows for reviews. There is one for the author of a review and another one for reviewers. An administrator may change the workflow in ''trac.ini'' similar to [TracWorkflow ticket workflows].
+
+The PeerReviewPlugin supports workflows for reviews. There is one for the author of a review and another one for reviewers. An administrator may change the workflow in `trac.ini` similar to [TracWorkflow ticket workflows].
 
 == Review Workflow
-This workflow is set in section {{{[peerreview-resource_workflow]}}} of ''trac.ini''.
-The default workflow after installation is the following.
+
+This workflow is set in section {{{[peerreview-resource_workflow]}}} of `trac.ini`.
+The default workflow after installation is the following:
+
 {{{#!ini
 [peerreview-resource_workflow]
@@ -48 +51 @@
 reviewing.name = Start review
 }}}
-When setting a review to a finishing state all associated files are set to the same state. This means if the owner sets the review to ''approved'' all files are also set to ''approved''.
+
+When setting a review to a finishing state all associated files are set to the same state. This means if the owner sets the review to ''approved'', then all files are also set to ''approved''.
+
 === Workflow operation ''set_review_owner''
-You may configure a custom workflow operation {{{set_review_owner}}} for reviews.
+
+You may configure a custom workflow operation {{{set_review_owner}}} for reviews:
+
 {{{#!ini
 [peerreview-resource_workflow]
@@ -58 +65 @@
 change_owner.permissions = CODE_REVIEW_MGR
 }}}
+
 This operation allows you to change the owner of a review. Possible users are taken from the same list as the one used when creating a review. In the given example you need the permission {{{CODE_REVIEW_MGR}}} to perform the operation.
 
 == Reviewer Workflow
-Reviewers may mark their individual progess just to inform the review author. The workflow states are not used for any other purpose or to impose any restrictions. For example it is possible for a review author to close a review even when none of the reviewers ever changed his personal workflow state.
+
+Reviewers may mark their individual progress just to inform the review author. The workflow states are not used for any other purpose or to impose any restrictions. For example it is possible for a review author to close a review even when none of the reviewers ever changed his personal workflow state:
+
 {{{#!ini
 [peerreviewer-resource_workflow]