From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of March 13
Date: Mon, 25 Mar 2019 22:36:06 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258013655FA9D@irsmsx105.ger.corp.intel.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2019-03-13.
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
0) Move TB meeting one hour earlier due to time change (3PM UTC)
1) Follow up on Community Survey on Tools and Process Pain Points
On time of meeting got 41 completed surveys
Decision to prolong deadline till March 23-rd, send more reminders to dpdk.org
and related communities (VPP, OVS) plus for TB member to send more reminders internally.
2) Status check on static code Analysis Issues
Ask Luca and John to evaluate at other possible tools (sonarcloud and LGTM).
Main criteria's to look at: number of issues found, ability to mark/stop false positives
Latest news - Coverity seems to be back online.
3) LF funding of interns
Currently looking for funding for 2 interns
GB budget working group will look for the options
4) define a minimum Qemu version dependency
Starting from 19.08 qemu 2.11 will be minimum supported version
5) Next techboard meeting(27 March)
- Maxime Coquelin will chair it
next reply other threads:[~2019-03-25 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 22:36 Ananyev, Konstantin [this message]
2019-03-25 22:36 ` Ananyev, Konstantin
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=2601191342CEEE43887BDE71AB977258013655FA9D@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@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).