diff --git a/1cd850dda66584f1ac362ace04740adb756290dd b/1cd850dda66584f1ac362ace04740adb756290dd
new file mode 100644
index 0000000..6d6bce3
--- /dev/null
+++ b/1cd850dda66584f1ac362ace04740adb756290dd
@@ -0,0 +1,27 @@
+{
+  "comments": [
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "534b5b7e_d2eb978f",
+        "filename": "sigs.yaml",
+        "patchSetId": 6
+      },
+      "lineNbr": 124,
+      "author": {
+        "id": 11655
+      },
+      "writtenOn": "2022-06-23T16:31:51Z",
+      "side": 1,
+      "message": "What if we put this as a collaboration directly at the overall foundation level and not just OpenStack? And by put, I mean not a decision among the TC, but the body just forms there.\n\nThat way, it is independent, and not tied to the OpenStack perception and overall \"business\" overhead that is OpenStack process.\n\nWe, as a larger community, should be crossing boundaries upfront and trying to work with projects like Kata, StarlingX, Edge Working Group, etc. Starting in just OpenStack likely means it will never leave OpenStack scope which I believe is a mistake for the effort.\n\nThe plus side of one layer up, is it can self organize however it really wants and could begin to collaborate immediately, where as process wise the iron is cooling because it is out of the forge (forum).\n\nIn a sense, given deliverables and scope, initial discussion participants at the forum, it sounds *far* more like an OpenInfra Edge Working Group like effort than an OpenStack effort.\n\nAnyhow, my $0.02.",
+      "range": {
+        "startLine": 123,
+        "startChar": 0,
+        "endLine": 124,
+        "endChar": 30
+      },
+      "revId": "1cd850dda66584f1ac362ace04740adb756290dd",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    }
+  ]
+}
\ No newline at end of file