Conclude the ARC investigation for FCAS

Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>

docs/fcas/index.rst

@@ -93,7 +93,7 @@ Index
 ----
 
 .. toctree::
-    :maxdepth: 1
+    :maxdepth: 2
 
     creation_workflow
     creation_gram
@@ -103,3 +103,45 @@ Index
     solution_examples
     solution_probntec
     solution_techtool
+
+Conclusions
+----
+
+After understanding how effective the project can be in helping the Fedora
+Council achieve its strategic objective of doubling the number of active
+contributors present over a given period of time, the options for making the
+said service as useful as possible were explored. It was concluded that the
+historical data collected by the Datanommer from the Fedora Messaging bus 
+would be indeed helpful in tracking contribution activities and detailing on
+contribution statistics and that it should be theoretically possible for the
+team to implement such a service.
+
+Roadmap
+----
+
+- **Step 1** - Connect with the data scientists to understand which data 
+  elements need to be focused on
+- **Step 2** - Author codebase to obtain details on human-run and human-owned
+  legitimate accounts
+- **Step 3** - Author SQL queries for obtaining historical contribution
+  statistics per username 
+- **Step 4** - Author SQL queries for obtaining historical contribution
+  statistics per service
+- **Step 5** - Adapt the queries to create a service to obtain current and
+  future statistics
+- **Step 6** - Expose necessary endpoints or integrations on the dashboard for
+  the analytics
+- **Step 7** - Setup the staging environment for the dashboard in a limited
+  testing environment for inspection
+- **Step 8** - Deploy to the production environment after ironing out the
+  vertex cases for statistics and... PROFIT?
+
+Estimate of work
+----
+
+As this service makes active use of technologies that are already created and
+maintained such as Fedora Messaging, Datagrepper, Datanommer, FASJSON etc., 
+and assuming that the team that is to work on this down the road has people who
+are experienced in the aforementioned technologies, the service should not take
+any longer than two quarters to hit the staging environment and one more 
+quarter to make it to the production one.