From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: dev@dpdk.org, techboard@dpdk.org
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-dev] next technical board meeting, 2017-04-10
Date: Mon, 10 Apr 2017 14:49:33 +0800 [thread overview]
Message-ID: <20170410064933.GX18844@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <20170406100142.GA10609@jerin>
Hi all,
The last techboard meeting was canceled, and it's been rescheduled to
today, 10th Apr, at 3pm UTC. I should have sent it out a bit earlier.
Sorry!
The agenda remains the same (see below).
--yliu
On Thu, Apr 06, 2017 at 03:31:43PM +0530, Jerin Jacob wrote:
> -----Original Message-----
> > Date: Thu, 30 Mar 2017 15:11:07 +0530
> > From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> > To: dev@dpdk.org
> > Cc: techboard@dpdk.org
> > Subject: [dpdk-dev] next technical board meeting, 2017-04-06
> > User-Agent: NeoMutt/20170306 (1.8.0)
> >
> > Hello everyone,
> >
> > A meeting of the DPDK technical board will occur next Thursday,
> > April 6th 2017 at 9am UTC?
> >
> > The meeting takes place on the #dpdk-board channel on IRC.
> > This meeting is public, so anybody can join, see below for the agenda.
> >
> > Jerin
>
> The meeting got canceled due to lack of quorum.
> (6 out of 9 members were present, which is less than 70%(minimum quorum))
> # http://dpdk.org/about/techboard#meetings
>
> Yuanhan Liu volunteered to chair the next meeting.
> No particular date was agreed for next meeting.
>
> Yuanhan to follow on mail to select a date/time of next meeting.
>
> >
> > 1) Divergence between DPDK/Linux PF/VF implementations.
> >
> > Discussions:
> > http://dpdk.org/ml/archives/dev/2017-March/060529.html
> > http://dpdk.org/ml/archives/dev/2017-March/060063.html
> > http://dpdk.org/ml/archives/dev/2016-December/053056.html
> >
> > 2) Representative for the DPDK governance board
> >
> > 3) Scope of cmdline and cfgfile libraries in DPDK.
> > Discuss the scope of cmdline and cfgfile libraries in DPDK
> > and see if we allow more libs like that (Keith proposed a CLI lib),
> > or we do not do more,
> > or do we target to replace them by better external equivalents?
> >
> > 4) Community questions/issues
> >
> >
> >
next prev parent reply other threads:[~2017-04-10 6:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 9:41 [dpdk-dev] next technical board meeting, 2017-04-06 Jerin Jacob
2017-03-30 14:25 ` Wiles, Keith
2017-03-30 15:05 ` Olivier Matz
2017-03-30 15:51 ` Wiles, Keith
2017-03-30 16:03 ` Jay Rolette
2017-03-30 18:09 ` Dumitrescu, Cristian
2017-04-03 19:51 ` Stephen Hemminger
2017-04-03 22:53 ` Wiles, Keith
2017-04-04 1:28 ` Stephen Hemminger
2017-04-04 5:01 ` Vincent Jardin
2017-04-04 14:35 ` Wiles, Keith
2017-03-31 8:52 ` Olivier Matz
2017-03-31 9:31 ` Dumitrescu, Cristian
2017-03-31 14:24 ` Wiles, Keith
2017-03-31 14:39 ` Wiles, Keith
2017-04-06 10:01 ` Jerin Jacob
2017-04-10 6:49 ` Yuanhan Liu [this message]
2017-04-10 14:34 ` [dpdk-dev] next technical board meeting, 2017-04-10 Wiles, Keith
2017-04-10 14:43 ` Dumitrescu, Cristian
2017-04-10 14:54 ` Wiles, Keith
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=20170410064933.GX18844@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--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).