From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50]) by dpdk.org (Postfix) with ESMTP id 46F0A108A for ; Mon, 6 Mar 2017 22:19:37 +0100 (CET) Received: by mail-wm0-f50.google.com with SMTP id 196so20851113wmm.1 for ; Mon, 06 Mar 2017 13:19:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=AFvC07Xh/Cmj+CIU65ryAjgXfFPwT9bXfyPyO4aBzFQ=; b=Ydw2Qicc70TQbhw9MS9mER8FpyGULMSZyXJ07/63540Y5UN/2oluQ8zKO99v8SzZna Qnc3LWccsQ9IaSsIQupjpyZfGhk045ezwMWOB1ZyD8D2eFeGruW2vzp5kkmlqhAB72Yg 6gaoVCjax1y6kTz4HmVKhCEjZqfEGGL6vn43sJwInOfiA7jc7EBz1sJAR/PuaRHfDWKg iYdSNqrRQZ7hIk9KdmfMf/Yd2iBPxXDSVn2asOzy5kD2KYEl6zH9phLwyXngjx7hr4uS vOrqSBYPsNsmQBp+Ak7hFIYdaZ6KFi7gxJIfufzl+WqiCmaigxpuB/vye4/jSelgb6GJ +bkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=AFvC07Xh/Cmj+CIU65ryAjgXfFPwT9bXfyPyO4aBzFQ=; b=FtLhQteRciELU/1hYnU/mBCXdue0mFYEN0pQtx2wDe3Qc1qyADMocUtXTYuP+/0pVF b+EyvkAxh0ZHfuM9DCmGc5+aqaB3bFikgFMgq6i58rIbxh+J9ustJDk5gtmwbqhusEpB e8G+r8ajKEUBT5eN1OlDWXwgPcie94glBAAbLv8yZF/jLXsBvCCNM8ENQ7nk0U2T0gDa cKsj0W6I1HedsO4eI9auif3vUDXEyeypFUEtQ2MBm88FQqUB3MSLx7wP/6jm9Qdmcn4w nGVr16kjtCz6fwDYZWFGLHJVBJF7OUcaEuNqTXN4GaG+4XUWm4rqZemi/RQeEi3hdGWB 9AmA== X-Gm-Message-State: AMke39mr6uGOtQUOrp70RW+sNGteV/uCYMVT8jg6WCBauZOF5NyNNcCf+B+4HiQY1FeyBnGw X-Received: by 10.28.50.6 with SMTP id y6mr15286672wmy.112.1488835176303; Mon, 06 Mar 2017 13:19:36 -0800 (PST) Received: from XPS13.localdomain (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id d75sm16298708wmd.25.2017.03.06.13.19.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 06 Mar 2017 13:19:35 -0800 (PST) From: Thomas Monjalon To: web@dpdk.org Cc: techboard@dpdk.org Date: Mon, 6 Mar 2017 22:19:27 +0100 Message-Id: <1488835167-18795-1-git-send-email-thomas.monjalon@6wind.com> X-Mailer: git-send-email 2.7.0 In-Reply-To: <4118025.NYSFXgDCxF@xps13> References: <4118025.NYSFXgDCxF@xps13> Subject: [dpdk-web] [PATCH v2] update techboard description X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Mar 2017 21:19:37 -0000 The Technical Board has new members and a new operation mode. Some of the changes have been discussed in the Linux Foundation meetings. Everything has been agreed in the Technical Board meetings. Cc: techboard@dpdk.org Signed-off-by: Thomas Monjalon --- v2: reword role of input for stalled patches --- about.html | 4 ++ about/techboard.html | 104 +++++++++++++++++++++++++++++++++++++++++++++++++ dev.html | 30 ++------------ scripts/serve_local.py | 2 +- 4 files changed, 112 insertions(+), 28 deletions(-) create mode 100644 about/techboard.html diff --git a/about.html b/about.html index 3f5199b..9a8df53 100644 --- a/about.html +++ b/about.html @@ -43,6 +43,10 @@

For an update of this web site, please join web@dpdk.org and check the git repository.

For any other question, please contact admin@dpdk.org. +

Maintainers

+

Each project on dpdk.org has its own maintenance process. +

The main DPDK project has a list of maintainers + and a 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..5bcb6bc --- /dev/null +++ b/about/techboard.html @@ -0,0 +1,104 @@ + + + + + + DPDK Technical Board + + + + + + +
    +

    DPDK: Data Plane Development Kit

    + +
    +
    +

    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 patch does not receive any or enough comment, the board may discuss it + in order to provide an input 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 = [] -- 2.7.0