Changes between Version 51 and Version 52 of Developers/DevProcess

Timestamp:

2016-03-03T23:40:14+01:00 (8 years ago)

Author:

nicolasmartin

Comment:

--

Developers/DevProcess

@@ -1 +1 @@
 = Form page for development work =
-
 [[PageOutline(2)]]
 
-A wiki page associated with a give action should be created in `wiki/${YEAR}WP/${WORKING_GROUP}-${ACTION_NUMBER}_${PI}` using this template.[[BR]]
-From that, you can customize it while editing within the !TracForm container `{{{#!TracForm ... }}}`. If necessary, you can copy the entire form (add a number `_[0-9]` to wiki page name) or the respective area in order to match the number of the (P)Reviewer(s). The best solution is not to extend significantly the length of the page.
+A wiki page associated with a give action should be created in `wiki/${YEAR}WP/${WORKING_GROUP}-${ACTION_NUMBER}_${PI}` using this template.[[BR]] From that, you can customize it while editing within the !TracForm container `{{{#!TracForm ... }}}`. If necessary, you can copy the entire form (add a number `_[0-9]` to wiki page name) or the respective area in order to match the number of the (P)Reviewer(s). The best solution is not to extend significantly the length of the page.
 
-This is the color code for the fulfilment of this form:
-{{{#!td style="background:lightgrey"
-PI(S)
-}}}
-{{{#!td style="background:lightblue"
-Previewer(s)
-}}}
-{{{#!td style="background:lightgreen"
-Reviewer(s)
-}}}
+This is the color code for the fulfilment of this form: {{{#!td style="background:lightgrey" PI(S) }}} {{{#!td style="background:lightblue" Previewer(s) }}} {{{#!td style="background:lightgreen" Reviewer(s) }}}
 
 ----
-
 The PI is responsible to closely follow the progress of the action, and especially to contact NEMO project manager if the delay on preview (or review) are longer than the 2 weeks expected.[[BR]]
 
 == Abstract ==
-This section should be completed before starting to develop the code, in order to find agreement on the method beforehand.[[BR]]
-'''To enabling the !ticket and the source links in the Trac environment, those have to be hardcoded in the form''' 
+This section should be completed before starting to develop the code, in order to find agreement on the method beforehand.[[BR]] '''To enabling the !ticket and the source links in the Trac environment, those have to be hardcoded in the form'''
+
 {{{
 #!TracForm
@@ -29 +17 @@
 #!submit_label 'Submit Abstract'
 #!keep_history yes
-|| Action || ''[tf.input:action -id=piform '${WORKING_GROUP}-${ACTION_NUMBER} $Title' 100]'' ||
-{{{#!td style="background-color:lightgrey"
-PI(S)
+|| Action || [tf.input:action -id=piform '${WORKING_GROUP}-${ACTION_NUMBER} $Title' 100] ||
+|| PI(S) || ''[tf.input:pi -id=piform 'Names' 100]'' ||
+|| Ticket || `#XXXX` ||
+|| Branch || `[source:/branches/$YEAR/dev_r${FORK_REVISION}_${WORKING_GROUP|INSTITUTE}${ACTION_NUMBER}_${PURPOSE}]` ||
+|| Previewer(s) || ''[tf.input:previewers -id=piform 'Names' 100]'' ||
+|| Reviewer(s) || || ''[tf.input:reviewers -id=piform 'Names' 100]'' ||
+Part 1: Description
+ [tf.textarea:description -id=piform 'Describe the goal of development, and the methodology.\n\nAdd reference documents or publications if relevant.' 200 20]
+Part 2: Implementation
+ [tf.textarea:implementation -id=piform 'Describe flow chart of the changes in the code.\n\nList the .F90 files and modules to be changed.\n\nDetailed list of new variables (including namelists) to be defined.\nGive for each the chosen name (following coding rules) and definition.' 200 20]
+Part 3: Reference manual updates
+ [tf.textarea:manual -id=piform 'Using part 1 and 2, define the summary of changes to be done in the NEMO reference manual (tex files).' 200 20]
+'''Updated on [tf.form_updated_on:] by [tf.form_updater:]'''
 }}}
-|| ''[tf.input:pi -id=piform 'Names' 100]'' ||
-|-
-{{{#!td align=left
-Ticket
-}}}
-{{{#!td style="background:lightgrey"
-`#XXXX`
-}}}
-|-
-{{{#!td align=left
-Branch
-}}}
-{{{#!td style="background:lightgrey"
-`[source:/branches/$YEAR/dev_r${FORK_REVISION}_${WORKING_GROUP|INSTITUTE}${ACTION_NUMBER}_${PURPOSE}]`''
-}}}
-|-
-{{{#!td style="background-color:lightblue"
-Previewer(s)
-}}}
-|| ''[tf.input:previewers -id=piform 'Names' 100]'' ||
-{{{#!td style="background-color:lightgreen"
-Reviewer(s)
-}}}
-|| ''[tf.input:reviewers -id=piform 'Names' 100]'' ||
-=== Part 1: Description ===
-[tf.textarea:description -id=piform 'Describe the goal of development, and the methodology.\n\nAdd reference documents or publications if relevant.' 200 20]
-=== Part 2: Implementation ===
-[tf.textarea:implementation -id=piform 'Describe flow chart of the changes in the code.\n\nList the .F90 files and modules to be changed.\n\nDetailed list of new variables (including namelists) to be defined.\nGive for each the chosen name (following coding rules) and definition.' 200 20]
-=== Part 3: Reference manual updates ===
-[tf.textarea:manual -id=piform 'Using part 1 and 2, define the summary of changes to be done in the NEMO reference manual (tex files).' 200 20]
-==== ''Updated on [tf.form_updated_on:] by [tf.form_updater:]'' ====
-}}}
+
 Once the PI has completed this section, he should send a mail to the previewer(s) asking them to preview the work within two weeks.