From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 814E3B6AB for ; Thu, 16 Apr 2015 12:38:57 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP; 16 Apr 2015 03:38:56 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,587,1422950400"; d="scan'208";a="481693325" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by FMSMGA003.fm.intel.com with ESMTP; 16 Apr 2015 03:38:55 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.2]) by IRSMSX103.ger.corp.intel.com ([169.254.3.129]) with mapi id 14.03.0224.002; Thu, 16 Apr 2015 11:38:53 +0100 From: "O'Driscoll, Tim" To: "dev@dpdk.org" Thread-Topic: Beyond DPDK 2.0 Thread-Index: AdB4KSdm1ftzhuzCQX2G2XNq9ZOWFA== Date: Thu, 16 Apr 2015 10:38:52 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA54D1A917@IRSMSX102.ger.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [dpdk-dev] Beyond DPDK 2.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2015 10:38:58 -0000 Following the launch of DPDK by Intel as an internal development project, t= he launch of dpdk.org by 6WIND in 2013, and the first DPDK RPM packages for= Fedora in 2014, 6WIND, Red Hat and Intel would like to prepare for future = releases after DPDK 2.0 by starting a discussion on its evolution. Anyone i= s welcome to join this initiative. =20 Since then, the project has grown significantly: - The number of commits and mailing list posts has increased steadily. - Support has been added for a wide range of new NICs (Mellanox support = submitted by 6WIND, Cisco VIC, Intel i40e and fm10k etc.). - DPDK is now supported on multiple architectures (IBM Power support in = DPDK 1.8, Tile support submitted by EZchip but not yet reviewed or applied)= . While this is great progress, we need to make sure that the project is stru= ctured in a way that enables it to continue to grow. To achieve this, 6WIND= , Red Hat and Intel would like to start a discussion about the future of th= e project, so that we can agree and establish processes that satisfy the ne= eds of the current and future DPDK community. We're very interested in hearing the views of everybody in the community. I= n addition to debate on the mailing list, we'll also schedule community cal= ls to discuss this. Project Goals ------------- = =20 Some topics to be considered for the DPDK project include: - Project Charter: The charter of the DPDK project should be clearly def= ined, and should explain the limits of DPDK (what it does and does not cove= r). This does not mean that we would be stuck with a singular charter for a= ll time, but the direction and intent of the project should be well underst= ood.=20 - Project Contributions: We want to continue to grow the size and diver= sity of the DPDK contributor community. - Project Presence: Maximise the impact of the DPDK project by ensuring = that it has a strong brand and industry perception. Growing awareness of DP= DK as a project is important to growing the community and giving people con= fidence in using DPDK as part of their product offerings. - Project Process: The project needs a clear decision making process to = resolve issues that don't reach a conclusion on the mailing list. =20 References to Open Source Projects ---------------------------------- =20 Governance structures for open source projects vary widely. For reference, = below are some examples with links to their governance info. Some are home = grown, while others avail of the infrastructure provided by organisations s= uch as the Linux Foundation. Some are more formal, while others are more li= ghtweight. Each approach has its advantages and disadvantages. DPDK (http://dpdk.org/): - Maintainers are listed in http://dpdk.org/browse/dpdk/tree/MAINTAINERS - Process for contributing is outlined in the "Contribute by sending patche= s" section of http://dpdk.org/dev Open vSwitch (http://openvswitch.org/): - Committer Grant/Revocation: http://openvswitch.org/development/committer-= grant-revocation/ - Committer Responsibilities: http://openvswitch.org/development/committer-= responsibilities/ =20 OpenStack (http://www.openstack.org/): - Governance Model: http://www.openstack.org/foundation/ - Technical Committee: http://www.openstack.org/foundation/tech-committee/ - Board of Directors: http://www.openstack.org/foundation/board-of-director= s/ - User Committee: http://www.openstack.org/foundation/user-committee/ =20 OpenDaylight (http://www.opendaylight.org/): - Linux Foundation - Governance: http://www.opendaylight.org/project/governance - Technical Steering Committee: http://www.opendaylight.org/project/governa= nce/tsc - Board of Directors: http://www.opendaylight.org/project/board-members =20 CloudStack (http://cloudstack.apache.org/): - Apache Foundation - Project Management Committee & Committers: http://cloudstack.apache.org/w= ho.html - The Apache Way: http://theapacheway.com/ QEMU (http://wiki.qemu.org/Main_Page): - Structure: http://wiki.qemu.org/Contribute/StartHere - Process: http://wiki.qemu.org/Contribute/SubmitAPatch U-Boot (http://www.denx.de/wiki/U-Boot/): - Maintainers: http://www.denx.de/wiki/U-Boot/Custodians - Process: http://www.denx.de/wiki/U-Boot/DevelopmentProcess - Guidelines: http://www.denx.de/wiki/U-Boot/Patches Thank you