DPDK community structure changes
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, December 20th
Date: Wed, 11 Jan 2017 11:41:05 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA722A4EED@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1601867.Ux85OEMUxP@xps13>


> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, January 11, 2017 8:26 AM
> To: moving@dpdk.org; O'Driscoll, Tim <tim.odriscoll@intel.com>
> Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux
> Foundation" call, December 20th
> 
> 2016-12-21 15:55, O'Driscoll, Tim:
> > Next Meeting:
> > We'll resume again on Tuesday January 10th at 3pm GMT, 4pm CET, 10am
> EST,
> > 7am PST. We'll cover any additional (and hopefully final) comments on
> the
> > charter, and discuss next steps for determining project members.
> 
> I was attending the call yesterday (January 10) but I did not heard
> everything,
> especially when Ed was talking (probably because of his
> micro/bandwidth/echo).
> Please would it be possible to have a detailed transcription of the
> different
> opinions expressed, in the minutes?
> Thanks

Yes, will do. I could hear Ed OK, but it seems like some others couldn't. I'll send minutes later today and will clarify the opinions that were expressed during the call.

  reply	other threads:[~2017-01-11 11:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 15:55 O'Driscoll, Tim
2017-01-11  8:25 ` Thomas Monjalon
2017-01-11 11:41   ` O'Driscoll, Tim [this message]
2017-01-11 13:04 ` Dave Neary
2017-01-11 13:09   ` Vincent JARDIN
2017-01-11 22:23     ` O'Driscoll, Tim

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=26FA93C7ED1EAA44AB77D62FBE1D27BA722A4EED@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=moving@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    /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).