DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: DPDK Techboard <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of Dec 4
Date: Fri, 13 Dec 2019 14:03:01 +0000	[thread overview]
Message-ID: <c57918f7-cf33-9bb8-01b2-c7682c39b954@redhat.com> (raw)

Minutes of Technical Board Meeting, 2019-12-04

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

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 2019-12-18 @3pm UTC, and will be
chaired by Konstantin Ananyev

1) DPDK Testing.

In-house testing will continue to happen regardless of upstream project
labs due to HW.

Decision to increase participation in UNH labs. Will try to get further
resources from contributing companies and also discuss options with the
governing board. Thomas will draft some proposals for this.

Thanks,
Kevin.


                 reply	other threads:[~2019-12-13 14:03 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=c57918f7-cf33-9bb8-01b2-c7682c39b954@redhat.com \
    --to=ktraynor@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).