DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of June 19
Date: Tue, 2 Jul 2019 13:55:52 +0000	[thread overview]
Message-ID: <BYAPR18MB2424438B3473FC858861362BC8F80@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)

Meeting notes for the DPDK technical board meeting held on June 19 2019

Attendees:
        - Bruce Richardson
        - Ferruh Yigit
        - Hemant Agrawal
        - Jerin Jacob
        - Maxime Coquelin
        - Olivier Matz
        - Thomas Monjalon
        - Konstantin

1) Reviewed Userspace CFP's. Selected the CFPs. TB to update CFP's acceptance/rejection to submitters.
2) Ray to send presentation and documentation on DPDK API stability based on the inputs from subgroup and schedule a community call to review.
3) TB to review tooling community survey feedback and Honnappa to send DPDK community result to mailing list.
4) Next meeting will be on 3rd-July 19 and Konstantin  will chair it

Thanks,
/Jerin.

                 reply	other threads:[~2019-07-02 13:55 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=BYAPR18MB2424438B3473FC858861362BC8F80@BYAPR18MB2424.namprd18.prod.outlook.com \
    --to=jerinj@marvell.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).