DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: DPDK Techboard <techboard@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2020-01-15
Date: Mon, 3 Feb 2020 15:53:16 +0100	[thread overview]
Message-ID: <9c634fb7-dadf-7b97-f4a7-b71d34551a5a@redhat.com> (raw)

Minutes of Technical Board Meeting, 2020-01-15

Members Attending
-----------------
- Ferruh
- Kevin
- Bruce
- Konstantin
- Thomas
- Hemant
- Maxime (Chair)
- Olivier
- Stephen
- Jerin
- Honnappa

NOTE: The technical board meetings every second Wednesday on IRC
channel  #dpdk-board, at 3pm UTC. Meetings are public and DPDK community
members  are welcome to attend.

NOTE: Next meeting will be on Wednesday 2020-01-29 @3pm UTC, and will be
chaired by Olivier.

1) Estimation of the rework needed for the new vDPA devices class
 - Matan already posted the rework, including moving IFC driver
 - Main driver impacted will be Mellanox
 - LTSes maintainers are fine with the rework
 - Thomas applied the rework to master branch, so that Matan can post
   the Mellanox vDPA series

2) Action request for Thomas to add approved e-mail IDs to the security
   pre-release mailing list
 - Done by Thomas

3) UNH Lab decisions
 - Technical Board proposed to have member companies to assign people to
   add more tests in UNH Lab.
 - The Governing Board approved the proposal for one quarter.
 - Top contributing companies will be asked to assign one contributor
   for 20% FTE.
 - Thomas volunteered to manage this trial

4) Kubernetes integration status
 - Proposal to write a blog post about DPDK status in Kubernetes and
   plans
 - Maxime volunteered to write this blog post
 - Draft review target on 2020-02-12 Techboard meeting

5) ABI check tooling
 - Question about where/whether to store ABI dumps
 - Techboard agrees it should not be stored in main DPDK git repo
 - Techboard voted to have the ABI check being done by the CI with
   scripts provided in DPDK git repo, vs. ABI check done at build time
 - No decision yet by the Techboard on whether the ABI dumps for the
   releases should be stored somewhere, or generated each time


                 reply	other threads:[~2020-02-03 14:53 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=9c634fb7-dadf-7b97-f4a7-b71d34551a5a@redhat.com \
    --to=maxime.coquelin@redhat.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).