From: Ferruh Yigit <ferruh.yigit@intel.com>
To: techboard@dpdk.org
Cc: dpdk-dev <dev@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of January 30
Date: Sun, 3 Feb 2019 17:46:50 +0000 [thread overview]
Message-ID: <596e6dd1-be23-638c-bf2f-d0e44767e4b8@intel.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2019-01-30
Attendees: 8/9
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Thomas Monjalon
1) Windows compilers for DPDK Windows Port
Techboard suggests using following tools for Windows development unless they are
proven to not satisfying our needs:
- Compiler: clang for Windows
- Build system: meson
- Development concerns:
- Windows port should use common code as much as possible
- If some part is not common for Windows, it needs to be reworked
- Thomas will spend some time on Windows code reviews
2) Community Survey on Tools and Process Pain Points
- Honnappa is managing the effort
- Will go with two surveys, first one is for collecting problem statement
- Second one will be for solutions
- Questions will be both open ended and multiple choice
- Deadline is February 6
3) Security Process
- A draft is prepared by Thomas, need to work more on details on steps
- Maxime will review draft and collect more information
- Progress will be discussed in next techboard meeting
4) Google Summer Of Code
- Stephen sent an email about it
- Deadline is close
- Maxime will follow the issue with Stephen
5) Next techboard meeting
- It will be on February 13
- Hemant Agrawal will chair it
6) Next Meeting
- Static Analysis Issues
- Security Process
- Google Summer Of Code
reply other threads:[~2019-02-03 17:46 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=596e6dd1-be23-638c-bf2f-d0e44767e4b8@intel.com \
--to=ferruh.yigit@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).