Changes between Version 40 and Version 41 of Developers/DevelopingCodeChanges

Timestamp:

2017-09-21T22:36:39+02:00 (7 years ago)

Author:

nicolasmartin

Comment:

--

Developers/DevelopingCodeChanges

@@ -12 +12 @@
 A brief overview of the process is given below.
 
-{{{#!div
+{{{#!div class="" style="text-align: center"
 {{{#!graphviz
+
 digraph {
-label = "Yearly Development Process"
-rankdir = LR
+label = "Yearly Development Process"; labelloc = t; rankdir = LR
 
-Workplan [ shape = egg      , label = "Workplan"   ]
-actA     [                    label = "Action A"   ]
-actB     [                    label = "Action B"   ]
-act      [ shape = plaintext, label = "..."        ]
-actx     [                    label = "Action ..." ]
-Plan  [ shape = box    , color = grey , label = "Development\nPlan"                ]
-Pre   [ shape = hexagon, color = blue , label = Preview                            ]
-Work  [ shape = box    , color = grey , label = "Coding &\nValidation"             ]
-Rev   [ shape = hexagon, color = green, label = Review                             ]
-Merge [ shape = tripleoctagon         , label = "Integration to\nNEMO main branch" ]
+Workplan [ shape = egg, label = "Workplan" ]
 
-Workplan -> actA; Workplan -> actB; Workplan -> act; Workplan -> actx
-actA -> Plan [ style = dotted ]
-actB -> Plan [ style = dotted ]
-act  -> Plan [ style = dotted ]
-actx -> Plan [ style = dotted ]
-Plan -> Pre -> Work -> Rev -> Merge
+subgraph clusterWorkflow {
+   label = "Worflow per action"; peripheries = 0; labelloc = b
+   Actions  [ shape = record, label = "<aA> Action A | <aB> Action B | <aC>Action C | <ai>... | <ax>Action ..." ]
+   Workflow [ shape = record, label = "{<Wi>Development Plan | Preview | Coding\n&\nValidation | <Wo>Review }"  ]
+   Branches [ shape = record, label = "<bA>Branch A | <bB>Branch B | <bC>Branch C | <bi>... | <bx>Branch x"     ]
+}
 
-subgraph Workflow { Plan; Pre; Work; Rev; Merge; label = "Action Workflow" }
-/*subgraph legend {
-   label = "Legend"
-   role[  shape = plaintext, label = "System Team"           , fontsize = 8 ]
-   role1[ shape = plaintext, label = "Principal Investigator", fontsize = 8 ]
-   role2[ shape = plaintext, label = "Previewer"             , fontsize = 8 ]
-   role3[ shape = plaintext, label = "Reviewer"              , fontsize = 8 ]
-   circle[  shape = circle, label = ""                ]
-   circle1[ shape = circle, label = "", color = grey  ]
-   circle2[ shape = circle, label = "", color = blue  ]
-   circle3[ shape = circle, label = "", color = green ]
-   circle->role [ nodesep = small ]
-   circle1->role1->circle2->role2->circle3->role3
-   }*/
+Workplan -> Actions:aA; Workplan -> Actions:aB; Workplan -> Actions:aC;
+Workplan -> Actions:ax; Workplan -> Actions:ai
+Actions:aA -> Workflow:Wi [ style = dotted ]; Actions:aB -> Workflow:Wi [ style = dotted ]
+Actions:aC -> Workflow:Wi [ style = dotted ]; Actions:ai -> Workflow:Wi [ style = dotted ]
+Actions:ax -> Workflow:Wi [ style = dotted ]
+Workflow:Wo -> Branches:bA [ style = dotted ]; Workflow:Wo -> Branches:bB [ style = dotted ]
+Workflow:Wo -> Branches:bC [ style = dotted ]; Workflow:Wo -> Branches:bi [ style = dotted ]
+Workflow:Wo -> Branches:bx [ style = dotted ]
+Branches:bA -> Merge; Branches:bB -> Merge; Branches:bC -> Merge; Branches:bi -> Merge; Branches:bx -> Merge;
+
+Merge [ shape = house, label = "Integration at\n\"NEMO Merge Party\"" ]
+
 }
+
 }}}
 }}}
@@ -60 +50 @@
 == Workplan content
 
-The yearly workplan is discussed within System Team, submitted to Developer's Committee, and approved by Steering Committee. It must include, for each development action, its motivation, status, main tasks so as a PI name, and a previewer (which will also be the reviewer) name. If needed, previewer can be divided into a "Science Previewer" and a "System Previewer". The name of Previewer should be added only once he did accept the task, and before submission of workplan to Developer's Committee.[[BR]]
+The yearly workplan is discussed within System Team, submitted to Developer's Committee, and approved by Steering Committee. It must include, for each development action, its motivation, status, main tasks so as a PI name, and a previewer (which will also be the reviewer) name. If needed, previewer can be divided into a "Science Previewer" and a "System Previewer". The name of Previewer should be added only once he did accept the task, and before submission of workplan to Developer's Committee.
 
 == Detailed description of implementation plan and Preview step