Changes between Version 11 and Version 12 of Page Templates/Workplan/Action


Ignore:
Timestamp:
2016-10-12T14:58:16+02:00 (4 years ago)
Author:
nicolasmartin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Page Templates/Workplan/Action

    v11 v12  
    1 = ''`${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}`'' = 
     1= ''`${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}`'' 
    22 
    3 == Help == 
     3''For each institute, the NEMO Officer [[BR]] 
     4The development process of each action of the yearly workplan should be described only in one wiki page based on this template and created in the workplan tree with the pattern `wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}`''.[[BR]] 
    45 
    5 ''The development process of each action of the yearly workplan should be described only in one wiki page created in the tree of the corre`wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}` using this template.Then, detail your action in the 'Summary' sub-page (ordinary wiki page).[[BR]]From that, the rest of the page has to be edited on-line inside the colored form fields and submit your modifications by clicking on the 'Submit ...' at the end of the section.'' 
    6 '''There is absolutely no risk for all form content to make any modification in the wiki page as long as you edit out of `{{{TracForm ... }}}` processor'''. The data of a form field is stored in a different database from the wiki page, so you can delete a version or submit a new one without danger.[[BR]] 
    7  
    8 '''For the Trac links to associated !ticket & development branch, it is mandatory to edit the page in `textarea` view'''. The `wysiwyg` view will alter the interpretation of the Trac processors `{{{#!th ... }}}` or `{{{#!td ... }}}` in the table.[[BR]] 
    9 ''To keep a preview, you can tick the box `edit side-by-side` at top right of the editing frame. It will part your screen with the editing view on the left and the preview on the right so you can control your changes. If you get by default the 'wysiwyg' view, this is due to your last editing work and can be changed in a simple manner.'' 
     6''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]]'' 
    107 
    118---- 
    129 
    13 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]] 
     10== Help 
    1411 
    15 [[PageOutline(2)]] 
    16  
    17 This is the color code for the fulfilment of this form: 
    18 {{{#!td style="background:lightgrey" 
     12The action has to be detailed briefly in the 'Summary' sub-page (ordinary wiki page) for later inclusion in the 'Shared Actions' or institute page. Out of this, the rest of the page can be edited on-line inside the form fields considering the color code, record your modifications by clicking on the 'Save ...' button at the end of the section. This is the color code for the fulfilment of this form: 
     13{{{#!th style="background:lightgrey" 
    1914PI(S) 
    2015}}} 
     16{{{#!td 
     17[#summary Summary] 
     18[#abstract Abstract] 
     19[#tests Tests] 
     20}}} 
     21|- 
    2122{{{#!td style="background:lightblue" 
    2223Previewer(s) 
    2324}}} 
     25{{{#!td 
     26[#preview Preview] 
     27}}} 
     28|- 
    2429{{{#!td style="background:lightgreen" 
    2530Reviewer(s) 
    2631}}} 
     32{{{#!td 
     33[#review Review] 
     34}}} 
    2735 
    28 == Summary == 
     36'''There is absolutely no risk for all form content to make any modification in the wiki page as long as you edit out of `{{{TracForm ... }}}` processor'''. The data of a form field is stored in a different database from the wiki page, so you can delete a version or submit a new one without danger.[[BR]] 
     37 
     38The `wysiwyg` view will alter the interpretation of the Trac processors `{{{#!th ... }}}` or `{{{#!td ... }}}` in the table.[[BR]] 
     39To keep a preview, you can tick the box `edit side-by-side` at top right of the editing frame. It will part your screen with the editing view on the left and the preview on the right so you can control your changes. If you get by default the 'wysiwyg' view, this is due to your last editing work and can be changed in a simple manner. 
     40 
     41== Summary [=#summary] 
    2942 
    3043'''Link for editing the summary:[[ExtractUrl(./Summary)]]''' 
     44{{{#!div style="background:lightgrey" 
    3145[[Include(./Summary)]] 
     46}}} 
    3247 
    33 == Abstract == 
     48== Abstract [=#abstract] 
    3449 
    3550This section should be completed before starting to develop the code, in order to find agreement on the method beforehand. 
     
    5267Once the PI has completed this section, he should send a mail to the previewer(s) asking them to preview the work within two weeks. 
    5368 
    54 == Preview == 
     69== Preview [=#preview] 
    5570 
    5671Since 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. 
     
    7287Once all "YES" have been reached, the PI can start the development into his development branch. 
    7388 
    74 == Tests == 
     89== Tests [=#tests] 
    7590 
    7691Once the development is done, the PI should complete this section below and ask the reviewers to start their review in the lower section. 
     
    96111}}} 
    97112 
    98 == Review == 
     113== Review [=#review] 
    99114 
    100115A successful review is needed to schedule the merge of this development into the future NEMO release during next Merge Party (usually in November).