| Version 14 (modified by nicolasmartin, 8 years ago) (diff) |
|---|
${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}
Per institute, the NEMO Officer creates a wiki page for each action of the yearly workplan using this template. The pattern for the page name to place it in the workplan tree with is wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}.
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.
Help
The action has to be detailed briefly in the 'Summary' sub-page (ordinary wiki page) for later inclusion in the 'Shared Actions' or institute page. Out of this, the rest of the page can be edited on-line inside the form fields considering the color code, record your modifications by clicking on the 'Save ...' button at the end of the section. This is the color code for the fulfilment of different sections of this form:
PI(S) | |
|---|---|
Previewer(s) | |
Reviewer(s) |
Apart from 'Summary' section (inclusion of sub-page), the informations inside the form fields and this wiki page itself are stored in 2 separate databases. As a consequence, there is absolutely no risk to make any modification in the page itself as long as you don't change the page name and the content of {{{TracForm ... }}} processors.
If you edit it in a classical way, use textearea instead of wysiwyg view because it doesn't handle well the Trac processors {{{#!th ... }}} or {{{#!td ... }}}. To keep a preview, you can tick the box edit side-by-side at top right of the editing frame. Your default view depends on your last editing work so can be changed in a simple manner.
Summary
Link for editing the summary:ExtractUrl(./Summary)?
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.
