| Version 9 (modified by nicolasmartin, 9 years ago) (diff) |
|---|
ROBUST-10 Evolution of Collaborative Development Environment
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
Preview discussions
Comments from Previewer 1: Andrew Coward: The task description and background context is well explained and the implementation plan appears to be well formulated. However, this is a difficult plan for system team officers to preview since we are, at best, 'knowledgable users' of the Source Code Management and TRAC systems and we have little experience of installing and configuring them. I am happy to rely on Nicolas' expertise for that but it is clear that we must all contribute to content and design decisions at some stages. The plan, as written, lacks clarity as to when critical points will be reached that require collective effort. I suggest adding a Gantt chart with the best estimates of when tasks will be completed and showing when greater involvement from the system team may be necessary. This will help NEMO officers to schedule their commitments accordingly. Is there an opportunity here to ensure that the new system is more compatible with FCM so that we can avoid all the 'property change' commits that plague the current system? Does anyone have ideas how to do that? Also, it would be good to remove the reference manual PDF from any commits but have it rebuilt automatically if anything in DOC is changed. Can we add hook scripts to do that? Comments from Previewer 2: Simona Flavoni: I agree with the idea of removing moderation (less of work), but I've just a question. Nemo mailing list will disappear, so we will loose aid of users that sometimes answer to questions? or not? Or probably users will use intensively discussions to exchange informations by each other? If all questions will be done with the creation of a ticket, and these tickets are visible only by nemo_st... that implies that only nemo_st members will answer to tickets? Comments from Previewer 3: Clement Bricaud I agree with the idea to simplify the web site and to gather all the others functionalities linked to the nemo developers and ST in the wiki. I am ok to remove the nemo@... and to transfer it in tickets and forum. all the tickets will be visible by all users ? |
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.
