From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: Minutes of Technical Board Meeting, 2022-06-29
Date: Mon, 11 Jul 2022 09:47:31 +0200 [thread overview]
Message-ID: <10218567.O52NOvI7LO@thomas> (raw)
Members Attending: 9/10
- Aaron Conole
- Bruce Richardson
- Honnappa Nagarahalli
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Maxime Coquelin
- Stephen Hemminger
- Thomas Monjalon (Chair)
NOTE: The Technical Board meetings take place every second Wednesday
on https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
NOTE: Next meeting will be on Wednesday 2022-07-13 @3pm UTC,
and will be chaired by Aaron.
1/ Actions from last meeting:
- Thomas to send an update of the security process
- Bruce to send a deprecation notice for the KNI example
- Looking for volunteers to start a doc intro based on the white paper
(note: we should include a reference to the white paper)
2/ Event in France:
- Discussed last details about the CFP, should be ready soon.
- There are attendee fees to avoid cancellations,
and early bird price to avoid late registrations.
- Hackathon will happen on September 6 with several topics
(static analysis, code coverage, coccinelle, vhost vulnerabilities)
- Open discussions with the Technical Board should happen
at the end of September 6 or 7 (agenda to be finalized)
3/ Technical writer hiring process:
- Will ask what could be a doc audit to an agency
- Position is still open
4/ Servers backup:
- Asking Linux Foundation for hosting of backups.
- Access should be granted to a group (techboard members?).
next reply other threads:[~2022-07-11 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 7:47 Thomas Monjalon [this message]
2022-07-11 9:27 ` Konstantin Ananyev
2022-07-11 9:39 ` Konstantin Ananyev
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=10218567.O52NOvI7LO@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).