wiki:Developers

NEMO Development activities

Overview of NEMO development process

NEMO is a free licence software, so anyone can use and develop NEMO for its own purposes.
The NEMO reference code is available through official releases following some precise development plan and quality control processes.The NEMO reference is under the responsibility of the NEMO System Team.

Notification

Mailing lists

  • If you want to follow a particular resource, set your email in your preferences and follow the instructions:
    • Wiki: click on 'Watch page' in the contextual menu.
    • Forum: subscribe to a topic from the topic list or a subject from the messages list.
    • Ticket: add your ID in the 'Cc' field.
  • mail forge@nemo-ocean.eu: to be notified of each event on this platform (repository commits, ticket creation/update and forums messages).
    Very high traffic recommended for all developers

More on the sustainable development workflow

Document your developments before coding by following the procedure described at Developers/Developing Code Changes

Hack

You have a new development, and believe it is of interest for the community, but you're not ready to do more. All suggestions or developments from the community are welcome and can be announced in one of the forums:
You have developed a tool related to NEMO (pre- or post-processing), or an addition ot the NEMO source code and would like to infor the NEMO community.
To publicise this information, please add a topic in the Alternative configurations, repositories and utilities forum

Contribution to the NEMO shared reference

You have a new development, done initially for your own purpose and you think it would be useful for you and/or the community to add it into the NEMO reference.
This very good idea needs a little more work, from you and also from the NEMO System Team in charge of NEMO development.

As a first step, you should to create a ticket here. This ticket should describe the development and its implementation, so as the existing validations.
Once the enhancement ticket is created, it will be examined by NEMO Developer's Committee (*) to decide if the development is relevant and useful for the NEMO shared reference.
Once the approval of Developer's Committee is sent, the development action can be added into the NEMO development yearly work plan and will need a contribution from the initial developer to be completed.

(*) Adding a development action in the NEMO reference development plan is decision with strong implications: first criteria is of course the scientific interest, but the amount of work needed to successfully meet the quality control requirements has also to be evaluated. This concerns:

  • The overall coherency with NEMO development strategy
  • Coding rules, performances
  • Documentation (in the code, on-line and reference manual)
  • Building the development branch in phase with latest NEMO release
  • Validation phase: checking that the development does what is expected, and that it is not breaking any existing feature (in terms of natural, computer sciences and of performances)

The NEMO System Team will ask you to contribute to the implementation work in the NEMO reference: you will be the PI of this action with the perspective of merging this new development by the end of civil year, during the so-called "Merge Party" meeting. If you agree with this perspective, you will be contacted by a member of NEMO System Team who will help you through the different development steps.

Last modified 3 days ago Last modified on 2018-11-12T17:01:10+01:00