Update patch set 6

Patch Set 6:

(1 comment)

Patch-set: 6
Attention: {"person_ident":"Gerrit User 11655 \u003c11655@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_8556\u003e replied on the change"}

1cd850dda66584f1ac362ace04740adb756290dd

@@ -39,6 +39,30 @@
       },
       "revId": "1cd850dda66584f1ac362ace04740adb756290dd",
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "a3610385_45546bd9",
+        "filename": "sigs.yaml",
+        "patchSetId": 6
+      },
+      "lineNbr": 124,
+      "author": {
+        "id": 8556
+      },
+      "writtenOn": "2022-06-23T17:23:11Z",
+      "side": 1,
+      "message": "True, i mentioned the same in my earlier reply that starting it in OpenStack can end up with being in OpenStack only and yes need to follow the OpenStack process as SIG:\n\n1. SIG guideline: https://governance.openstack.org/sigs/reference/sig-guideline.html\n\n2. Best practices for running a SIG: \nhttps://governance.openstack.org/sigs/reference/sig-guideline.html#best-practices-for-running-a-sig\n\nAnd I feel that not all these process are required to do this work. Starting it at the OpenInfra level will help to avoid more process, global visibility, overahead of change-things-later, and most important risk of having-this-effort-in-openstack-only",
+      "parentUuid": "534b5b7e_d2eb978f",
+      "range": {
+        "startLine": 123,
+        "startChar": 0,
+        "endLine": 124,
+        "endChar": 30
+      },
+      "revId": "1cd850dda66584f1ac362ace04740adb756290dd",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
     }
   ]
 }