= `$YEAR` Workplan

[[PageOutline(2)]]

NEMO is a shared, sustainable, and state-of-the-art software for research and operational oceanography. Its development is defined in a yearly workplan.\\
Since 2014, the long term evolution is designed in the [attachment:"wiki:Users/private:NEMO development strategy-2014.pdf" NEMO Development Strategy document].

The next 2 sections describe the `$YEAR` workplan.

== Shared Actions

[./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.

||= '''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-*'') =||
|| [[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)]] ||

== Specific Actions

[./SpecificActions] contains the other planned developments for the year, as agreed by all consortium members

||= [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-*'') =||
|| [[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)]] ||

== Overall status #status

||= Tickets \\'Type: Task' \\'Milestone: `$YEAR` WP' =|| [[TicketQuery(type=Task, milestone=`$YEAR` WP, format=progress)]][[TicketQuery(type=Task, milestone=`$YEAR` WP, format=table, order=summary, col=id|summary|owner|workplan_status|workplan_comment)]] ||

== Add an action

See [wiki:Developers/DevelopingCodeChanges the instructions page] to learn how to implement a development work in NEMO.

Append 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.

[[Include(wiki:PageTemplates/WorkPlan/FormCode)]]

__Reminders__
* Action name pattern: `{INSTITUTE for specific actions, STREAM or WORKING_GROUP for shared actions}-{action number}_{PI(S)}-{keyword(S)}`
  * Current Working Groups: [wiki:WorkingGroups/AGRIF AGRIF] | [wiki:WorkingGroups/nemo_ConfigurationManager CONFIGMAN] | [wiki:WorkingGroups/NEMO_HPC HPC] | [wiki:WorkingGroups/Robustness-TestCases ROBUST] | [wiki:WorkingGroups/Wave_Coupling WAVE]
  * Current Streams: Enhancement | Publication | Validation
* Ticket \\
  * Default properties: 'Type: Task' and 'Milestone: `$YEAR` WP'
  * Custom fields 'Workplan status' & 'Comments' will be queried to display [#status the actions status table]
  * 'Cc': add users or email(s) for further notification.
  * The other fields in the ticket (e.g. 'Priority', 'Keywords') should also be set appropriately.