governance-sigs/1cd850dda66584f1ac362ace04740adb756290dd

{
  "comments": [
    {
      "unresolved": false,
      "key": {
        "uuid": "03a29577_0f292c3a",
        "filename": "/PATCHSET_LEVEL",
        "patchSetId": 6
      },
      "lineNbr": 0,
      "author": {
        "id": 7198
      },
      "writtenOn": "2022-06-23T17:16:35Z",
      "side": 1,
      "message": "I support adding this group.  I do think we should decide if this is going to be an OpenInfra level project or just OpenStack.  I think having it at the OpenInfra level as Julia suggests makes sense for the long term success of the group.",
      "revId": "1cd850dda66584f1ac362ace04740adb756290dd",
      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
    },
    {
      "unresolved": false,
      "key": {
        "uuid": "57b0391c_b2ada921",
        "filename": "/PATCHSET_LEVEL",
        "patchSetId": 6
      },
      "lineNbr": 0,
      "author": {
        "id": 5314
      },
      "writtenOn": "2022-07-08T13:40:44Z",
      "side": 1,
      "message": "I think we should get this started as an OpenStack SIG, and if it meets with success, there\u0027s nothing preventing the Foundation from supporting an OpenInfra-wide SIG on the same topic that incorporates efforts from other OpenInfra projects.\n\nI share Kendall\u0027s worry from earlier reviews that if we don\u0027t get this started with a focused effort, it may not gain much traction.  There\u0027s plenty of work for us to do in OpenStack, for example, I\u0027ve always thought of the multi-arch SIG effort to get arm64 into the OpenStack CI pipeline as an environmental effort given the lower power consumption of ARM processors.  My opinion is: start the SIG and let\u0027s see what happens.",
      "revId": "1cd850dda66584f1ac362ace04740adb756290dd",
      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
    },
    {
      "unresolved": false,
      "key": {
        "uuid": "8f309b30_00aba9df",
        "filename": "/PATCHSET_LEVEL",
        "patchSetId": 6
      },
      "lineNbr": 0,
      "author": {
        "id": 8556
      },
      "writtenOn": "2022-07-08T19:17:32Z",
      "side": 1,
      "message": "some feedback from knikolla in IRC: https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2022-06-30.log.html#t2022-06-30T16:06:10",
      "revId": "1cd850dda66584f1ac362ace04740adb756290dd",
      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
    },
    {
      "unresolved": false,
      "key": {
        "uuid": "9075c1e8_735fef60",
        "filename": "/PATCHSET_LEVEL",
        "patchSetId": 6
      },
      "lineNbr": 0,
      "author": {
        "id": 8556
      },
      "writtenOn": "2022-07-08T19:19:35Z",
      "side": 1,
      "message": "Just to record voting, As mentioned in my earlier comments, I am in favor of making it a Open Infra level effort/group to have wider visibility and involve all OpenInfra projects not just OpenStack.",
      "revId": "1cd850dda66584f1ac362ace04740adb756290dd",
      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
    },
    {
      "unresolved": false,
      "key": {
        "uuid": "33b182cf_b53af7b3",
        "filename": "/PATCHSET_LEVEL",
        "patchSetId": 6
      },
      "lineNbr": 0,
      "author": {
        "id": 17068
      },
      "writtenOn": "2022-07-11T10:08:07Z",
      "side": 1,
      "message": "Regardless on how we intend to do it, please make sure we are inclusive.\nThis was discussed as a first step. So if we change the first step without linking to the next, it is possible to lose people on the way. In other words: it would be nice if people can follow the next steps from here  😊.\nOverall, I am happy with the scope.\n\nFor the record, I think Sylvain\u0027s point is well phrased and could deserve to be part of the scope explicitly (at least item 1).",
      "revId": "1cd850dda66584f1ac362ace04740adb756290dd",
      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
    },
    {
      "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"
    },
    {
      "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"
    },
    {
      "unresolved": true,
      "key": {
        "uuid": "9c3c84d2_4dc93806",
        "filename": "sigs.yaml",
        "patchSetId": 6
      },
      "lineNbr": 355,
      "author": {
        "id": 5314
      },
      "writtenOn": "2022-07-08T13:40:44Z",
      "side": 1,
      "message": "nit: unrelated change",
      "revId": "1cd850dda66584f1ac362ace04740adb756290dd",
      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
    }
  ]
}