From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] Minutes of Technical Board meeting 2020-09-09
Date: Thu, 10 Sep 2020 07:54:05 +0000 [thread overview]
Message-ID: <acc6ffbe3813415787b5efdfb7e32a20@intel.com> (raw)
Members Attending:
-------------------
Bruce Richardson
Ferruh Yigit
Honnappa Nagarahalli
Jerin Jacob
Kevin Traynor
Konstantin Ananyev
Maxime Coquelin
Olivier Matz
Stephen Hemminger
Thomas Monjalon
The technical board meetings takes place every second Wednesday on IRC channel #dpdk-board, at 3pm UTC. Meetings are public and DPDK community members are welcome to attend.
NOTE: Technical Board meetings for 2020-08-12 and 2020-08-26 were cancelled due to holidays in August.
Minutes
--------
#1 Reminder to all Techboard members to volunteer as moderators for session in the virtual DPDK Userspace event later this month.
#2 Requiring unit tests for contributions to DPDK:
* Discussion focused mainly on the areas of flow APIs and similar areas of DPDK which cannot be tested easily using "dpdk-test" unit test binary
* Concern was expressed about DTS usability, and lack of widespread use in developer community.
* Concern was also raised about mandating tests for features while DTS is in a separate repo from DPDK - and which uses a separate patch mailing list.
* **Action for all Techboard members**: Evaluate DTS to determine the usability pain-points and be able to discuss plan to improve it.
#3 Development of unit tests at UNH:
* Many of the same concerns raised as in previous discussion
* Flow APIs would be one area where more work would be needed
* Improvements to DTS itself was felt to be the highest priority initially
* Currently lacking specifics of tasks to be undertaken, this needs to be prepared before any work can start
* No volunteer from Techboard right now to take responsibility for directing that effort.
* **Action for all Techboard members**: members to attend the regular CI meetings whenever possible
* **Action**: Kevin to forward invite to all TB members (done)
#4 Request for Technical Writer to help with DPDK documentation:
* Spec for work was already started over email previously
* **Action**: Bruce to take existing discussion emails and begin document based on that.
Other items deferred for next meeting.
---
Next meeting will be on 2020-09-23, and will be chaired by Ferruh.
reply other threads:[~2020-09-10 7:54 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=acc6ffbe3813415787b5efdfb7e32a20@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=techboard@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).