DPDK patches and discussions
 help / color / mirror / Atom feed
From: "St Leger, Jim" <jim.st.leger@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK.org Community Call - Sept 24 - Discuss Growth, Improvements
Date: Tue, 22 Sep 2015 07:14:48 +0000	[thread overview]
Message-ID: <00B2C372B6E6DA4FB04934511BF0564A3E94B1A7@FMSMSX114.amr.corp.intel.com> (raw)

I am going to host a community call on Thursday Sept 24 at 7:00am Pacific daylight time.  The conference call dial-in info via GoToMeeting is pasted below.  Here is the background and objective of the discussion.

The DPDK community continues to grow.  Here are some stats on the 2.1 release from August 17th:
=> 827 commits. A growth of ~50% over the 2.0 release.
=> 82 individual committers. A growth of ~33% over the 2.0 release.
The number of companies contributing has also continued to grow.

There is a strong desire to continue to grow and solidify the community. But the growth brings up the question of how the community is structured to scale.   Additionally, there are many private DPDK repositories across the industry (e.g. ARM ports, for example.)  There are a myriad of reasons why companies have elected to keep their DPDK code and ports private versus put them into the DPDK.org community. We as a community need to understand and explore these reasons and work towards enabling inclusion.

During this gathering I'd like to bring together the DPDK community including:
a) the DPDK code contributors,
b) the consumers of DPDK downstream (VNF vendors, etc.),
c) private branch DPDK creators/consumers, and
d) anyone else interested in the growth and future of the DPDK open source software project.

The call will focus on two topics:

1)    Structure for growth:

Do we have the community practices, policies, and procedures in place to allow us to continue to grow on our current trajectory?



2)    Gaps Limiting Participation:

What gaps do companies who would like to participate/contribute to DPDK.org see?

What changes would they like to see made to improve the project?

I hope people can attend AND that they will join and speak up and be heard. The success and growth of the community depends on YOU!

Thanks,
Jim
=========================================
DPDK Community Call

Thu, Sep 24, 2015 3:00 PM - 4:00 PM GMT Daylight Time
Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/766709085

You can also dial in using your phone.

Access Code: 766-709-085
Dial-in phone numbers
United States : +1 (312) 757-3117
Australia : +61 2 8355 1031
Austria : +43 (0) 7 2088 1033
Belgium : +32 (0) 28 93 7001
Canada : +1 (647) 497-9371
Denmark : +45 (0) 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) 20 3713 5010

             reply	other threads:[~2015-09-22  7:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22  7:14 St Leger, Jim [this message]
2015-09-23 21:00 ` Dave Neary
2015-09-23 23:56   ` St Leger, Jim
2015-09-24  8:36     ` Thomas Monjalon
2015-09-24  8:40       ` Simon Kågström
2015-09-24 15:35     ` Butler, Siobhan A
2015-09-28 20:44 ` 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=00B2C372B6E6DA4FB04934511BF0564A3E94B1A7@FMSMSX114.amr.corp.intel.com \
    --to=jim.st.leger@intel.com \
    --cc=dev@dpdk.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 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).