From: "Dumitrescu, Cristian" <email@example.com>
To: "Wiles, Keith" <firstname.lastname@example.org>,
Yuanhan Liu <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>,
Jerin Jacob <firstname.lastname@example.org>
Subject: Re: next technical board meeting, 2017-04-10
Date: Mon, 10 Apr 2017 14:43:42 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891265278A980@IRSMSX108.ger.corp.intel.com> (raw)
It will start in 15 mins.
> -----Original Message-----
> From: dev [mailto:email@example.com] On Behalf Of Wiles, Keith
> Sent: Monday, April 10, 2017 3:34 PM
> To: Yuanhan Liu <firstname.lastname@example.org>
> Cc: email@example.com; firstname.lastname@example.org; Jerin Jacob
> Subject: Re: [dpdk-dev] next technical board meeting, 2017-04-10
> Did this meeting take place and meet quorum?
> What is the out come of the meeting?
> > On Apr 10, 2017, at 1:49 AM, Yuanhan Liu <email@example.com>
> > 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 <firstname.lastname@example.org>
> >>> To: email@example.com
> >>> Cc: firstname.lastname@example.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
> >> # 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 14:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 9:41 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 ` next technical board meeting, 2017-04-10 Yuanhan Liu
2017-04-10 14:34 ` Wiles, Keith
2017-04-10 14:43 ` Dumitrescu, Cristian [this message]
2017-04-10 14:54 ` Wiles, Keith
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.