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 (diff) – NEMO

Changes between Version 58 and Version 59 of Developers


Ignore:
Timestamp:
2018-06-28T16:22:09+02:00 (4 years ago)
Author:
clevy
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Developers

    v58 v59  
    1 = Welcome to the NEMO development area 
     1= Welcome to the NEMO developers section 
    22 
    33[[PageOutline(2-3)]] 
    44 
    5 You should find here everything regarding the development and the support of the NEMO reference. 
     5[[BR]] 
     6[[BR]] 
     7[[BR]] 
     8[[BR]] 
     9[[BR]] 
     10[[BR]] 
     11[[BR]] 
     12[[BR]] 
    613 
    7 == Prerequisites 
     14== Overview of NEMO development process 
     15[[Color(if you have developments to share, please read this introductory section first,/lime)]] 
    816 
    9 === Become a NEMO developer 
     17NEMO is a free licence software, so that all the developments from the community are more than welcome.[[BR]] 
     18Still, since the NEMO reference is share by the whole community after a commonly agreed development and validation process, the developments to be added in the NEMO reference must follow a specific quality control process.[[BR]] 
     19The different levels of sharing for your developments are briefly described below, in order to help you find the best way(s) for your developments to reach to community. 
    1020 
    11 First and foremost, if you don't already have a user account then you have to '''[/register create it]'''. 
     21First and foremost, to be able to create a ticket or add a topic in a forum, if you don't already have a user account then you have to '''[/register create it]'''. 
    1222 
     23 
     24=== A piece of software related to NEMO, that you want to share: 
     25'''You have developed a tool for NEMO pre- or post-processing, you have a personal repository with files you would like to share''' with the community, etc... , please add a topic in the [forum:5  Alternative configurations, repositories and utilities] forum 
     26 
     27=== A development of NEMO code itself 
     28'''You developed a new piece in NEMO, for your own purpose and you now want to inform the community''', but you're not ready to do more. You are welcome to create a ticket here and attach the routines you have developped to your new ticket. 
     29 
     30newticket?summary=&type=ENHANCEMENT&component=ALL&version=trunk&severity=minor&keywords=&cc=&milestone=&priority=low&description=&owner=&sfp_email=&sfph_mail= 
     31 
     32'''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]] 
     33This very good idea needs a little more work, from you and also from the NEMO System Team in charge of NEMO development. 
     34 
     35As a first step, you should, as above, open a ticket here: [[BR]] 
     36describing the development. Please create it with a "TASK" type, so that the NEMO workplan discussions can take it in account. 
     37 
     38Listing 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: 
     39* The overall coherency with NEMO development strategy 
     40* Coding rules, performances 
     41* Documentation (in the code, on-line and refernce manual) 
     42* Building the development branch in phase with latest NEMO release 
     43* Validation phase, including checking this development is not braking any existing feature 
     44 
     45Considering the costs (efforts needed to implement development in the NEMO reference) and benefits, the NEMO System Team will eventually offer you to contribute to the implementation work in the NEMO reference. If so, the development will be added in the workplan of the year, 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. 
     46 
     47 
     48 
     49{{{#!comment 
     50 
     51Claire: j'ai enlevé cette table parce que je ne crois pas que cette différence entre Consortium members et autres soit pertinente ici: la difference est entre développements acceptés pour la référence de NEMO et les autres. A revoir si tu veux 
    1352[[Include(wiki:Developers/Homepage/Table)]] 
     53}}} 
     54 
     55=== Development activities 
     56 
     57* [wiki:2018WP Yearly Workplan] 
     58* WorkingGroups 
     59* [attachment:wiki:Users:NEMO_Development_Strategy_Version2_2018-2022.pdf NEMO Development Strategy document Version2 - 2018-2022] 
     60* [attachment:wiki:Users/private:NEMO_Development_Strategy_Version2_2018-2022.pdf Development Strategy Version 1] (accessible after authentication) 
     61 
     62Document your developments before coding by following the procedure described at [wiki:Developers/DevelopingCodeChanges] 
     63 
     64=== Support 
     65 
     66[wiki:Developers/WorkingOnTickets] 
     67 
     68=== Forums 
     69 
     70Discussion 
     71 
     72* If you want to follow a particular resource, set your email in [/prefs your preferences] and follow the instructions: 
     73  * Wiki: click on 'Watch page' in the contextual menu. 
     74  * Forum: subscribe to a topic from the topic list or a subject from the messages list. 
     75  * Ticket: add your ID in the 'Cc' field. 
     76 
     77* (|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).\\ 
     78  ''Very high traffic recommended for developers only.'' 
     79 
     80{{{#!comment 
     81 
     82Claire: pas convaincue que le paragraphe suivant doive être ici?? Je le vois plutôt dans Developing code changes? 
     83 
    1484 
    1585=== Recommended development installation 
     
    42112 
    43113==  
    44  
    45 === Development activities 
    46  
    47 * [wiki:2018WP Yearly Workplan] 
    48 * WorkingGroups 
    49 * [attachment:wiki:Users:NEMO_Development_Strategy_Version2_2018-2022.pdf NEMO Development Strategy document Version2 - 2018-2022] 
    50 * [attachment:wiki:Users/private:NEMO_Development_Strategy_Version2_2018-2022.pdf Development Strategy Version 1] (accessible after authentication) 
    51  
    52 Document your developments before coding by following the procedure described at [wiki:Developers/DevelopingCodeChanges] 
    53  
    54 === Support 
    55  
    56 [wiki:Developers/WorkingOnTickets] 
    57  
    58 === Forums 
    59  
    60 Discussion 
    61  
    62 * If you want to follow a particular resource, set your email in [/prefs your preferences] and follow the instructions: 
    63   * Wiki: click on 'Watch page' in the contextual menu. 
    64   * Forum: subscribe to a topic from the topic list or a subject from the messages list. 
    65   * Ticket: add your ID in the 'Cc' field. 
    66  
    67 * (|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).\\ 
    68   ''Very high traffic recommended for developers only.'' 
     114}}}