DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dave Neary <dneary@redhat.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Community Call - Linux Foundation
Date: Tue, 26 Jan 2016 10:49:34 -0500	[thread overview]
Message-ID: <56A7958E.3030807@redhat.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA674AA240@IRSMSX108.ger.corp.intel.com>

Hi Tim,

On 01/22/2016 07:19 PM, O'Driscoll, Tim wrote:
> At the community call we held on governance in December, we agreed that a few of us would work with the Linux Foundation on a proposal for a light-weight governance of DPDK. This would include things like management of DPDK events, registering trademarks, and any required legal support etc.
> 
> Stephen, Thomas, Dave, Vincent and I met with the Linux Foundation to discuss this and came up with a draft budget proposal. We'd like to have a community call to discuss this and decide how we should proceed.
> 
> The current budget estimate is ~$227k. LF guidance is that for this size of budget they'd propose a flat membership fee (i.e. no tiered membership) of ~$25k per member company, with a target of getting 10 or more companies to contribute.
> 
> At the call we can discuss:
> - A breakdown of the proposed budget. LF are very flexible on this, so we can add or remove whatever we want for DPDK.
> - Proposed membership fee.
> - Matthew also highlight some recent changes to community representation at the Linux Foundation. We should discuss any concerns associated with this.
> - Next steps.

Sounds good to me. All of the times below work. :-)

Thanks,
Dave.

> When: 
> Tue, Feb 2, 2015 15:00 - 16:00 GMT
> Tue, Feb 2, 2015 07:00 - 08:00 PST
> Tue, Feb 2, 2015 10:00 - 11:00 EST
> Tue, Feb 2, 2015 16:00 - 17:00 CET
> 
> 
> How to join:
> You can join from a computer, tablet or smartphone: https://global.gotomeeting.com/join/474154717
> 
> You can also dial in by phone.
> Access Code: 474-154-717
> 
> More phone numbers
> United States : +1 (312) 757-3126
> Australia : +61 2 9087 3604
> Austria : +43 7 2088 1400
> Belgium : +32 (0) 92 98 0592
> Canada : +1 (647) 497-9350
> Denmark : +45 69 91 80 05
> Finland : +358 (0) 942 41 5778
> France : +33 (0) 182 880 456
> Germany : +49 (0) 692 5736 7313
> Ireland : +353 (0) 15 290 180
> Italy : +39 0 247 92 12 39
> Netherlands : +31 (0) 208 080 379
> New Zealand : +64 9 442 7358
> Norway : +47 21 03 58 96
> Spain : +34 911 82 9782
> Sweden : +46 (0) 313 613 558
> Switzerland : +41 (0) 435 0006 96
> United Kingdom : +44 (0) 20 3713 5028
> 
> 

-- 
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:[~2016-01-26 15:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-23  0:19 O'Driscoll, Tim
2016-01-26 15:49 ` Dave Neary [this message]
2016-02-04 22:15 ` O'Driscoll, Tim
2016-02-05 16:30   ` Bob Monkman
2016-02-05 17:08     ` O'Driscoll, Tim
2016-02-05 17:20       ` Bob Monkman
2016-02-09 16:20         ` Dave Neary
  -- strict thread matches above, loose matches on Subject: below --
2015-12-10 23:01 O'Driscoll, Tim
2015-12-17 15:28 ` 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=56A7958E.3030807@redhat.com \
    --to=dneary@redhat.com \
    --cc=dev@dpdk.org \
    --cc=tim.odriscoll@intel.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).