From: Paul Barker <paul@pbarker.dev>
To: docs@lists.yoctoproject.org
Cc: Paul Barker <paul@pbarker.dev>,
Marta Rybczynska <marta.rybczynska@ygreky.com>
Subject: [PATCH v2 0/3] Security team documentation updates
Date: Wed, 03 Jun 2026 20:45:16 +0100 [thread overview]
Message-ID: <20260603-sec-team-v2-0-ee7d2016fbf4@pbarker.dev> (raw)
- Add myself to the security team in place of Steve Sakoman.
- Small tidy up and update of how we describe the security team
operations.
- Migrate the documentation of how we handle multi-project embargoes
from the wiki.
I've based this on top of v2 of Marta's patch to update her email
address [1] so that it is easier to apply.
[1]: https://lore.kernel.org/yocto-docs/20260603185843.44152-1-marta.rybczynska@ygreky.com/
---
Changes in v2:
- Rebase on v2 of Marta's patch.
- Drop "If an upstream project does not respond quickly" to a lower
heading level.
- Migrate multi-project embargo docs.
---
Paul Barker (3):
security-team: Update membership list
security-team: Tidy and update section on security team operations
security-team: Add section on multi-project embargoes
documentation/security-reference/security-team.rst | 50 ++++++++++++++--------
1 file changed, 31 insertions(+), 19 deletions(-)
---
base-commit: f57c4bb14c40fcd187f53042fd06d8cbef8f4e22
change-id: 20260603-sec-team-1c39909e383b
Best regards,
--
Paul Barker
next reply other threads:[~2026-06-03 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 19:45 Paul Barker [this message]
2026-06-03 19:45 ` [PATCH v2 1/3] security-team: Update membership list Paul Barker
2026-06-03 19:45 ` [PATCH v2 2/3] security-team: Tidy and update section on security team operations Paul Barker
2026-06-04 5:33 ` [docs] " Marta Rybczynska
2026-06-04 8:22 ` Paul Barker
2026-06-03 19:45 ` [PATCH v2 3/3] security-team: Add section on multi-project embargoes Paul Barker
2026-06-09 7:27 ` [PATCH v2 0/3] Security team documentation updates Antonin Godard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260603-sec-team-v2-0-ee7d2016fbf4@pbarker.dev \
--to=paul@pbarker.dev \
--cc=docs@lists.yoctoproject.org \
--cc=marta.rybczynska@ygreky.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox