Update meta-security maintainers
cover Update meta-security maintainers
After discussing it with Marta, we have agreed to co-maintain meta-security and the other embedded layers that Armin had been previously maintaining. If the TSC is onboard with the handover this patch can be merged, and then we can start addressing the immediate concerns like whinlatter compatibility on master branch once repo access has been sorted out.
Scott Murray (1):
Update maintainers
README.md | 4 +- .../include/maintainers-meta-security.inc | 72 +++++++++---------- meta-hardening/README.md | 4 +- meta-integrity/README.md | 4 +- meta-tpm/README.md | 2 + .../distro/include/maintainers-meta-tpm.inc | 32 ++++----- 6 files changed, 63 insertions(+), 55 deletions(-)
Signature · 1 line
2.49.0
PATCH 1/1 Update maintainers
Add Marta and myself as maintainers for meta-security and the other embedded layers that Armin had been maintaining. To avoid Armin getting bugged about individual recipes, set the RECIPE_MAINTAINER variables to myself for now as a starting point that can be adjusted as things get more settled.
--- README.md | 4 +- .../include/maintainers-meta-security.inc | 72 +++++++++---------- meta-hardening/README.md | 4 +- meta-integrity/README.md | 4 +- meta-tpm/README.md | 2 + .../distro/include/maintainers-meta-tpm.inc | 32 ++++----- 6 files changed, 63 insertions(+), 55 deletions(-)
README.md +3 -1
@@ -88,7 +88,9 @@ Now you can just do 'git send-email origin/master' to send all local patches. For pull requests, please use create-pull-request and send-pull-request. -Maintainers: Open +Maintainers: +Scott Murray <[email protected]> +Marta Rybczynska <[email protected]> License
conf/distro/include/maintainers-meta-security.inc +36 -36
75 lines not on this page · raw message
meta-hardening/README.md +3 -1
@@ -76,7 +76,9 @@ $ git config format.subjectPrefix meta-hardening][PATCH Now you can just do 'git send-email origin/master' to send all local patches. -Maintainers: Open +Maintainers: +Scott Murray <[email protected]> +Marta Rybczynska <[email protected]> License =======
meta-integrity/README.md +3 -1
@@ -45,7 +45,9 @@ [email protected] mailing list. When submitting patches that way, make sure to copy the maintainer and add a "[meta-integrity]" prefix to the subject of the mails. -Maintainer: Open +Maintainers: +Scott Murray <[email protected]> +Marta Rybczynska <[email protected]> Table of Contents
meta-tpm/README.md +2 -0
@@ -70,6 +70,8 @@ $ git config format.subjectPrefix meta-security][PATCH Now you can just do 'git send-email origin/master' to send all local patches. Maintainers: +Scott Murray <[email protected]> +Marta Rybczynska <[email protected]> License
meta-tpm/conf/distro/include/maintainers-meta-tpm.inc +16 -16
@@ -19,20 +19,20 @@ # RECIPE_MAINTAINER:pn-<recipe name> = "Full Name <address@domain>" # # Please keep this list in alphabetical order. -RECIPE_MAINTAINER:pn-aircrack-ng = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-pcr-extend = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-tpm-quote-tools = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-libtpms = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-trousers = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-swtpm = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-openssl-tpm-engine = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-tpm-tools = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-tpm2-abrmd = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-tpm2-totp = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-tpm2-tcti-uefi = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-tpm2-tss-engine = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-tpm2-pkcs11 = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-tpm2-tss = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-tpm2-tools = "Armin Kuster <[email protected]>" -RECIPE_MAINTAINER:pn-ibmswtpm2 = "Armin Kuster <[email protected]>" +RECIPE_MAINTAINER:pn-aircrack-ng = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-pcr-extend = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-tpm-quote-tools = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-libtpms = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-trousers = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-swtpm = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-openssl-tpm-engine = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-tpm-tools = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-tpm2-abrmd = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-tpm2-totp = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-tpm2-tcti-uefi = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-tpm2-tss-engine = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-tpm2-pkcs11 = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-tpm2-tss = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-tpm2-tools = "Scott Murray <[email protected]>" +RECIPE_MAINTAINER:pn-ibmswtpm2 = "Scott Murray <[email protected]>"
Signature · 1 line
2.49.0
Richard Purdie
AppliedRe: [meta-security][PATCH 1/1] Update maintainers
Quoted 7 lines · Scott Murray
Add Marta and myself as maintainers for meta-security and the other embedded layers that Armin had been maintaining. To avoid Armin getting bugged about individual recipes, set the
RECIPE_MAINTAINERvariables to myself for now as a starting point that can be adjusted as things get more settled.Signed-off-by Scott Murray <[email protected]>
Quoted 8 lines
---
README.md | 4 +- .../include/maintainers-meta-security.inc | 72 +++++++++---------- meta-hardening/README.md | 4 +- meta-integrity/README.md | 4 +- meta-tpm/README.md | 2 + .../distro/include/maintainers-meta-tpm.inc | 32 ++++-----6 files changed, 63 insertions(+), 55 deletions(-)
I've merged this and made it official, thanks Scott and Marta.
Cheers,
Richard
Re: [meta-security][PATCH 1/1] Update maintainers
In reply to Scott MurrayHi Scott, Marta,
Thank you for taking maintainer roles for meta-security.
Armin also used to be a co-maintainer of meta-parsec. I don't know if you want to include yourselves there as well.
When you have access to all the repositories could you have a look at his PR: https://lore.kernel.org/all/[email protected]/
It's a breaking issue.
Thank you,
Anton
Re: [yocto-patches] [meta-security][PATCH 1/1] Update maintainers
Quoted 10 lines · Anton Antonov via lists.yoctoproject.org
Hi Scott, Marta,
Thank you for taking maintainer roles for meta-security. Armin also used to be a co-maintainer of meta-parsec. I don't know if
you want to include yourselves there as well.
When you have access to all the repositories could you have a look at
his PR:
https://lore.kernel.org/all/[email protected]/
It's a breaking issue.
Hello Anton,
Thank you. I have had a look at the patch and it looks correct, but will need at least to build-test.
Kind regards,
Marta
Re: [meta-security][PATCH 1/1] Update maintainers
Hello Martha,
Thank you for checking the patch.
I don't know if you already started running pipelines for meta-security. Armin used to have jobs building security-test-image which also includes Parsec and OE QA test suites for it.
Regards,
Anton
Re: [yocto-patches] [meta-security][PATCH 1/1] Update maintainers
Quoted 6 lines · Anton Antonov via lists.yoctoproject.org
Hello Martha,
Thank you for checking the patch.
I don't know if you already started running pipelines for meta-security. Armin used to have jobs building security-test-image which also includes Parsec and OE QA test suites for it.
The CI setup is still something we're discussing, but the plan is to keep doing that testing. It is possible, however, that we may merge some of the more immediately required changes for whinlatter compatibility with just manual testing for expediency.
Scott
Re: [yocto-patches] [meta-security][PATCH 1/1] Update maintainers
In reply to Anton AntonovQuoted 4 lines · Anton Antonov via lists.yoctoproject.org
Hi Scott, Marta,
Thank you for taking maintainer roles for meta-security.
Armin also used to be a co-maintainer of meta-parsec. I don't know if you want to include yourselves there as well.
Given the contents of the layer, that seems reasonable, we'll discuss making it official.
Quoted 2 lines
When you have access to all the repositories could you have a look at his PR: https://lore.kernel.org/all/[email protected]/
It's a breaking issue.
Okay. From looking at meta-parsec, I'm curious if your usecase for it is currentlty relying on the LAYERSERIES_COMPAT on master branch including scarthgap? I can see that potentially working for the moment with the recipes in the layer, but I'd prefer to drop it to simplify testing.
Thanks,
Scott