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.
Developers/Homepage/Contribution (diff) – NEMO

Changes between Initial Version and Version 1 of Developers/Homepage/Contribution


Ignore:
Timestamp:
2018-11-12T16:05:39+01:00 (5 years ago)
Author:
nicolasmartin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Developers/Homepage/Contribution

    v1 v1  
     1=== A contribution to the NEMO shared reference 
     2 
     3You 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.[[BR]] 
     4This very good idea needs a little more work, from you and also from the NEMO System Team in charge of NEMO development. 
     5 
     6As a first step, you should to [https://forge.ipsl.jussieu.fr/nemo/newticket?summary=&type=enhancement&component=ALL&version=trunk&severity=minor&keywords=&cc=&description=&milestone=&priority=low&owner=systeam&sfp_email=&sfph_mail=  create a ticket here]. This ticket should describe the development and its implementation, so as the existing validations.[[BR]] 
     7Once 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.[[BR]] 
     8Once 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. 
     9 
     10(*) 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: 
     11 * The overall coherency with NEMO development strategy 
     12 * Coding rules, performances 
     13 * Documentation (in the code, on-line and reference manual) 
     14 * Building the development branch in phase with latest NEMO release 
     15 * 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) 
     16 
     17The 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.