From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Minutes of Technical Board Meeting, 2022-06-15
Date: Thu, 12 Jan 2023 20:37:30 -0800 [thread overview]
Message-ID: <20230112203730.3a2b7a99@hermes.local> (raw)
Members Attending
=================
11/11
- Aaron
- Bruce
- David
- Hemant
- Kevin
- Konstantin
- Maxime
- Nathan
- Olivier
- Stephen (chair)
- Thomas
NOTE: The technical board meetings are on every second Wednesday at
https://meet.jit.si/DPDK at 3 pm UTC. Meetings are public, and DPDK
community members are welcome to attend.
NOTE: Next meeting will be on Wednesday 2021-June-29 @3pm UTC, and will
be chaired by Thomas.
Agenda Items
============
1) DPDK Userspace Event
-----------------------
In last phases prior to announcement. Waiting for landing page, and CFP.
Will need quick approval from Technical Advisory Board.
(See follow up email for current status)
2) Bug smashing
---------------
Could we do this at userpace event? Who would own it?
Logistics support is needed. No volunteers from Technical Advisory Board at this time.
3) Tech Writer update
---------------------
None of the earlier candidates appeared to be a good fit.
One new candidate is being looked at.
May need to revise the rate (needs governing board approval).
4) Olivier resignation from Technical Advisory Board
----------------------------------------------------
Consensus from Technical Advisory Board is that Olivier is irreplaceable.
5) Motivating cleanups?
-----------------------
Lots of topics need addressing, and there is nowhere to point motivated
newcomers to get started. Need some process to acknowledge approval from
Technical Advisory Board for a rework items.
The list of items in roadmap is: https://core.dpdk.org/roadmap/
There are currently 13 items in "Nice to have" section.
Proposal is to use existing bugzilla to track these and assign owners.
https://bugs.dpdk.org/buglist.cgi?bug_severity=enhancement&bug_status=CONFIRMED&bug_status=IN_PROGRESS&product=DPDK
6) Bugzilla status
------------------
Ajit is owner, have not gotten status recently.
There are currently 246 DPDK open bugs.
https://bugs.dpdk.org/buglist.cgi?bug_status=__open__&product=DPDK
7) Security process
-------------------
Need two different processes based on severity level but this is not documented.
A few critical bugs may need to be done immediately, special release;
and non critical bugs can be done as part of release process.
8) Removal of KNI
-----------------
Should example be removed, replaced in future release.
9) Documentation
----------------
Missing a high level document about goals and scope of DPDK.
Can we reuse what in earlier white paper? Thomas to ask.
reply other threads:[~2023-01-13 4:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230112203730.3a2b7a99@hermes.local \
--to=stephen@networkplumber.org \
--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).