DPDK Technical Board

Services

Companies able to provide services and support for DPDK environments:

> diff --git a/about/techboard.html b/about/techboard.html > new file mode 100644 > index 0000000..0390f14 > --- /dev/null > +++ b/about/techboard.html > @@ -0,0 +1,106 @@ > + > + > + > + > + > + DPDK Technical Board > + > + > + > + > + > + > +

> +

> + > +

> +

Technical Board

> + > +

More high level details are defined in the > +charter.

> + > +

Scope

> +

The decision making process is primarily based on consensus. > +However in rare cases, the Technical Board can make a decision > +when consensus is not reached on the mailing list. > +

The scope of this body is limited to the questions directly related > +to the development in the following repositories: > +

dpdk.git > +
dpdk-stable.git > +
dpdk-next-*.git > +
dpdk-ci.git > +
dpdk-web.git > +

> + > +

Members

> +

The 9 current members of > +techboard@dpdk.org are: > +

Bruce Richardson > +
Hemant Agrawal > +
Jan Blunck > +
Jerin Jacob > +
Konstantin Ananyev > +
Olivier Matz > +
Stephen Hemminger > +
Thomas Monjalon > +
Yuanhan Liu > +

> + > +

Renewal

> +

Technical Board positions are held by individuals, not companies. > +However, employees of a single company should not occupy more than 40% of board seats. > +

It can be decided to remove a member if there is an approval of 2/3 of the whole Technical Board. > +It can be decided either to replace the member, or to redefine the size of the board. > +

There will be some renewal when it will be felt as needed. > + > +

Meetings

> +

A short meeting happens on IRC (freenode #dpdk-board) every two weeks. > +

The quorum required for a meeting to proceed is a 70% majority of the Technical Board. > +

The Chair is a rotating role among members. > +

Any contributor can ask to add a topic in the agenda by sending an email > +to techboard@dpdk.org. > +The board members will add any topic of interest in the agenda. > +

Minutes are sent to dev@dpdk.org so anyone can comment. > +However, the technical discussions should happen in the original thread. > + > +

Roles

> +

The new project repositories must be approved by the Technical Board, > + while applying the non-technical criteria defined by the Governing Board. > +
If a technical discussion lacks of explanation, details or evidence, > + it will be asked on the mailing list. > +
If a patch does not receive any or enough comment, the board will help > + to make it progressing on the mailing list. > +
If there is no consensus in a discussion, a decision can be taken > + by the Technical Board and explained on the mailing list. > +

> +

For a vote to be passed, a majority (> 50%) of the total Technical Board is required > +(not 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. > + > +

> diff --git a/dev.html b/dev.html > index a4b7386..478f712 100644 > --- a/dev.html > +++ b/dev.html > @@ -133,32 +133,8 @@ >

Most of the patchwork actions can be done > with a pwclient command line. > > -

Technical board

> -

The decision making process is primarily based on consensus. > - However in rare cases, the technical board can make a decision > - when consensus is not reached on the mailing list. > -

The scope of this body is limited to the questions directly related to > - the development in the following repositories: > -

dpdk.git > -
dpdk-next*.git > -
dpdk-web.git > -

> -

After having tried to solve every concerns, a maintainer > - (listed in the MAINTAINERS file) > - or a board member (listed below) can request a board meeting as a last resort. > - Then the technical board will meet on IRC to issue a decision within 2 weeks. > - A quorum of 6 members is required. > -

The 7 current members of > - techboard@dpdk.org are: > -

Bruce Richardson > -
Jerin Jacob > -
Konstantin Ananyev > -
Olivier Matz > -
Panu Matilainen > -
Stephen Hemminger > -
Thomas Monjalon > -

> +

Technical Board

> +

The Technical Board may intermediate in the development process, > + as described in the Technical Board operation. > > > diff --git a/scripts/serve_local.py b/scripts/serve_local.py > index 63a0e59..bdfc92e 100644 > --- a/scripts/serve_local.py > +++ b/scripts/serve_local.py > @@ -2,7 +2,7 @@ import BaseHTTPServer > from os import curdir, sep, listdir > > port = 8000 > -folders = [".", "./doc", "./dev"] > +folders = [".", "./about", "./doc", "./dev"] > > html_files = [] > Fine as far as it goes. There are some later issues that need to be addressed in revisions. We need a Code Of Conduct and a process for handling infractions documented before first offense. This will help CYA and attract a more diverse set of contributors. If a CoC is not created by techboard one will be placed upon us by LF. One issue that has come up on the kernel developers list is how to handle people who spam the community with useless and broken patches. There is already an unofficial short list of known abusers who are ignored. As DPDK gets bigger we are bound to attract these clueless developers. What is the plan for that? Is it a tech board topic. Acked-by: Stephen Hemminger

Maintainers

Services

Technical Board

Scope

Members

Renewal

Meetings

Roles

Technical board

Technical Board