DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Glynn, Michael J" <michael.j.glynn@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Subject: Re: [dpdk-dev] DPDK Community Call - 16.04 Retrospective - Wednesday	May 11th
Date: Tue, 10 May 2016 08:00:09 +0000	[thread overview]
Message-ID: <6A5E04BECFB4144EAFCF9EAE3B739A5355A502AD@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA6751C00C@IRSMSX108.ger.corp.intel.com>

Hi all
Just a reminder about the 16.04 Retrospective Call tomorrow. All the call-in details are provided in Tim's email below 

Chat then!
Mike 


-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim
Sent: Friday, April 29, 2016 3:09 PM
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK Community Call - 16.04 Retrospective - Wednesday May 11th

At the end of each release, we typically hold a retrospective within our development team to discuss what went well, what could be improved etc. For 16.04, we thought it would be a good idea to try doing this with the open source community, so that everybody involved in the project can provide their input and we can discuss any suggested improvements collectively.

Mike Glynn, who's our Program Manager for DPDK, will facilitate the discussion. John McNamara has gathered some stats on things like how many revisions patches typically went through etc., which we'll present to help initiate the discussion, but the meeting should mostly be an open discussion where people should feel free to suggest any improvements they think we should make.

If the approach is successful we can repeat it for future releases.


When:
London (United Kingdom - England)        Wednesday, May 11, 2016 at 4PM    BST  UTC+1 hour     
San Jose (USA - California)              Wednesday, May 11, 2016 at 8AM    PDT  UTC-7 hours    
Boston (USA - Massachusetts)             Wednesday, May 11, 2016 at 11AM   EDT  UTC-4 hours    
Paris (France - Île-de-France)           Wednesday, May 11, 2016 at 5PM    CEST UTC+2 hours    
New Delhi (India - Delhi)                Wednesday, May 11, 2016 at 8:30PM IST  UTC+5:30 hours 
Shanghai (China - Shanghai Municipality) Wednesday, May 11, 2016 at 11PM   CST  UTC+8 hours    
Tokyo (Japan)                            Midnight between Wednesday, May 11 and Thursday, May 12 JST  UTC+9 hours    


GoToMeeting details:
Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/634498213

You can also dial in using your phone. 
United States : +1 (312) 757-3117

Access Code: 634-498-213

More phone numbers
Australia : +61 2 8355 1039
Austria : +43 7 2088 1033
Belgium : +32 (0) 28 93 7001
Canada : +1 (647) 497-9379
Denmark : +45 69 91 89 33
Finland : +358 (0) 942 41 5770
France : +33 (0) 170 950 585
Germany : +49 (0) 692 5736 7303
Ireland : +353 (0) 19 030 050
Italy : +39 0 693 38 75 50
Netherlands : +31 (0) 208 080 208
New Zealand : +64 9 925 0481
Norway : +47 21 54 82 21
Spain : +34 911 82 9890
Sweden : +46 (0) 853 527 817
Switzerland : +41 (0) 435 0167 65
United Kingdom : +44 (0) 330 221 0099

  reply	other threads:[~2016-05-10  8:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 14:08 O'Driscoll, Tim
2016-05-10  8:00 ` Glynn, Michael J [this message]
2016-05-12 10:45 ` Glynn, Michael J

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=6A5E04BECFB4144EAFCF9EAE3B739A5355A502AD@IRSMSX106.ger.corp.intel.com \
    --to=michael.j.glynn@intel.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).