Changes between Version 1 and Version 2 of 2016WP/ROBUST-5_CMCC


Ignore:
Timestamp:
2016-10-13T16:13:51+02:00 (4 years ago)
Author:
lovato
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • 2016WP/ROBUST-5_CMCC

    v1 v2  
    1 = ''`${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}`'' 
    2  
     1= ''`2016WP CMCC_ROBUST-5_Lovato`'' = 
    32''The NEMO Officer creates a wiki page using this template for each action of the yearly workplan that his institute is in charge. The pattern for the page name in order to place it in the workplan tree is `wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}`''. 
    43 
     
    65 
    76---- 
     7== Help == 
     8The action has to be detailed briefly in the 'Summary' sub-page (ordinary wiki page) for later inclusion in the 'Shared Actions' page or the institute page. Out of this, the rest of the page can be edited on-line inside the form fields considering the following color code: `#!th style="background:lightgrey" PI(S) ` `#!td [#summary Summary] [#abstract Abstract] [#tests Tests] ` |- `#!td style="background:lightblue" Previewer(s) ` `#!td [#preview Preview] ` |- `#!td style="background:lightgreen" Reviewer(s) ` `#!td [#review Review] ` 
    89 
    9 == Help 
     10`#!html <b>Record your modifications for the section you have edited by clicking on the corresponding button at the end of the section (<input type="submit" value="Save ... "/>). Just above, the timestamp of the record will be updated. </b> ` 
    1011 
    11 The action has to be detailed briefly in the 'Summary' sub-page (ordinary wiki page) for later inclusion in the 'Shared Actions' page or the institute page. Out of this, the rest of the page can be edited on-line inside the form fields considering the following color code: 
    12 {{{#!th style="background:lightgrey" 
    13 PI(S) 
    14 }}} 
    15 {{{#!td 
    16 [#summary Summary] 
    17 [#abstract Abstract] 
    18 [#tests Tests] 
    19 }}} 
    20 |- 
    21 {{{#!td style="background:lightblue" 
    22 Previewer(s) 
    23 }}} 
    24 {{{#!td 
    25 [#preview Preview] 
    26 }}} 
    27 |- 
    28 {{{#!td style="background:lightgreen" 
    29 Reviewer(s) 
    30 }}} 
    31 {{{#!td 
    32 [#review Review] 
    33 }}} 
     12`#!div class="important" Apart from the case of 'Summary' section (inclusion of sub-page), the informations inside the form fields and this wiki page itself are stored in 2 separate databases. As a consequence, there is absolutely no risk to make any modification in the page itself as long as you don't change the page name or the content of `{{{`}}}`{{{TracForm ... `` processors.[[BR]] If you edit it in a classical way, use `textearea` instead of `wysiwyg` view because it doesn't handle well the Trac processors ``#!th ... `` or ``#!td ... ``. To keep a preview, you can tick the box `edit side-by-side` at top right of the editing frame. Your default view depends on your last editing work so can be changed in a simple manner. }}} 
    3413 
    35 {{{#!html 
    36 <b>Record your modifications for the section you have edited by clicking on the corresponding button at the end of the section 
    37 (<input type="submit" value="Save ... "/>). Just above, the timestamp of the record will be updated. 
    38 </b> 
    39 }}} 
     14== Summary [=#summary] == 
     15'''Link for editing the summary:[[CMCC_2016?action=edit&section=9]]''' `#!div style="background:lightgrey" [[Include(./Summary)]] ` 
    4016 
    41 {{{#!div class="important" 
    42 Apart from the case of 'Summary' section (inclusion of sub-page), the informations inside the form fields and this wiki page itself are stored in 2 separate databases. As a consequence, there is absolutely no risk to make any modification in the page itself as long as you don't change the page name or the content of `{{{TracForm ... }}}` processors.[[BR]] 
    43 If you edit it in a classical way, use `textearea` instead of `wysiwyg` view because it doesn't handle well the Trac processors `{{{#!th ... }}}` or `{{{#!td ... }}}`. To keep a preview, you can tick the box `edit side-by-side` at top right of the editing frame. Your default view depends on your last editing work so can be changed in a simple manner. 
    44 }}} 
    45  
    46 == Summary [=#summary] 
    47  
    48 '''Link for editing the summary:[[ExtractUrl(./Summary)]]''' 
    49 {{{#!div style="background:lightgrey" 
    50 [[Include(./Summary)]] 
    51 }}} 
    52  
    53 == Abstract [=#abstract] 
    54  
     17== Abstract [=#abstract] == 
    5518This section should be completed before starting to develop the code, in order to find agreement on the method beforehand. 
    5619 
     
    6932'''''Updated on [tf.form_updated_on:] by [tf.form_updater:]''''' 
    7033}}} 
    71  
    7234Once the PI has completed this section, he should send a mail to the previewer(s) asking them to preview the work within two weeks. 
    7335 
    74 == Preview [=#preview] 
    75  
     36== Preview [=#preview] == 
    7637Since the preview step must be completed before the PI starts the coding, the previewer(s) answers are expected to be completed within the two weeks after the PI has sent his request.[[BR]]For each question, an iterative process should take place between PI and previewer(s) in order to reach a "YES" answer for each of the following questions. 
    7738 
     
    8950'''''Updated on [tf.form_updated_on:] by [tf.form_updater:]''''' 
    9051}}} 
    91  
    9252Once all "YES" have been reached, the PI can start the development into his development branch. 
    9353 
    94 == Tests [=#tests] 
    95  
     54== Tests [=#tests] == 
    9655Once the development is done, the PI should complete this section below and ask the reviewers to start their review in the lower section. 
    9756 
     
    11574'''''Updated on [tf.form_updated_on:] by [tf.form_updater:]''''' 
    11675}}} 
    117  
    118 == Review [=#review] 
    119  
     76== Review [=#review] == 
    12077A successful review is needed to schedule the merge of this development into the future NEMO release during next Merge Party (usually in November). 
    12178 
     
    14198'''''Updated on [tf.form_updated_on:] by [tf.form_updater:]''''' 
    14299}}} 
    143  
    144100Once review is successful, the development must be scheduled for merge during next Merge Party Meeting.