DPDK community structure changes
 help / color / mirror / Atom feed
From: Ed Warnicke <hagbard@gmail.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: "Wiles, Keith" <keith.wiles@intel.com>,
	"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, January 24th
Date: Wed, 25 Jan 2017 09:30:32 -0700	[thread overview]
Message-ID: <CAFVSqg05tA+fUbYbQpb1rTVsAYThG2bqW5YNtg2Zb-RMBLuA8A@mail.gmail.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA722AFEEA@IRSMSX108.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]

Question... are you only pricing for *one* rack?  I ask, because *one* rack
can fill pretty quick...

Ed

On Wed, Jan 25, 2017 at 9:16 AM, O'Driscoll, Tim <tim.odriscoll@intel.com>
wrote:

> > From: Wiles, Keith
> >
> > Sent from my iPhone
> >
> > > On Jan 25, 2017, at 4:57 AM, O'Driscoll, Tim <tim.odriscoll@intel.com>
> > wrote:
> > >
> > >
> > > Membership costs:
> > > - Discussed potential membership costs. My proposal was ~$50-100k for
> > Gold, ~$5-$20k for Silver. Most agreed that this was a good starting
> > point for discussions.
> >
> > I thought we were trending toward the higher $100k range as the lab was
> > going cost a fair bit am I wrong here?
>
> The membership rates we decide on will need to strike a balance between
> raising budget and having a broad membership that's representative of the
> breadth of DPDK contributions/usage. If we choose a high figure it will
> limit the number of companies prepared to join. If we choose too low a
> number then we won't maximize our budget. We need to strike a balance
> between the two.
>
> The next step we agreed was for Mike to identify who's interested in
> membership (he's already posted on the moving list asking for contacts) and
> begin to have individual discussions with them. Feedback on membership
> rates from these discussions will help us to make a final decision.
>
> I think we need to be careful on lab costs. Some high figures have been
> mentioned based on FD.io, but from the beginning of these discussions we've
> agreed that we want a smaller scope and lower cost level for DPDK. Rough
> estimate for a full rack with a part time sys admin and a part time release
> engineer is ~$200k/year.
>
> We also discussed yesterday whether lab costs should be fully accounted
> for in the Gold membership fee, or if they should be handled separately.
> Mike will also ask about interest in the lab as part of his discussions
> which will help us to reach a conclusion on this.
>

[-- Attachment #2: Type: text/html, Size: 2511 bytes --]

  reply	other threads:[~2017-01-25 16:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 11:57 O'Driscoll, Tim
2017-01-25 15:48 ` Wiles, Keith
2017-01-25 16:16   ` O'Driscoll, Tim
2017-01-25 16:30     ` Ed Warnicke [this message]
2017-01-25 17:10       ` O'Driscoll, Tim
2017-01-25 17:29         ` George Zhao
2017-01-25 17:39           ` Zhu, Heqing
2017-01-25 18:06             ` O'Driscoll, Tim
2017-01-25 18:15               ` Michael Dolan
2017-01-26  1:33           ` Xu, Qian Q
2017-01-31 11:12 ` [dpdk-moving] changes in the Technical Board Thomas Monjalon
2017-01-31 11:55   ` Vincent Jardin
2017-01-31 13:16     ` Thomas Monjalon
2017-01-31 13:40   ` O'Driscoll, Tim
2017-02-06 12:53   ` [dpdk-moving] [dpdk-techboard] " Hemant Agrawal

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=CAFVSqg05tA+fUbYbQpb1rTVsAYThG2bqW5YNtg2Zb-RMBLuA8A@mail.gmail.com \
    --to=hagbard@gmail.com \
    --cc=keith.wiles@intel.com \
    --cc=moving@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).