Merge pull request #2 from dat-adi/updates

docs: December 2020 Update

content/updates/december2020.md

@@ -0,0 +1,34 @@
++++
+title = "December 2020"
+weight = 40
++++
+
+# December 2020
+## Northstar
+
+As the development on [Northstar](@/services/northstar.md) nears the completion phase,
+updates on it have slowed down, and the only updates that were made during this
+stage mostly comprises of configuration updates.
+These updates were mostly related to bootstrapping [DynaConf](https://www.dynaconf.com/), 
+as we embraced 12-factor app configuration recommendations, allowing for better 
+configuration management.
+
+## Interface
+
+Realising the need for validation of a request to an actor, an authentication 
+mechanism was developed to implement Matrix's [signed JSON](https://github.com/matrix-org/python-signedjson)
+feature, but, was later replaced in favor of [HTTP Signatures](https://tools.ietf.org/html/draft-cavage-http-signatures).
+
+Interface underwent major refactoring to improve test-ability and reliability in addition 
+to implementing authentication by a [signed JSON](https://github.com/matrix-org/python-signedjson)
+mechanism implemented by the Matrix project. Taking note of rate-limits imposed by some forges, 
+we figured we'd have to cache responses and so data persistence was implemented by way of 
+storing in a database.
+
+## References
+These are a list of the Pull Requests where the following updates took place for the
+organization.
+
+- Forking Implementation :: [#34](https://github.com/forgeflux-org/interface/commit/5c9f61d60ce069963da7abc761b9ba3d81c8883a)
+- Authentication :: [#36](https://github.com/forgeflux-org/interface/commit/5cc206cbe5be83cedac14949a537baad4c6351e3)
+- DB Refactor :: [#39](https://github.com/forgeflux-org/interface/commit/57c9a085b38f8c3bab7975e18d21e4455ad3cac9), [#40](https://github.com/forgeflux-org/interface/commit/d9d785ca116e9a2bb9a40cf3eaa16a8b275d1593)

content/updates/november2020.md

@@ -5,13 +5,11 @@ weight = 40
 
 # November 2020
 
-Errors were modularized at the back of [Northstar](https://github.com/forgeflux-org/northstar/).
-A Docker CI was set up for the Northstar builds.
+Errors were modularized at the back of [Northstar](https://github.com/forgeflux-org/northstar/),
+and A Docker CI was set up for the Northstar builds.
 
-A [GitHub organization](https://github.com/forgeflux-org) was created for ForgeFedv2, and the repositories for the projects were
-transferred over to it.
-
-A majority of the development on Interface was done during this time.
+A [GitHub organization](https://github.com/forgeflux-org) was created for ForgeFedv2,
+and the repositories for the projects were transferred over to it.
 
 A Notification-Event Translation Mechanism was set up.
 

content/updates/october2020.md

@@ -4,10 +4,13 @@ weight = 40
 +++
 
 # October 2020
-In the month of October, there were significant changes to the development in ForgeFedv2.
-Starting off with the addition of the [OpenAPI Specification](https://forgeflux-org.github.io/northstar/) for Northstar.
+
+In the month of October, there were significant changes to the development
+in ForgeFedv2, with the addition of the [OpenAPI Specification](https://forgeflux-org.github.io/northstar/)
+for Northstar.
 
 ## Northstar
+
 A database model was created to store the details of the various forge interfaces,
 having these details would be a prerequisite to looking up a server.
 
@@ -15,15 +18,18 @@ Endpoints were subsequently created, following the defined OpenAPI specification
 While the Lookup service was in the process of development, terminologies and the
 concept for Forge Federation was also being [discussed](https://github.com/forgeflux-org/spec/tree/master/rfc).
 
-Docker support as part of the CI process was added into the mix.
-Keeping in mind, that the test suite was the method to work with the application for
-the time being, an initial working model for the lookup service was established.
+Docker support as part of the CI process was added into the mix, while
+keeping in mind, that the test suite was the method to work with the application for
+the time being.
+An initial working model for the lookup service was established.
 
 ## Interface
-Development of the `libgit` library had begun.
+
+Development of the `libgit` library had begun at this point.
+
 [libgit] is a library that processes the contributor's changes, and generates a patch.
 Details regarding the implementation and feature set of libgit will be covered in another section.
 
-
 ## References
-- Database Initialization :: [database init](https://github.com/forgeflux-org/northstar/commit/6a82a1bc83d4733a5a077e33ad0c222aed496145)
+
+-   Database Initialization :: [database init](https://github.com/forgeflux-org/northstar/commit/6a82a1bc83d4733a5a077e33ad0c222aed496145)

content/updates/september2020.md

@@ -4,6 +4,7 @@ weight = 40
 +++
 
 # September 2020
+
 In the month of September, project "ForgeFedv2" started off by
 initializing the lookup service, [Northstar](https://github.com/forgeflux-org/northstar/).