DPDK community structure changes
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "moving@dpdk.org" <moving@dpdk.org>
Subject: [dpdk-moving] Tomorrow's "Moving DPDK to Linux Foundation" Meeting
Date: Mon, 20 Mar 2017 20:43:43 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA72323F06@IRSMSX108.ger.corp.intel.com> (raw)

I don't like having meetings without a clear purpose, so I'd propose that we cancel tomorrow's meeting as there isn't anything specific to cover. If anybody else has topics they'd like to discuss and thinks we should go ahead, please feel free to say, otherwise I'll cancel it for this week.

For the press release, the LF team are working on this and will share a draft with the moving@dpdk.org mailing list when it's ready for broader review.

For membership discussions, these mostly seem to be at the stage where they're still being approved internally and/or being discussed between the member companies and the LF, so there isn't much we can say in a public meeting. The deadline we gave is next Monday (27th), so we'll be able to review the numbers at next week's meeting.

For the lab proposal, we're still working on this, but it is moving slowly. We need to get to the stage where we have a full proposal including costs that this larger group can then review. That's still a few weeks away.

If there are any other questions or issues, we can always use the moving@dpdk.org list.


Tim

             reply	other threads:[~2017-03-20 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 20:43 O'Driscoll, Tim [this message]
2017-03-30 23:25 ` Thomas Monjalon
2017-03-31 16:29   ` 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=26FA93C7ED1EAA44AB77D62FBE1D27BA72323F06@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=moving@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).