From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] [dpdk-techboard] [DRAFT] DPDK techboard minutes of October 26
Date: Tue, 07 Nov 2017 04:08:32 +0100 [thread overview]
Message-ID: <11731528.D3DzaYynkh@xps> (raw)
Hi,
Here are the minutes of the last DPDK technical board meeting
held on 2017-10-26.
Attendees:
- Bruce Richardson
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Stephen Hemminger
- Thomas Monjalon
- Yuanhan Liu
1) update on ABI stability guidelines
Bruce takes the action to update the guidelines (or delegate this task),
according to recent techboard decision:
http://dpdk.org/ml/archives/dev/2017-October/079961.html
2) update on license discussion
The Linux Foundation made an audit about licenses.
Jan Blunck (as the current techboard representative) is supposed to meet
with them and propose an action plan.
It is going to be a long term plan.
3) The techboard is not allowed to disclose this item.
A private meeting will be organized.
4) next chair, recurring meeting date?
The next meetings should happen at a recurring fixed day and time.
A poll will be organized in the techboard.
Yuanhan will lead the next meeting.
A technical panel session will be organized during the US summit,
including a lot of techboard members.
reply other threads:[~2017-11-07 3:08 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=11731528.D3DzaYynkh@xps \
--to=thomas@monjalon.net \
--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).