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.
2017WP – NEMO
wiki:2017WP

Version 38 (modified by nicolasmartin, 7 years ago) (diff)

--

2017 Workplan

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 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-*)

Specific Actions

SpecificActions contains the other planned developments for the year, as agreed by all consortium members

CMCC actions?
(!2017WP/CMCC-*)

CNRS actions
(!2017WP/CNRS-*)

INGV actions
(!2017WP/INGV-*)

Mercator Océan actions?
(!2017WP/Mercator_Ocean-*)

Met_Office actions
(!2017WP/Met_Office-*)

NOC actions
(!2017WP/NOC-*)

      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.

      NewPage(id=WPAction, parent=wiki/2017WP, template=WorkPlanAction, placeholder=Wikipage name, button=Create action's wikipage)? Reminders

      • Wikipage name pattern: {WG for shared actions or INSTITUTE for specific actions}-{action number}_{PI(S)}-{keyword(S)}
      • Current WG: AGRIF | CONFIGMAN? | ENHANCE | HPC? | ROBUST? | WAVE?

      Ticket fields setting

      • 'Type': 'Development'
      • 'Milestone' to current yearly WP
      • '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 the instructions page to learn how to implement a development work in NEMO.