DPDK community structure changes
 help / color / mirror / Atom feed
From: Michael Dolan <mdolan@linuxfoundation.org>
To: Dave Neary <dneary@redhat.com>, Raghu <rmadabushi@linuxfoundation.org>
Cc: "moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] Reminder: Formerly discussed DPDK budget
Date: Mon, 31 Oct 2016 13:52:39 -0400
Message-ID: <CAFV=PSFQeXyKt6aS4mWLmRN=U9nE8rzpPY1SD55bXne3LNZ_WA@mail.gmail.com> (raw)
In-Reply-To: <58177E46.6050007@redhat.com>

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

Hi Dave, I'm not sure that budget is still relevant / accurate. When was
that created?

I thought the group wanted to explore a CI/test infrastructure and 1 event
per year only... did I misunderstand that? I'm copying Raghu from the LF
who will be helping to create budget estimates. I see marketing, websites,
trademark work in here that doesn't seem relevant. I only asked Raghu to
listen in to scope out CI/test infrastructure and an event.

---
Mike Dolan
VP of Strategic Programs
The Linux Foundation
Office: +1.330.460.3250   Cell: +1.440.552.5322  Skype: michaelkdolan
mdolan@linuxfoundation.org
---

On Mon, Oct 31, 2016 at 1:24 PM, Dave Neary <dneary@redhat.com> wrote:

> Hi,
>
> As a reminder and basis for our current discussions, this is the budget
> that the LF came up with during our previous discussions:
> https://docs.google.com/spreadsheets/d/1-3686Xb_jf4FtxdX8Mus9UwIxUb2vI_
> ppmJV5GnXcLg/edit#gid=302618256
>
> Thanks,
> Dave.
>
> --
> 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
>

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

  reply	other threads:[~2016-10-31 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 17:24 Dave Neary
2016-10-31 17:52 ` Michael Dolan [this message]
2016-10-31 18:52   ` Dave Neary

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='CAFV=PSFQeXyKt6aS4mWLmRN=U9nE8rzpPY1SD55bXne3LNZ_WA@mail.gmail.com' \
    --to=mdolan@linuxfoundation.org \
    --cc=dneary@redhat.com \
    --cc=moving@dpdk.org \
    --cc=rmadabushi@linuxfoundation.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

DPDK community structure changes

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/moving/0 moving/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 moving moving/ http://inbox.dpdk.org/moving \
		moving@dpdk.org
	public-inbox-index moving

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.moving


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git