From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Marta Rybczynska <rybczynska@gmail.com>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>,
yocto-security@lists.yoctoproject.org
Subject: Re: [docs] Documenting YP processes
Date: Wed, 18 Oct 2023 18:35:57 +0100 [thread overview]
Message-ID: <f296756f07267e29d23732acf41e7c799d7f4d22.camel@linuxfoundation.org> (raw)
In-Reply-To: <ef4d2c98-e7f2-4c3d-8a59-dd5d1e181dea@bootlin.com>
On Wed, 2023-10-18 at 16:57 +0200, Michael Opdenacker wrote:
> Hi Marta
>
> On 18.10.23 at 16:23, Marta Rybczynska wrote:
> > Hello,
> > I'm writing the "official" documentation for the YP security processes
> > and I'm realizing that I do not know which document to put it into.
> > There is no "YP Processes" manual. What about adding a "Security
> > manual"? It can then include:
> > - security processes
> > - a single place describing how to submit CVE fixes
> > - links to other manuals for relevant material and/or rewrites if necessary
>
> IMHO, it does makes sense to create a new "Security Manual". We
> currently have
> https://docs.yoctoproject.org/dev-manual/vulnerabilities.html with some
> useful details contributed over time, but a separate manual would
> probably get more of the attention this topic deserves.
I'm torn between a security section in the Development Manual or a
separate one. I don't think we want too many manuals so I have a slight
leaning to a section but am open to persuasion.
Cheers,
Richard
next prev parent reply other threads:[~2023-10-18 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 14:23 Documenting YP processes Marta Rybczynska
2023-10-18 14:57 ` [docs] " Michael Opdenacker
2023-10-18 17:35 ` Richard Purdie [this message]
2023-10-19 7:40 ` Marta Rybczynska
2023-10-19 9:02 ` Michael Opdenacker
2023-10-19 9:08 ` Richard Purdie
2023-10-19 9:10 ` Michael Opdenacker
2023-10-19 8:23 ` [yocto-security] " Rich Persaud
2023-10-19 9:52 ` Robert P. J. Day
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=f296756f07267e29d23732acf41e7c799d7f4d22.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.com \
--cc=rybczynska@gmail.com \
--cc=yocto-security@lists.yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.