Changes between Version 30 and Version 31 of Developers/DevelopingCodeChanges

Timestamp:

2016-04-06T12:23:36+02:00 (8 years ago)

Author:

clevy

Comment:

--

Developers/DevelopingCodeChanges

@@ -30 +30 @@
 Once the workplan has been approved, the code development is planned. The PI should create:
 
- * An '''associated wiki page''' to be created in `wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PI}` using this '''[wiki:PageTemplates/Devlt_Work_Form template]''', you can customize it while editing in the !TracForm container. The wiki page will describe:
+ * An '''associated wiki page''' to be created. Please follow carefully the following indications:
+   * '''Create page in `wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PI}` using this [wiki:PageTemplates/Devlt_Work_Form template], '''
+   * '''DO NOT switch to wyziwig mode '''(it blows up the fomat and automatic completion in the page)
+   * To faciltate your edition, click on "edit side by side" button on top left of the page
+
+  you can customize ithe page while editing in the !TracForm container. 
+
+ * The wiki page will describe:
+
    * Purpose, motivation and main tasks of the action
    * PI(S) & (P)Reviewer(s) name(s)
@@ -48 +56 @@
 
 Once the wiki page is completed by PI (detailed implementation plan), the PI will submit it to Previewer. The Previewer will discuss with PI to reach full agreement on detailed implementation plan (in a maximum of 2 weeks starting when PI submits wiki page to Previewer).[[BR]]The PI is responsible to give all requested details.[[BR]]The Previewer is responsible to check with all experts that implementation plan is indeed correct and compatible with the other developments going on in parallel during the year.  Objective is to avoid the need for a full rewriting at the end (which did happen sometimes previously)
+
 == Start the coding ==
 Once the Previewer has sent the green light (approval of detailed implementation plan and summary of changes in reference manual), the PI can created the corresponding  development branch. The branch should be created from the up to date version of NEMO as chosen for each year (usually the trunk at a give fixed revision for a give year, see minutes of NEMO System Team videoconferences.  Development can progress on this new branch.