DPDK community structure changes
 help / color / mirror / Atom feed
From: Dave Neary <dneary@redhat.com>
To: moving@dpdk.org
Subject: Re: [dpdk-moving] Proposing to cancel tomorrow's "Moving DPDK to LF" call
Date: Mon, 20 Feb 2017 11:36:44 -0500	[thread overview]
Message-ID: <ce9a4f32-4a3c-3cfb-077c-bf484d16579d@redhat.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA722C05A9@IRSMSX108.ger.corp.intel.com>

Thanks Tim,

I think the main blocking factor at this stage is a budget refresh that
we can use as a basis for relative priorities for expenditure - which
will feed into funding level discussions.

Thanks,
Dave.

On 02/20/2017 09:26 AM, O'Driscoll, Tim wrote:
> I propose that we cancel tomorrow's call on "Moving DPDK to the Linux Foundation". The main item we need to talk about is the status of the membership discussions, and whether it's realistic to be ready for a project launch to coincide with ONS at the start of April. However, due to the LF's open source leadership summit last week and a public holiday in the USA today (Presidents' Day), I don't think much will have changed since our last discussion on this. Postponing this for a week will allow more time for 1:1 discussions to happen so that we have a full picture.
> 
> If anybody has any concerns, or other topics that they want to cover tomorrow, please comment. If there are no objections then we'll cancel tomorrow's meeting and discuss membership status next week instead.
> 
> 
> Tim
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338

  reply	other threads:[~2017-02-20 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 14:26 O'Driscoll, Tim
2017-02-20 16:36 ` Dave Neary [this message]
2017-02-20 22:51   ` 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=ce9a4f32-4a3c-3cfb-077c-bf484d16579d@redhat.com \
    --to=dneary@redhat.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).