add revised project planning

architecture.md

@@ -387,6 +387,20 @@ Whereas details of the implementation may need to be decided as the technical ch
 
 1.  [Implement a way to run online services emphasising user autonomy and portability](https://git.fediversity.eu/Fediversity/Fediversity/issues/347)
     - [deploying Fediversity applications](https://git.fediversity.eu/Fediversity/Fediversity/issues/99)
+    - [Initial internal user to kick-start feedback process](https://git.fediversity.eu/Fediversity/Fediversity/issues/225):
+        - automated provisioning of:
+            - [databases](https://git.fediversity.eu/Fediversity/Fediversity/issues/115)
+            - [object storage](https://git.fediversity.eu/Fediversity/Fediversity/issues/185)
+            - [virtual machines](https://git.fediversity.eu/Fediversity/Fediversity/issues/116)
+            - [DNS](https://git.fediversity.eu/Fediversity/Fediversity/issues/110)
+            - [admin accounts](https://git.fediversity.eu/Fediversity/Fediversity/issues/178)
+            - [SMTP service](https://git.fediversity.eu/Fediversity/Fediversity/issues/117)
+            - [email accounts](https://git.fediversity.eu/Fediversity/Fediversity/issues/118)
+            - [ephemeral state](https://git.fediversity.eu/Fediversity/Fediversity/issues/314)
+        - [specification published](https://git.fediversity.eu/Fediversity/Fediversity/issues/334)
+        - [ProxmoX back-end supports multiple users](https://git.fediversity.eu/Fediversity/Fediversity/issues/313)
+        - [user can have multiple deployments](https://git.fediversity.eu/Fediversity/Fediversity/issues/241)
+        - [users can update their deployment configurations](https://git.fediversity.eu/Fediversity/Fediversity/issues/158)
     - [application data back-ups](https://git.fediversity.eu/Fediversity/Fediversity/issues/123)
     - [migrating application data between hosting providers](https://git.fediversity.eu/Fediversity/Fediversity/issues/100)
 1.  [Disseminate our results by engaging the open-source community to further expand on work in this direction](https://git.fediversity.eu/Fediversity/Fediversity/issues/348)
@@ -408,20 +422,6 @@ Whereas details of the implementation may need to be decided as the technical ch
         - [knowledge base](https://git.fediversity.eu/Fediversity/Fediversity/issues/288)
         - [module upstreamed to nixpkgs](https://git.fediversity.eu/Fediversity/Fediversity/issues/333)
 1.  [Exploit our work by facilitating the sample use-case of web hosting organisations using an initial set of services](https://git.fediversity.eu/Fediversity/Fediversity/issues/349)
-    - [Initial internal user to kick-start feedback process](https://git.fediversity.eu/Fediversity/Fediversity/issues/225):
-        - automated provisioning of:
-            - [databases](https://git.fediversity.eu/Fediversity/Fediversity/issues/115)
-            - [object storage](https://git.fediversity.eu/Fediversity/Fediversity/issues/185)
-            - [virtual machines](https://git.fediversity.eu/Fediversity/Fediversity/issues/116)
-            - [DNS](https://git.fediversity.eu/Fediversity/Fediversity/issues/110)
-            - [admin accounts](https://git.fediversity.eu/Fediversity/Fediversity/issues/178)
-            - [SMTP service](https://git.fediversity.eu/Fediversity/Fediversity/issues/117)
-            - [email accounts](https://git.fediversity.eu/Fediversity/Fediversity/issues/118)
-            - [ephemeral state](https://git.fediversity.eu/Fediversity/Fediversity/issues/314)
-        - [specification published](https://git.fediversity.eu/Fediversity/Fediversity/issues/334)
-        - [ProxmoX back-end supports multiple users](https://git.fediversity.eu/Fediversity/Fediversity/issues/313)
-        - [user can have multiple deployments](https://git.fediversity.eu/Fediversity/Fediversity/issues/241)
-        - [users can update their deployment configurations](https://git.fediversity.eu/Fediversity/Fediversity/issues/158)
     - [Software ready for web hosts to take into production](https://git.fediversity.eu/Fediversity/Fediversity/issues/228):
         - [garbage collection of unallocated resources](https://git.fediversity.eu/Fediversity/Fediversity/issues/188)
         - [Nix-less bootstrap](https://git.fediversity.eu/Fediversity/Fediversity/issues/332)

fediversity.md

@@ -153,10 +153,10 @@ In order to deal with this, we will have to keep up with the change and at the s
 To give a clear view of what interdepencies we expect:
 
 1.  Project Management: will keep an overview of all other Work Packages.
-1.  Vertical partners: will offer a 'feedback loop' and feed to WP5
+1.  Vertical Hosting: will offer a 'feedback loop' and feed to WP5
 1.  Open calls and grant management: will feed back to the verticals and feed to WP5
 1.  Enhancement & Usability: will feed back to the verticals and feed to WP5
-1.  Outreach & Dissemination
+1.  Dissemination & Outreach
 
 This diagram graphically represents the relations:
 
@@ -733,5 +733,4 @@ Consortium members have been instructed to stay clear from project proposals fro
 
 # Overview of project displayed in a Gantt chart
 
-<!-- ![](Pictures/gantt-chart.png) -->
+![](https://git.fediversity.eu/Fediversity/meta/raw/branch/proposal-gantt/planning/gantt.svg)
-TODO