New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
PageTemplates/Workplan (diff) – NEMO

Changes between Version 20 and Version 21 of PageTemplates/Workplan


Ignore:
Timestamp:
2017-10-26T18:07:30+02:00 (6 years ago)
Author:
nemo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PageTemplates/Workplan

    v20 v21  
    1 = ''`$YEAR`'' Workplan 
    2 [[TOC(noheading, Admin/WorkPlan/SharedActions, Admin/WorkPlan/SpecificActions, depth=3)]] 
     1= `$YEAR` Workplan 
    32 
    4 NEMO is a shared, sustainable, and state-of-the-art software for research and operational oceanography. Its development is defined in a yearly workplan.[[BR]]Since 2014, the long term evolution is designed in the [http://www.nemo-ocean.eu/About-NEMO/News/Development-Strategy-2014 NEMO Development Strategy document]. 
     3[[PageOutline(2)]] 
    54 
    6 The next 2 pages describe the ''`$YEAR`'' workplan 
    7 * [[ExtractUrl(./SharedActions)]] contains the workplan's core: the development priorities for all NEMO consortium's institutions which are expected to be directly related to the long term goals. 
    8 * [[ExtractUrl(./SpecificActions)]] contains the other planned developments for the year, as agreed by all consortium members 
     5NEMO is a shared, sustainable, and state-of-the-art software for research and operational oceanography. Its development is defined in a yearly workplan.\\ 
     6Since 2014, the long term evolution is designed in the [attachment:"wiki:SystemTeam/ReportsAndDocuments:NEMO development strategy-2014.pdf" NEMO Development Strategy document]. 
    97 
    10 '''Current wiki pages in the annual workplan tree:''' 
    11 [[TitleIndex(Admin/WorkPlan/,depth=1,hideprefix,format=group)]] 
     8The next 2 sections describe the `$YEAR` workplan. 
    129 
    13 '''Add your work by creating your own sub-pages in the workplan tree from [PageTemplates templates]: 
    14 [[NewPage(id=WPActionSummary, parent=wiki/Admin/WorkPlan, template=WorkplanAction/Summary, placeholder=Pattern for page name: "${WG|INSTITUTE}-${NUM}_${PIS}-${KEYWORD}/Summary", button=New WP Action Summary)]] 
     10== Shared Actions 
     11 
     12[./SharedActions] contains the workplan's core: the development priorities for all NEMO consortium's institutions which are expected to be directly related to the long term goals. 
     13 
     14||= '''AGRIF''' \\(''!`$YEAR`WP/AGRIF-*'') =||= '''Configuration Manager''' \\(''!`$YEAR`WP/CONFIGMAN-*'') =||= '''Enhancement''' \\(''!`$YEAR`WP/ENHANCE-*'') =||= '''HPC''' \\(''!`$YEAR`WP/HPC-*'') =||= '''Robustness''' \\(''!`$YEAR`WP/ROBUST-*'') = ||=    '''Wave Coupling''' \\(''!`$YEAR`WP/WAVE-*'') =|| 
     15|| [[TitleIndex(`$YEAR`WP/AGRIF-, hideprefix, depth=0)]] || [[TitleIndex(`$YEAR`WP/CONFIGMAN-, hideprefix, depth=0)]] ||  [[TitleIndex(`$YEAR`WP/ENHANCE-, hideprefix, depth=0)]] || [[TitleIndex(`$YEAR`WP/HPC-, hideprefix, depth=0)]] || [[TitleIndex(`$YEAR`WP/ROBUST-, hideprefix, depth=0)]] || [[TitleIndex(`$YEAR`WP/WAVE-, hideprefix, depth=0)]] || 
     16 
     17== Specific Actions 
     18 
     19[./SpecificActions] contains the other planned developments for the year, as agreed by all consortium members 
     20 
     21||= [wiki:`$YEAR`WP/CMCC CMCC actions] \\(''!`$YEAR`WP/CMCC-*'') =||= [wiki:`$YEAR`WP/CNRS CNRS actions] \\(''!`$YEAR`WP/CNRS-*'') =||= [wiki:`$YEAR`WP/INGV INGV actions] \\(''!`$YEAR`WP/INGV-*'') =||= [wiki:`$YEAR`WP/Mercator_Ocean Mercator Océan actions] \\(''!`$YEAR`WP/Mercator_Ocean-*'') =||= [wiki:`$YEAR`WP/Met_Office Met_Office actions] \\(''!`$YEAR`WP/Met_Office-*'') =||= [wiki:`$YEAR`WP/NOC NOC actions] \\(''!`$YEAR`WP/NOC-*'') =|| 
     22|| [[TitleIndex(`$YEAR`WP/CMCC-, hideprefix, depth=0)]] || [[TitleIndex(`$YEAR`WP/CNRS-, hideprefix, depth=0)]] || [[TitleIndex(`$YEAR`WP/INGV-, hideprefix, depth=0)]] || [[TitleIndex(`$YEAR`WP/Mercator_Ocean-, hideprefix, depth=0)]] || [[TitleIndex(`$YEAR`WP/Met_Office-, hideprefix, depth=0)]] || [[TitleIndex(`$YEAR`WP/NOC-, hideprefix, depth=0)]] || 
     23 
     24== Overall status #status 
     25 
     26||= Tickets \\'Type: Task' \\'Milestone: `$YEAR` WP' =|| [[TicketQuery(type=Task, milestone=`$YEAR` WP, format=progress)]][[TicketQuery(type=Task, milestone=`$YEAR` WP)]] || 
     27 
     28== Add an action 
     29 
     30Append your action(s) to the list by initiating 2 resources to track and archive your development work: a wikipage to describe and follow the ongoing work through different steps, and a ticket to gather the group discussion and monitor the overall workplan progress. 
     31 
     32{{{#!td style="vertical-align: top" 
     33[[NewPage(id=WPAction, parent=wiki/`$YEAR`WP, template=WorkPlanAction, placeholder=Wikipage name, button=Create action's wikipage)]] 
     34__Reminders__ 
     35* Wikipage name pattern: \\ 
     36  `{WG for shared or INSTITUTE for specific actions}-{action number}_{PI(S)}-{keyword(S)}` 
     37* Current WG: [wiki:WorkingGroups/AGRIF AGRIF] | [wiki:WorkingGroups/nemo_ConfigurationManager CONFIGMAN] | ENHANCE | [wiki:WorkingGroups/NEMO_HPC HPC] | [wiki:WorkingGroups/Robustness-TestCases ROBUST] | [wiki:WorkingGroups/Wave_Coupling WAVE] 
     38}}} 
     39{{{#!td style="vertical-align: top" 
     40   {{{#!html 
     41      <p></p> 
     42      <form action="/nemo/newticket?summary=summary&type=type&version=version" method="get"> 
     43      <input type="hidden" name="type"    value="Task"                      /> 
     44      <input type="hidden" name="version" value=""                          /> 
     45      <input type="text"   name=summary size=51 placeholder="Ticket subject"/> 
     46      <input type="submit" value="Open action's ticket"/> 
     47      </form> 
     48   }}} 
     49__Ticket fields setting__ \\ 
     50* 'Type: Task' and 'Milestone: `$YEAR` WP' by default 
     51* 'Cc': add email(s) of people outside NEMO ST for further notification. 
     52* 'Component': the area the change is being targeted for. 
     53The other fields in the ticket (e.g. 'Priority', 'Keywords') should also be set appropriately. 
     54}}} 
     55 
     56See [wiki:Developers/DevelopingCodeChanges the instructions page] to learn how to implement a development work in NEMO.