Update patch set 1

Patch Set 1: Code-Review-1

(1 comment)

Patch-set: 1
Reviewer: Gerrit User 5314 <5314@4a232e18-c5a9-48ee-94c0-e04e7cca6543>
Label: Code-Review=-1, 65f6309676f77003f203306c06a3e5b9cb4250df
This commit is contained in:
Gerrit User 5314 2024-03-21 15:03:20 +00:00 committed by Gerrit Code Review
parent f286a16237
commit 0730046ee2
1 changed files with 17 additions and 0 deletions

View File

@ -34,6 +34,23 @@
"parentUuid": "291e66b1_ae38426c",
"revId": "648bbc76f91542ef62dcf9e44f979c7181dc1b16",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": false,
"key": {
"uuid": "d761e016_5308673b",
"filename": "/PATCHSET_LEVEL",
"patchSetId": 1
},
"lineNbr": 0,
"author": {
"id": 5314
},
"writtenOn": "2024-03-21T15:03:20Z",
"side": 1,
"message": "Sylvain is correct. This patch, if merged, would put 5 people affiliated with Red Hat on the TC, and 5/9 \u003e 1/2, which would violate the TC diversity requirement. So unless one of the Red Hat people bows out and creates a vacancy (the highest-ranking non-elected candidate is not affiliated with Red Hat), the current TC will have to temporarily waive the diversity requirement, or come up with some other solution consistent with the TC charter. In any case, proposed patch to tc.yaml can\u0027t be merged yet.\n\nI suggest separating out ptl.yaml onto a separate patch so it can be merged right away, and then the tc.yaml can be handled separately.",
"revId": "648bbc76f91542ef62dcf9e44f979c7181dc1b16",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
}
]
}