Form page for development work
Help
A wiki page associated with a give action should be created in wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PI} using this template.
For the creation of the page of the editing of the template itself (Trac links for !ticket & source), it is mandatory to visualize it in 'textarea' view and not in 'wysiwyg' view as it will alter the interpretation of the Trac processors #!th ... or #!td ... in the complex tables.
To avoid it and keep a preview, you can enable the side-by-side edition (tick box 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 to 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.
Apart form this, each editor complete its section inside the form fields and save its modifications by clicking on the 'Save' button at the end of the section, the date and the author of the last edition will be updated above it.
There is absolutely no risk to make any operation on the wiki page itself and especially delete last version or submit a new one. The content of the form fields are recorded and singled out by the URL of the wiki page, the form context ('Abstract'/'Preview'/'Tests'/'Review') and subcontext (fields name).
From that, you can customize it while editing within the TracForm container {{{#!TracForm ... }}}. If necessary, you can copy the entire form (add a number _[0-9] to wiki page name) or the respective area in order to match the number of the (P)Reviewer(s). The best solution is not to extend significantly the length of the page.
This is the color code for the fulfilment of this form:
PI(S) | Previewer(s) | Reviewer(s) |
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.
