DPDK patches and discussions
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.o'driscoll@intel.com>
To: Dave Neary <dneary@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Community Call - Beyond DPDK 2.0
Date: Sat, 2 May 2015 18:01:02 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA54D31A95@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <55440154.7020502@redhat.com>

> From: Dave Neary [mailto:dneary@redhat.com]
> 
> When were you thinking of having the call?

I put the day and time at the end of the email, but it probably should have been at the start! Apologies that this wasn't clear.

Dublin (Ireland) - Tuesday, May 12, 2015 at 4:00:00 PM IST UTC+1 hour
San Francisco (U.S.A. - California) - Tuesday, May 12, 2015 at 8:00:00 AM PDT UTC-7 hours
Phoenix (U.S.A. - Arizona) - Tuesday, May 12, 2015 at 8:00:00 AM MST UTC-7 hours
Boston (U.S.A. - Massachusetts) - Tuesday, May 12, 2015 at 11:00:00 AM EDT UTC-4 hours
New York (U.S.A. - New York) - Tuesday, May 12, 2015 at 11:00:00 AM EDT UTC-4 hours
Ottawa (Canada - Ontario) - Tuesday, May 12, 2015 at 11:00:00 AM EDT UTC-4 hours
London (United Kingdom - England) - Tuesday, May 12, 2015 at 4:00:00 PM BST UTC+1 hour
Paris (France) - Tuesday, May 12, 2015 at 5:00:00 PM CEST UTC+2 hours
Tel Aviv (Israel) - Tuesday, May 12, 2015 at 6:00:00 PM IDT UTC+3 hours
Moscow (Russia) - Tuesday, May 12, 2015 at 6:00:00 PM MSK UTC+3 hours
New Delhi (India - Delhi) - Tuesday, May 12, 2015 at 8:30:00 PM IST UTC+5:30 hours
Shanghai (China - Shanghai Municipality) - Tuesday, May 12, 2015 at 11:00:00 PM CST
UTC+8 hours Corresponding UTC (GMT) Tuesday, May 12, 2015 at 15:00:00

> It's not been explicit, but can I assume that this call will also be
> promoted among potential supporters of the project who may not be on
> this list? I would be interested to get the perspective from the people
> who are perhaps not developers who decide whether their organization
> engages strategically with a project or not.

I think this is a great idea. Anybody should feel free to pass this on to other interested parties. If we have more contributors to the discussion then the output should be more representative of current and future community needs.


Tim

  reply	other threads:[~2015-05-02 18:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 22:20 O'Driscoll, Tim
2015-05-01 22:42 ` Dave Neary
2015-05-02 18:01   ` O'Driscoll, Tim [this message]
2015-05-11 15:34     ` O'Driscoll, Tim
2015-05-13 11:19       ` O'Driscoll, Tim
2015-05-13 13:54         ` Dave Neary
2015-05-13 20:53           ` 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=26FA93C7ED1EAA44AB77D62FBE1D27BA54D31A95@IRSMSX102.ger.corp.intel.com \
    --to=tim.o'driscoll@intel.com \
    --cc=dev@dpdk.org \
    --cc=dneary@redhat.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).