summaryrefslogtreecommitdiff
path: root/about/charter.html
diff options
context:
space:
mode:
Diffstat (limited to 'about/charter.html')
-rw-r--r--about/charter.html631
1 files changed, 0 insertions, 631 deletions
diff --git a/about/charter.html b/about/charter.html
deleted file mode 100644
index 2b42e09..0000000
--- a/about/charter.html
+++ /dev/null
@@ -1,631 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
- <meta charset="utf-8" />
- <meta name=viewport content="width=device-width, initial-scale=1" />
- <title>DPDK Project Charter</title>
- <link rel="stylesheet" href="/reset.css" />
- <link rel="stylesheet" href="/layout.css" />
- <link rel="stylesheet" href="/content.css" />
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-39229303-1']);
- _gaq.push(['_setDomainName', 'dpdk.org']);
- _gaq.push(['_setAllowLinker', true]);
- _gaq.push(['_trackPageview']);
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = '//www.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
-</head>
-<body>
-<header>
- <h1><a href="//dpdk.org/"><img src="/logos/dpdk.png"
- alt="DPDK: Data Plane Development Kit"></a></h1>
- <nav>
- <ul>
- <li><a href="/">Home</a>
- <li><a href="/download">Download</a>
- <li><a href="/doc">Documentation</a>
- <li><a href="/dev">Development</a>
- <li><a href="/ml">Mailing Lists</a>
- <li><a href="/events">Events</a>
- <li><a href="/news">News</a>
- <li><a href="/about" id="current">About</a>
- </ul>
- </nav>
-</header>
-<section id="charter">
-<h1>Project Charter</h1>
-
-<h2 id="mission">Mission of the Data Plane Development Kit</h2>
-<p>
- The mission of DPDK is to:
-<ol>
- <li>
- Create an open source, production quality, vendor neutral
- software platform for enabling fast dataplane I/O,
- upon which users can build and run data plane applications.
- <li>
- Host the infrastructure for the DPDK community,
- establishing a neutral home for community assets,
- infrastructure, meetings, events and collaborative discussions.
-</ol>
-
-<h2 id="structure">Project Structure</h2>
-<p>
- The DPDK Project is comprised of
- one core software project which is DPDK itself,
- and a few smaller sub-projects that are closely related to DPDK.
-<p>
- The core DPDK project is comprised of a number of git repositories,
- including a master repository,
- several "next" repositories
- which are used to apply changes to specific parts of DPDK
- before these are pulled into the master repository,
- and a stable release repository.
- This structure is listed in
- the <a href= "/browse/">repository home page</a>.
-<p>
- The sub-projects that are also hosted as part of the DPDK Project
- are typically applications that are closely related to DPDK.
- These can be browsed in
- the <a href= "/browse/">repository home page</a>.
-<p>
- Changes to this structure, including approval for any new sub-projects,
- are the responsibility of the Technical Board
- (see <a href="#techboard">section 3.2</a> below).
-
-<h2 id="governance">Project Governance</h2>
-<p>
- Governance for DPDK will be provided by two boards:
-<ol>
- <li>
- A Governing Board which deals with budget, marketing,
- lab resources, administrative, legal and licensing issues.
- <li>
- A Technical Board which deals with technical issues
- including approval of new sub-projects, deprecating old sub-projects,
- and resolution of technical disputes.
-</ol>
-<p>
- These two boards are peers and work together to oversee the DPDK project.
-
-<h3 id="govboard">Governing Board</h3>
-
-<h4 id="govscope">Scope</h4>
-<p>
- The Governing Board covers the full scope of DPDK, including all sub-projects.
- Responsibilities of the Governing Board are:
-<ol>
- <li>
- Electing a Chair to preside over meetings,
- authorize expenditures approved by the Governing Board,
- and manage any day-to-day operations.
- <ol>
- <li>
- The Chair will be elected on an annual basis.
- <li>
- The existing Chair will be allowed to stand for re-election.
- </ol>
- <li>
- Approving an annual budget comprising funds raised by DPDK
- from all sources of revenue,
- and approving expenditures in compliance with that budget.
- <li>
- Overseeing all project business and marketing matters
- including planning and executing DPDK events.
- <li>
- Planning and management of all project lab resources.
- <li>
- Adopting and maintaining administrative policies and procedures for DPDK
- (subject to LF approval) including but not limited to a Code of Conduct,
- and a trademark policy.
- <li>
- Approving procedures for the nomination and election of
- (1) Silver Member representatives to the Governing Board,
- and (2) any officer or other positions created by the Governing Board.
- <li>
- Recruiting and approving new Gold and Silver members of the project.
- <li>
- Approving any exceptions to the Intellectual Property Policy.
- <li id="subprojcriteria">
- Defining any non-technical criteria
- (examples might include things like "no or minimal additional
- budgetary requirements for the project")
- that the Technical Board must consider when approving new sub-projects.
- In the interim period until these criteria are defined and agreed
- with the Technical Board, the Governing Board must approve new sub-projects
- after the Technical Board has approved them.
- <li>
- Voting on all matters requiring a decision from the Governing Board.
-</ol>
-
-<h4 id="govcomposition">Composition</h4>
-<p>
- The Governing Board shall consist of:
-<ol>
- <li>
- One representative appointed by each Gold Member
- as specified in <a href="#goldrep">clause 4.d.i</a> below.
- <li>
- Up to two Silver Member representatives
- as specified in <a href="#silverrep">clause 4.e.i</a> below.
- <li>
- One representative of the Technical Board,
- to be nominated by the Technical Board on an annual basis.
-</ol>
-
-<h4 id="govconduct">Conduct</h4>
-<p>
- Conduct of Governing Board meetings:
-<ol>
- <li>
- Governing Board meetings shall be limited to
- the Governing Board representatives,
- plus any other individuals that the Governing Board invites
- because their input is required on specific agenda topics.
- The Governing Board will allow a named representative to attend
- as an alternate if a Governing Board member cannot attend.
- <li>
- The quorum required for a meeting to proceed is a majority
- (&gt; 50%) of the Governing Board.
- <li>
- For a vote to be passed on the following items,
- a &frac23; majority (&gt; 66%) of the total Governing Board is required
- (<em>not</em> just a &frac23; majority of those in attendance at the meeting).
- In the event of a deadlock the Governing Board Chair
- shall have the casting vote.
- <ol>
- <li>
- Approval of any exceptions to the Intellectual Property Policy
- (see <a href="#licexception">clause 6.c</a>).
- <li>
- Approval of any changes to this document
- (see <a href="#amendments">section 12</a>).
- </ol>
- <li>
- For a vote to be passed on any other item,
- a majority (&gt; 50%) of the total Governing Board is required
- (<em>not</em> just a majority of those in attendance at the meeting).
- In the event of a deadlock the Governing Board Chair
- shall have the casting vote.
- <li id="govtransp">
- The Governing Board will encourage transparency,
- including the public publication of meeting minutes
- and reporting of budgets within a reasonable time
- following their approval by the Governing Board.
- When approving meeting minutes and budgets,
- the Governing Board must approve any items which cannot be included
- in the public versions for confidentiality reasons.
- <br>
- <em>Note</em>: Examples of board discussions which should not be made public
- might include things like legal issues, confidential budget discussions,
- discussion on potential new project members that have not yet been made public,
- etc.
-</ol>
-
-<h3 id="techboard">Technical Board</h3>
-
-<h4 id="techscope">Scope</h4>
-<p>
- The Technical Board is responsible for technical decision making
- for the DPDK project.
- Its scope does not include the other sub-projects
- hosted on dpdk.org (Pktgen, SPP etc.).
- A separate Technical Board may be established for other sub-projects
- in future if any of them grows sufficiently large to require one.
- Responsibilities of the Technical Board are:
-<ol>
- <li>
- Electing a Chair to preside over meetings,
- and manage any day-to-day operations.
- <ol>
- <li>
- The Chair will be elected on an annual basis.
- <li>
- The existing Chair will be allowed to stand for re-election.
- </ol>
- <li>
- Approving any new sub-projects,
- including new "next" repositories for DPDK
- and new DPDK-based apps like Pktgen and SPP.
- The procedure and requirements for requesting a new sub-project
- will be defined by the Technical Board.
- The Technical Board will apply non-technical criteria
- for new sub-projects that are defined by the Governing Board
- (see <a href="#subprojcriteria">clause 3.1.1.i</a>)
- when making its decision on proposed new projects.
- Requests can be submitted by emailing
- <a href="mailto:techboard@dpdk.org">techboard@dpdk.org</a>.
- <li>
- Deprecating any existing sub-projects.
- The procedure for deprecation and archival
- will be defined by the Technical Board.
- Deprecation requests can be submitted by emailing
- <a href="mailto:techboard@dpdk.org">techboard@dpdk.org</a>.
- <li>
- Resolving any technical disputes.
- Anybody who is unhappy with the resolution of a technical issue
- can request that the Technical Board review the issue
- and make a decision on it by emailing
- <a href="mailto:techboard@dpdk.org">techboard@dpdk.org</a>.
- This is only expected to happen in exceptional cases.
- Before escalating to the Technical Board it is required that
- all reasonable steps to resolve the dispute via consensus
- are taken and recorded on the
- <a href="/ml/listinfo/dev">dev@dpdk.org</a> mailing list.
- If the Technical Board Chair does not feel that this has happened,
- they can refer the issue back to the complainant
- for further action to be taken before escalating it to the Technical Board.
- <br>
- The decision of the Technical Board on any technical disputes will be final
- and all project contributors are expected to comply.
- If a Maintainer or Committer fails to comply
- with a decision of the Technical Board,
- the Technical Board will be empowered to take
- any necessary steps to enforce its decision,
- including replacing that Maintainer/Committer.
- <br>
- <em>Note</em>: Examples of issues that fall into this category might include
- disagreements over which patches should/should not go into DPDK.
- <li>
- Voting on all matters requiring a decision from the Technical Board.
-</ol>
-
-<h4 id="techcomposition">Composition</h4>
-<p>
- The Technical Board shall consist of:
-<ol>
- <li>
- The composition of the Technical Board is documented at
- <a href="/about/techboard#members">dpdk.org/about/techboard#members</a>.
- In the case of a conflict, the terms of this Charter prevail.
- <li>
- To be added to or removed from the Technical Board:
- <ol>
- <li>
- A candidate must be nominated by an existing member of the Technical Board and
- <li>
- The Technical Board must review and approve the change.
- </ol>
- <li>
- When adding or removing members, the Technical Board must consider the following:
- <ol>
- <li>
- Positions on the Technical Board are determined based on technical merit.
- A new member must have a strong history of contribution
- (including reviews of other people's contributions) to the project.
- <li>
- The Technical Board must ensure that it represents all parts of DPDK,
- including support for all architectures that DPDK runs on.
- <li>
- Employees of a single company should not occupy
- more than 40% of the Tech Board seats.
- <li>
- The Technical Board needs to be kept to a manageable size
- so that decisions can be made in an effective way.
- </ol>
-</ol>
-
-<h4 id="techconduct">Conduct</h4>
-<p>
- Conduct of Technical Board meetings:
-<ol>
- <li>
- Technical Board meetings shall be open to the public.
- <li>
- The quorum required for a meeting to proceed is a 70% majority
- of the Technical Board.
- <li>
- For a vote to be passed, a majority (&gt; 50%) of the total Technical Board
- is required (<em>not</em> just a majority of those in attendance at the meeting).
- In the event of a deadlock the Technical Board Chair shall have the casting vote.
- <li>
- Minutes of Technical Board meetings will be published publicly
- within a reasonable time following their approval by the Technical Board.
-</ol>
-
-<h2 id="membership">Membership</h2>
-<ol>
- <li>
- DPDK is a free, open source project that welcomes all contributors.
- Anybody can use or contribute to DPDK.
- There is no requirement to be a member of the DPDK project
- or a member of The Linux Foundation ("LF") to do so.
- <li>
- The DPDK project shall have Gold and Silver Members,
- independent of the technical contributors.
- All Gold and Silver Members must be current
- corporate members of The Linux Foundation (at any level).
- Details of LF membership levels and rates are available in
- <a href="https://www.linuxfoundation.org/about/bylaws">
- The Linux Foundation Bylaws</a>.
- <li>
- All Gold and Silver Members enjoy the privileges
- and undertake the obligations described in this DPDK Project Charter,
- as from time to time amended by the Governing Board
- with the approval of The Linux Foundation.
- During the term of their membership,
- all members will comply with all such policies
- as the LF Board of Directors and/or the DPDK Governing Board
- may from time to time adopt with notice to members.
- <li>
- Gold Members shall be entitled to:
- <ol>
- <li id="goldrep">
- Appoint a representative to the Governing Board
- and any other committees established by the Governing Board.
- <li>
- Participate in an open DPDK performance lab
- as outlined in <a href="#lab">clause 4.f</a> below.
- <li>
- Be prominently identified as Gold sponsors of the project
- at DPDK-funded events.
- Specific details of how this will be implemented
- will be determined by the Governing Board.
- <li>
- Identify themselves as Gold Members of the project.
- </ol>
- <li>
- Silver Members shall be entitled to:
- <ol>
- <li id="silverrep">
- Annually elect one representative to the Governing Board
- and any other committees established by the Governing Board
- for every five (5) Silver Members,
- up to a maximum of two (2) representatives.
- The election process shall be determined
- and published publicly by the Governing Board.
- <li>
- Participate in an open DPDK performance lab
- as outlined in <a href="#lab">clause 4.f</a> below.
- <li>
- Be identified as Silver sponsors of the project
- at DPDK-funded events.
- Specific details of how this will be implemented
- will be determined by the Governing Board.
- <li>
- Identify themselves as Silver Members of the project.
- </ol>
- <li id="lab">
- Gold and Silver Members shall be entitled to participate in
- an open DPDK Project performance lab (if created):
- <ol>
- <li>
- They will be able to contribute hardware
- to be hosted in the lab for DPDK performance testing.
- <li>
- They will be able to integrate software applications
- into the performance test configuration within the lab.
- <li>
- Limits on hardware and software contributions
- for Gold and Silver Members will be determined by the Governing Board.
- A higher priority will be given to Gold members
- than to Silver members when determining these limits.
- <li>
- Costs for hardware and software contributions
- for Gold and Silver Members will be determined by the Governing Board.
- The cost structure will take into account the fact that
- Gold members have already contributed significantly
- more funding to the project than Silver members.
- </ol>
-</ol>
-
-<h2 id="techgov">Technical Governance</h2>
-<p>
- The Technical Board described in <a href="#techboard">section 3.2</a>
- provides overall technical guidance and direction for DPDK.
-<p>
- Beyond that, each sub-project within DPDK shall be responsible
- for its own technical governance and technical decision making,
- including issues such as:
-<ol>
- <li>
- Determining the process and tools to be used
- for development, CI, validation etc.
- <li>
- Reviewing proposed changes (patches)
- and making decisions on which patches are and are not accepted
- into the project.
- <li>
- Scheduling of releases.
-</ol>
-<p>
- For the core DPDK project, technical governance is documented in
- the <a href="/doc/guides/contributing/">Contributor's Guidelines</a>
- and on the <a href="/dev/">Development web page</a>.
-<p>
- For the other sub-projects within DPDK,
- technical governance will be documented in a CONTRIBUTING.txt file
- in the root directory for the sub-project.
- See <a href="/browse/apps/pktgen-dpdk/tree/CONTRIBUTING.TXT"
- >pktgen-dpdk/tree/CONTRIBUTING.TXT</a> for an example.
-
-<h2 id="ip">Intellectual Property Policy</h2>
-<ol>
- <li>
- All new inbound contributions to DPDK
- will be made under the following licenses:
- <ol>
- <li>
- The <a href="https://spdx.org/licenses/GPL-2.0.html"
- >GPL-2.0 license</a>
- shall be used for code that runs in the kernel.
- Current examples of this are:
- <ol>
- <li>
- lib/librte_eal/linuxapp/igb_uio
- <li>
- lib/librte_eal/linuxapp/kni
- <li>
- lib/librte_eal/linuxapp/kni/ethtool/igb
- <li>
- lib/librte_eal/linuxapp/kni/ethtool/ixgbe
- </ol>
- <li>
- A disjunctive licence choice of
- <a href="https://spdx.org/licenses/BSD-3-Clause.html"
- >BSD-3-Clause</a> OR
- <a href="https://spdx.org/licenses/GPL-2.0.html"
- >GPL-2.0</a> or
- <a href="https://spdx.org/licenses/BSD-3-Clause.html"
- >BSD-3-Clause</a> OR
- <a href="https://spdx.org/licenses/LGPL-2.1.html"
- >LGPL-2.1</a>
- will be used for code that is shared between the kernel and userspace.
- Current examples of this are:
- <ul>
- <li>
- BSD-3-Clause OR GPL-2.0:
- <ol>
- <li>
- All files in
- <a href="/browse/dpdk/tree/drivers/crypto/qat/qat_adf/"
- >qat_adf</a>
- <li>
- <a href="/browse/dpdk/tree/lib/librte_eal/common/include/rte_pci_dev_features.h"
- >rte_pci_dev_features.h</a>,
- <a href="/browse/dpdk/tree/lib/librte_eal/common/include/rte_pci_dev_feature_defs.h"
- >rte_pci_dev_feature_defs.h</a>
- </ol>
- <li>
- BSD-3-Clause OR LGPL-2.1:
- <ol start="4">
- <li>
- <a href="/browse/dpdk/tree/lib/librte_eal/linuxapp/eal/include/exec-env/rte_kni_common.h"
- >rte_kni_common.h</a>
- </ol>
- </ul>
- <li>
- The <a href="https://spdx.org/licenses/BSD-3-Clause.html"
- >BSD-3-Clause license</a>
- will be used for all other contributions.
- </ol>
- <li>
- All contributions shall include a "Signed-off-by:" line
- which certifies that the contribution complies with
- the <a href="http://developercertificate.org"
- >Developer Certificate of Origin</a>.
- <li id="licexception">
- If an alternative inbound or outbound license is required
- for compliance with the license for a leveraged open source project
- or is otherwise required to achieve DPDK's Mission,
- the Governing Board may approve the use of an alternative license
- for specific inbound or outbound contributions on an exception basis.
- Any exceptions must be approved
- by a two-thirds vote of the entire Governing Board
- and must be limited in scope to what is required for such purpose.
- <li>
- Subject to available Project funds,
- DPDK may engage The Linux Foundation to determine the availability of,
- and register, trademarks, service marks, and certification marks,
- which shall be owned by the LF.
-</ol>
-
-<h2 id="budget">Budget</h2>
-<ol>
- <li>
- The Governing Board shall approve an annual budget
- and never commit to spend in excess of funds raised.
- The budget and the purposes to which it is applied
- shall be consistent with the non-profit mission of The Linux Foundation.
- <li>
- The Linux Foundation shall provide the Governing Board
- with regular reports of spend levels against the budget.
- In no event will The Linux Foundation have any obligation
- to undertake any action on behalf of DPDK or otherwise related to DPDK
- that will not be covered in full by funds raised by DPDK.
- <li>
- In the event any unbudgeted or otherwise unfunded obligation
- arises related to DPDK, The Linux Foundation will coordinate
- with the Governing Board to address gap funding requirements.
- <li>
- As described in <a href="#govtransp">clause 3.1.3.e</a>,
- the Governing Board will publish a public version of the budget.
- Questions on the budget should be addressed to the Governing Board.
-</ol>
-
-<h2 id="expenses">General &amp; Administrative Expenses</h2>
-<ol>
- <li>
- The Linux Foundation shall have custody of and final authority
- over the usage of any fees, funds and other cash receipts.
- <li>
- A General &amp; Administrative (G&amp;A) fee
- will be applied by the Linux Foundation
- to funds raised to cover Finance, Accounting, and operations.
- The G&amp;A fee shall equal 9% of DPDK's first $1,000,000 of gross receipts
- and 6% of DPDK's gross receipts over $1,000,000.
- <li>
- Under no circumstances shall The Linux Foundation be expected or required
- to undertake any action on behalf of DPDK that is inconsistent
- with the tax exempt purpose of The Linux Foundation.
-</ol>
-
-<h2 id="antitrust">Antitrust Guidelines</h2>
-<ol>
- <li>
- All members shall abide by
- <a href="http://www.linuxfoundation.org/antitrust-policy"
- >The Linux Foundation Antitrust Policy</a>.
- <li>
- All members shall encourage open participation
- from any organization able to meet the membership requirements,
- regardless of competitive interests.
- Put another way, the Governing Board shall not seek to exclude any member
- based on any criteria, requirements or reasons other than those that
- are reasonable and applied on a non-discriminatory basis to all members.
-</ol>
-
-<h2 id="coc">Code of Conduct</h2>
-<ol>
- <li>
- The Governing Board may adopt a specific Project code of conduct,
- with approval from the LF.
- <li>
- All participants in LF Project events shall abide by
- <a href="http://events.linuxfoundation.org/EVENT-CODE-OF-CONDUCT"
- >The Linux Foundation Events Code of Conduct</a>.
-</ol>
-
-<h2 id="genrules">General Rules and Operations</h2>
-<p>
- The DPDK project shall be conducted so as to:
-<ol>
- <li>
- Engage in the work of the project in a professional manner
- consistent with maintaining a cohesive community,
- while also maintaining the goodwill and esteem
- of The Linux Foundation in the open source software community;
- <li>
- Respect the rights of all trademark owners,
- including any branding and usage guidelines;
- <li>
- Engage The Linux Foundation for
- all DPDK press and analyst relations activities;
- <li>
- Upon request, provide information regarding project participation,
- including information regarding attendance at project-sponsored events,
- to The Linux Foundation;
- <li>
- Coordinate with The Linux Foundation in relation to
- any websites created directly for DPDK; and
- <li>
- Operate under such rules and procedures
- as may from time to time be approved by the Governing Board
- and confirmed by The Linux Foundation.
-</ol>
-
-<h2 id="amendments">Amendments</h2>
-<p>
- This charter may be amended by a two-thirds vote of
- the entire Governing Board,
- subject to approval by The Linux Foundation.
- Proposed changes must be communicated publicly
- to the community prior to being approved by the Governing Board.
-
-</section>
-<footer></footer>