All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Neary <dneary-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "O'Driscoll,
	Tim" <tim.o'driscoll-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"dev-VfR2kkLFssw@public.gmane.org"
	<dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: DPDK Community Call - Beyond DPDK 2.0
Date: Fri, 01 May 2015 18:42:28 -0400	[thread overview]
Message-ID: <55440154.7020502@redhat.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54D3158A-kPTMFJFq+rFP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>

Hi Tim,

When were you thinking of having the call?

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.

Thanks,
Dave.

On 05/01/2015 06:20 PM, O'Driscoll, Tim wrote:
> There's been a good discussion on the mailing list on the Beyond DPDK 2.0 thread. To supplement this, we'd like to have a community call for people to air their views, and to help progress things towards a conclusion. It'll be an open format, so people can bring up whatever issues they want, but some topics for discussion might include:
> - Decision-making process. What do we do if issues don't reach a conclusion on the mailing list? Does stalemate just mean no change, or do we need some other mechanism to decide? A good example of an issue that may not reach a clear conclusion is the proposal move to github, where some seem to be in favour and others against.
> - How do we encourage more contributors to DPDK?
> - What tool/process improvements do we need to make? Further discussion of github is one obvious example.
> 
> GoToMeeting Details:
> Please join my meeting from your computer, tablet or smartphone.
> https://global.gotomeeting.com/join/556212525
> 
> You can also dial in using your phone.
> Ireland +353 (0) 19 030 010
> 
> Access Code: 556-212-525
> 
> More phone numbers
> United States (Long distance): +1 (646) 749-3129
> Australia (Long distance): +61 2 8355 1020
> Austria (Long distance): +43 (0) 7 2088 1047
> Belgium (Long distance): +32 (0) 28 08 4368
> Canada (Long distance): +1 (647) 497-9353
> Denmark (Long distance): +45 (0) 69 91 89 28
> Finland (Long distance): +358 (0) 942 59 7850
> France (Long distance): +33 (0) 170 950 594
> Germany (Long distance): +49 (0) 692 5736 7317
> Italy (Long distance): +39 0 247 92 13 01
> Netherlands (Long distance): +31 (0) 208 080 219
> New Zealand (Long distance): +64 (0) 9 280 6302
> Norway (Long distance): +47 75 80 32 07
> Spain (Long distance): +34 911 82 9906
> Sweden (Long distance): +46 (0) 852 500 186
> Switzerland (Long distance): +41 (0) 435 0167 13
> United Kingdom (Long distance): +44 (0) 330 221 0088
> 
> Here's the time in a variety of time zones:
> 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
> 
> 

-- 
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

  parent reply	other threads:[~2015-05-01 22:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 22:20 DPDK Community Call - Beyond DPDK 2.0 O'Driscoll, Tim
     [not found] ` <26FA93C7ED1EAA44AB77D62FBE1D27BA54D3158A-kPTMFJFq+rFP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-05-01 22:42   ` Dave Neary [this message]
     [not found]     ` <55440154.7020502-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-02 18:01       ` O'Driscoll, Tim
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=55440154.7020502@redhat.com \
    --to=dneary-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=tim.o'driscoll-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.