Changes between Version 61 and Version 62 of Developers


Ignore:
Timestamp:
2018-11-09T14:55:11+01:00 (20 months ago)
Author:
clevy
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developers

    v61 v62  
    1919The NEMO reference code is available through official releases following some precise developement plan and quality control processes.The NEMO reference is under the responsibility of the NEMO System Team.[[BR]] 
    2020 
    21 All suggestions or developments from the community are welcome and can be announced in one of the forums.[[BR]] 
     21=== A piece of software that you want to share: 
     22You 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:[[BR]] 
     23You 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. [[BR]] 
     24To publicise this information, please add a topic in the [forum:5  Alternative configurations, repositories and utilities] forum 
    2225 
    23 A development can be eligible for the NEMO reference. If so, this task should be added to NEMO development annual work plan.[[BR]] 
    24 As a first step,a ticket should be opened to describe the development and its implementation, so as the existing validations.[[BR]] 
    25 This ticket will be examined by NEMO Developer's Committee to decide if the development is relevant and useful for the NEMO shared reference.[[BR]] 
    26 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 intial developer to be completed. 
    27  
    28 The different options to inform, share and eventually implement your developments in the NEMO reference are  described below: 
    29  
    30 === A piece of software that you want to share: 
    31 * You have developed a tool related to NEMO (pre- or post-processing), please add a topic in the [forum:5  Alternative configurations, repositories and utilities] forum 
    32  
    33 * You have a new development of NEMO, and believe it is of interest for the community, but you're not ready to do more. You are welcome to [https://forge.ipsl.jussieu.fr/nemo/newticket?summary=&type=ENHANCEMENT&component=ALL&version=release-3.6&severity=minor&keywords=&cc=&description=&milestone=&priority=low&owner=systeam&sfp_email=&sfph_mail=  create a ticket here] and attach the routines you have developped to your new ticket. 
    34  
    35 === A contribution the the NEMO reference 
    36 You developed a new piece in NEMO, 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]] 
     26=== A contribution to the NEMO shared reference 
     27You 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]] 
    3728This very good idea needs a little more work, from you and also from the NEMO System Team in charge of NEMO development. 
    3829 
    39 As a first step, you should, as above, open a ticket here: [[BR]] 
    40 describing the development. Please create it with a "TASK" type, so that the NEMO Developer's Committee can take it in account. 
     30As 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]] 
     31Once 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]] 
     32Once 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. 
    4133 
    42 Listing 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: 
    43 * The overall coherency with NEMO development strategy 
    44 * Coding rules, performances 
    45 * Documentation (in the code, on-line and reference manual) 
    46 * Building the development branch in phase with latest NEMO release 
    47 * 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) 
     34 
     35 
     36(*) 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: 
     37 * The overall coherency with NEMO development strategy 
     38 * Coding rules, performances 
     39 * Documentation (in the code, on-line and reference manual) 
     40 * Building the development branch in phase with latest NEMO release 
     41 * 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) 
    4842 
    4943The 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. 
    5044 
    51  
    52 === Development activities 
    53  
    54 * [wiki:2018WP Yearly Workplan] 
    55 * WorkingGroups 
    56 * [attachment:wiki:Users:NEMO_Development_Strategy_Version2_2018-2022.pdf NEMO Development Strategy document Version2 - 2018-2022] 
    57 * [attachment:wiki:Users/private:NEMO_Development_Strategy_Version2_2018-2022.pdf Development Strategy Version 1] (accessible after authentication) 
    58  
     45=== More on the sustainable development workflow 
    5946Document your developments before coding by following the procedure described at [wiki:Developers/DevelopingCodeChanges] 
    60  
    61 === Support 
    6247 
    6348* [wiki:Developers/WorkingOnTickets] 
     
    6550* [wiki:Developers/SVNHowTo] 
    6651 
    67 === Forums 
    68  
    69 Discussion 
    70  
     52==== Mailing lists 
    7153* If you want to follow a particular resource, set your email in [/prefs your preferences] and follow the instructions: 
    7254  * Wiki: click on 'Watch page' in the contextual menu. 
     
    7658* (|mail|) [https://listes.ipsl.fr/sympa/info/nemo-forge           forge@nemo-ocean.eu]: to be notified of each event on this platform (repository commits, ticket creation/update and forums messages).\\ 
    7759  ''Very high traffic recommended for all developers'' 
     60=== Overview on NEMO development activities 
    7861 
     62* [wiki:2018WP Yearly Workplan] 
     63* WorkingGroups 
     64* [attachment:wiki:Users:NEMO_Development_Strategy_Version2_2018-2022.pdf NEMO Development Strategy document Version2 - 2018-2022] 
     65* [attachment:wiki:Users/private:NEMO_Development_Strategy_Version2_2018-2022.pdf Development Strategy Version 1] (accessible after authentication) 
     66 
     67 
     68 
     69 
     70