| Version 76 (modified by nicolasmartin, 8 years ago) (diff) |
|---|
Form page for development work
Help
A wiki page associated with a given action should be created in wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PI} using this template. Each editor (PI/Previewer/Reviewer) complete its section inside the form fields and save its modifications by clicking on the 'Save' button at the end of the section (last modification record will be updated just above it).
This is the color code for the fulfilment of this form:
PI(S) | Previewer(s) | Reviewer(s) |
There is absolutely no risk for all form content to make any modification in the wiki page as long as you edit out of {{{TracForm ... }}} processor. The data of a form field is stored in a different database from the wiki page, so you can delete a version or submit a new one without danger.
For the Trac links to associated !ticket & development branch, it is mandatory to edit the page in textarea view. The wysiwyg view will alter the interpretation of the Trac processors {{{#!th ... }}} or {{{#!td ... }}} in the table.
To keep a preview, you can tick the box edit side-by-side at top right of the editing frame). It will part your screen with the editing view on the left and the automatic preview on the right so you can control your changes. If you get by default the 'wysiwyg' view, this is due to your last editing work and can be changed in a simple manner.
The PI is responsible to closely follow the progress of the action, and especially to contact NEMO project manager if the delay on preview (or review) are longer than the 2 weeks expected.
Abstract
This section should be completed before starting to develop the code, in order to find agreement on the method beforehand.
Once the PI has completed this section, he should send a mail to the previewer(s) asking them to preview the work within two weeks.
Preview
Since the preview step must be completed before the PI starts the coding, the previewer(s) answers are expected to be completed within the two weeks after the PI has sent his request.
For each question, an iterative process should take place between PI and previewer(s) in order to reach a "YES" answer for each of the following questions.
Once all "YES" have been reached, the PI can start the development into his development branch.
Tests
Once the development is done, the PI should complete this section below and ask the reviewers to start their review in the lower section.
Review
A successful review is needed to schedule the merge of this development into the future NEMO release during next Merge Party (usually in November).
Once review is successful, the development must be scheduled for merge during next Merge Party Meeting.
