From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of July 29
Date: Thu, 03 Sep 2020 19:00:05 +0200 [thread overview]
Message-ID: <11512411.dF79g20n3X@thomas> (raw)
Minutes of Technical Board meeting, 2020-07-29
Members Attending: 11/11
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Honnappa Nagarahalli
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon (Chair)
NOTE: Technical Board meetings happen every second Wednesday
on IRC channel #dpdk-board, at 3pm UTC.
Meetings are public and DPDK community members are welcome to attend.
1/ awards
The nominees of the year were decided by the techboard.
They will be revealed during the online summit.
2/ online event schedule
The presenters of the accepted talks will be notified.
The talk durations must be confirmed to build the schedule.
3/ addition of NXP library inside DPDK
A library (fmlib) was submitted as part of net/dpaa.
It has been accepted in next-net by Ferruh,
and rejected from main tree by Thomas.
The reasons for initial reject were:
- code style not compatible with DPDK
- kernel module dependency
- doubt on the dual GPL+BSD license
This lib was forked for DPDK usage.
The original fmlib repository is in maintenance mode for legacy usages.
A header file is shared with the external kernel module (in NXP SDK).
The decision is to accept the library when code style will be fixed.
The dual license must be checked because there is some ambiguity
in whether it meets the criteria of the charter clause 6.i.iii.
4/ removal of dpdk-next-qos and dpdk-next-pipeline
The git trees "qos" and "pipeline" were created to share the load
of merging related patches, but they are not active enough to be kept.
It has been decided to hide these git trees
and unreference them from the MAINTAINERS file.
5/ design reviews
We need to encourage and accelerate adoption of new ideas.
Contributors must know technical direction to avoid wasting their time.
It has been decided to organize design meetings for complex features
or libraries. The recommended meeting tool is https://meet.jit.si/dpdk.
Experts of the topic should attend and give their opinions.
The exact decision process is to be defined.
reply other threads:[~2020-09-03 17:00 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=11512411.dF79g20n3X@thomas \
--to=thomas@monjalon.net \
--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).