| Version 9 (modified by nicolasmartin, 8 years ago) (diff) |
|---|
${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS}
A wiki page associated with a given action should be created in wiki/${YEAR}WP/${WORKING_GROUP|INSTITUTE}-${ACTION_NUMBER}_${PIS} using this template.Then, detail your action in the 'Summary' sub-page (ordinary wiki page).
From that, the rest of the page has to be edited on-line inside the colored form fields and submit your modifications by clicking on the 'Submit ...' at the end of the section.
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.
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.
