= 2017 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:SystemTeam/ReportsAndDocuments:NEMO development strategy-2014.pdf" NEMO Development Strategy document]. The next 2 sections describe the 2017 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''' \\(''!2017WP/AGRIF-*'') =||= '''Configuration Manager''' \\(''!2017WP/CONFIGMAN-*'') =||= '''Enhancement''' \\(''!2017WP/ENHANCE-*'') =||= '''HPC''' \\(''!2017WP/HPC-*'') =||= '''Robustness''' \\(''!2017WP/ROBUST-*'') = ||= '''Wave Coupling''' \\(''!2017WP/WAVE-*'') =|| || [[TitleIndex(2017WP/AGRIF-, hideprefix, depth=0)]] || [[TitleIndex(2017WP/CONFIGMAN-, hideprefix, depth=0)]] || [[TitleIndex(2017WP/ENHANCE-, hideprefix, depth=0)]] || [[TitleIndex(2017WP/HPC-, hideprefix, depth=0)]] || [[TitleIndex(2017WP/ROBUST-, hideprefix, depth=0)]] || [[TitleIndex(2017WP/WAVE-, hideprefix, depth=0)]] || == Specific Actions [./SpecificActions] contains the other planned developments for the year, as agreed by all consortium members ||= [wiki:2017WP/CMCC CMCC actions] \\(''!2017WP/CMCC-*'') =||= [wiki:2017WP/CNRS CNRS actions] \\(''!2017WP/CNRS-*'') =||= [wiki:2017WP/INGV INGV actions] \\(''!2017WP/INGV-*'') =||= [wiki:2017WP/Mercator_Ocean Mercator Océan actions] \\(''!2017WP/Mercator_Ocean-*'') =||= [wiki:2017WP/Met_Office Met_Office actions] \\(''!2017WP/Met_Office-*'') =||= [wiki:2017WP/NOC NOC actions] \\(''!2017WP/NOC-*'') =|| || [[TitleIndex(2017WP/CMCC-, hideprefix, depth=0)]] || [[TitleIndex(2017WP/CNRS-, hideprefix, depth=0)]] || [[TitleIndex(2017WP/INGV-, hideprefix, depth=0)]] || [[TitleIndex(2017WP/Mercator_Ocean-, hideprefix, depth=0)]] || [[TitleIndex(2017WP/Met_Office-, hideprefix, depth=0)]] || [[TitleIndex(2017WP/NOC-, hideprefix, depth=0)]] || == Overall status #status ||= Tickets \\'Type: Task' \\'Milestone: 2017 WP' =|| [[TicketQuery(type=Task, milestone=2017 WP, format=progress)]][[TicketQuery(type=Task, milestone=2017 WP)]] || == Add an action 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. {{{#!td style="vertical-align: top" [[NewPage(id=WPAction, parent=wiki/2017WP, template=WorkPlanAction, placeholder=Wikipage name, button=Create action's wikipage)]] __Reminders__ * Wikipage name pattern: \\ `{WG for shared or INSTITUTE for specific actions}-{action number}_{PI(S)}-{keyword(S)}` * 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] }}} {{{#!td style="vertical-align: top" {{{#!html

}}} __Ticket fields setting__ \\ * 'Type: Task' and 'Milestone: 2017 WP' by default * 'Cc': add email(s) of people outside NEMO ST for further notification. * 'Component': the area the change is being targeted for. The other fields in the ticket (e.g. 'Priority', 'Keywords') should also be set appropriately. }}} See [wiki:Developers/DevelopingCodeChanges the instructions page] to learn how to implement a development work in NEMO.