From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0085.outbound.protection.outlook.com [104.47.0.85]) by dpdk.org (Postfix) with ESMTP id D3574BD2C; Mon, 6 Feb 2017 13:53:29 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nxp.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=VpOpGWgB3t312CrId0b02jBtgzNmARQ28kHKWU52MJw=; b=IDgXl4xg8NP73QXm5IKJZEyzkEpzDJfBC3zRn4dZMrxT0AiKoWdF1MIyeQpzPocKJ1945bNJgzfW25xFy+6X16rojsrrxVIo8ufRrMMEcm3uEYP8yFKOx2/vscJ5oEDEF0xhyXgMqiqJg7RMVhpTBu6wTVugK/JvB97UR+v4OPI= Received: from DB5PR04MB1605.eurprd04.prod.outlook.com (10.164.38.147) by DB5PR04MB1605.eurprd04.prod.outlook.com (10.164.38.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Mon, 6 Feb 2017 12:53:28 +0000 Received: from DB5PR04MB1605.eurprd04.prod.outlook.com ([10.164.38.147]) by DB5PR04MB1605.eurprd04.prod.outlook.com ([10.164.38.147]) with mapi id 15.01.0888.025; Mon, 6 Feb 2017 12:53:28 +0000 From: Hemant Agrawal To: Thomas Monjalon , "O'Driscoll, Tim" CC: "moving@dpdk.org" , "techboard@dpdk.org" Thread-Topic: [dpdk-techboard] [dpdk-moving] changes in the Technical Board Thread-Index: AQHSe7Lv1tyrbTqRD0m8rGTfCUNTtaFb6Ulw Date: Mon, 6 Feb 2017 12:53:27 +0000 Message-ID: References: <26FA93C7ED1EAA44AB77D62FBE1D27BA722AFB94@IRSMSX108.ger.corp.intel.com> <1536736.Y1UUVgnqSY@xps13> In-Reply-To: <1536736.Y1UUVgnqSY@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=hemant.agrawal@nxp.com; x-originating-ip: [192.88.169.1] x-ms-office365-filtering-correlation-id: c98e11b2-f9a1-484b-e68e-08d44e8f255e x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:DB5PR04MB1605; x-microsoft-exchange-diagnostics: 1; DB5PR04MB1605; 7:oI3eLPayTyMypHmMGccognRfPw6Q3uLDcq1Le8r9W95UjlUscYtHmV6P5HX9aCwXKgP6UkvUMsNqy2T66FKgcTQ26UvhGAlgnazOqTgYnoWn3xrXI7yN7//Z3HzimLKtlafNifrL849f+r1/9vJDGLHegom6iEE4OPMW13Tc/5NvXQ5m9HrdMEF5JIjtg2PsfdbA+ydmQZvFEi0hGB14kg8NCgK9VT14joz2E7F27pyLeo/aGLLAIu3emIyI6wZ7Iw++rETn6nsfm6aET9YuAQgstKF8G7f/zlA/ziXwJnlh9i4Nw+wkO+eOp6zsDRabmKx7BJyiaH5ydwftK1p/whJDS3Nh0nmsv2AMyJU84zkhL2sPSFBrzfHGxXhDw1UOquSQbYzmjI6HQ7Uj4cz3B4OJqbnLXMkuTWDdjcdaPzKjXQZjQZPRFZQCdkEaiT+ST2hsbGbAl7VYw6ni0XyQtydOhju77hSLnArwSx+kubkRsgDwaBtqh1pEqzQkz2y9QnzIS2EZBk8UI3TCBeGORw== x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(788757137089)(100405760836317)(228905959029699); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(20170203043)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123555025)(20161123558025)(20161123560025)(20161123564025)(20161123562025)(6072148); SRVR:DB5PR04MB1605; BCL:0; PCL:0; RULEID:; SRVR:DB5PR04MB1605; x-forefront-prvs: 0210479ED8 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39860400002)(39840400002)(39410400002)(39450400003)(39850400002)(199003)(377454003)(189002)(377424004)(13464003)(25786008)(2900100001)(4326007)(6506006)(6246003)(2906002)(229853002)(966004)(68736007)(77096006)(3660700001)(189998001)(5001770100001)(3846002)(6116002)(97736004)(2950100002)(102836003)(122556002)(38730400001)(3280700002)(53936002)(92566002)(6436002)(305945005)(74316002)(33656002)(86362001)(7736002)(8676002)(105586002)(8936002)(15395725005)(50986999)(99286003)(54906002)(55016002)(6306002)(101416001)(66066001)(9686003)(7696004)(106116001)(106356001)(5660300001)(54356999)(76176999)(81166006)(81156014); DIR:OUT; SFP:1101; SCL:1; SRVR:DB5PR04MB1605; H:DB5PR04MB1605.eurprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: nxp.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: nxp.com X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Feb 2017 12:53:27.9237 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR04MB1605 Subject: Re: [dpdk-moving] [dpdk-techboard] changes in the Technical Board X-BeenThere: moving@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK community structure changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2017 12:53:30 -0000 HI Thomas, > -----Original Message----- > From: techboard [mailto:techboard-bounces@dpdk.org] On Behalf Of > Thomas Monjalon > Sent: Tuesday, January 31, 2017 4:43 PM > To: O'Driscoll, Tim > Cc: moving@dpdk.org; techboard@dpdk.org > Subject: Re: [dpdk-techboard] [dpdk-moving] changes in the Technical Boar= d >=20 > 2017-01-25 11:57, O'Driscoll, Tim: > > Next Meeting: > > Tuesday January 31st at 3pm GMT, 4pm CET, 10am EST, 7am PST. We can > discuss any preliminary input that Mike has from his membership > discussions, discuss the desired budget level, and hopefully get an updat= e > from the Tech Board on any changes they're planning to make. >=20 > I have provided some feedbacks from the Technical Board in the charter. > Please, could we discuss or approve them in the next meeting today? >=20 > We should also discuss about integrating the charter in the website. > I suggest creating a dedicated page dpdk.org/charter linked from the "hom= e" > page and from the "about" page. >=20 > We also need to refresh the technical board description. > I suggest to move the section http://dpdk.org/dev#board to a dedicated > page dpdk.org/techboard linked from the "dev" page and from the "about" > page. >=20 > Here is a first draft for the page dpdk.org/techboard: >=20 [Hemant] I could not find details about the Technical Board Chair, you ma= y add some details about it as well e.g. Technical Board Chair How he will be elected? E.g. The Technical Board Chair will elected by the = process of nomination/election within the technical board.=20 Term ? The term of technical board will be for 1 years. There are no restr= ictions, the current Technical Board Chair can be re-elected for next term= . Governing Board Rep? He will be the representative of the Technical Board i= n Governing Board. He may choose to nominate another Technical Board Member= to attend Governing Board meetings.=20 > ------------------------- >=20 > More high level details are defined in the dpdk.org/charter. >=20 > Scope >=20 > 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 th= e > development in the following repositories: > - dpdk.git > - dpdk-stable.git > - dpdk-next-*.git > - dpdk-ci.git > - dpdk-web.git >=20 > Members >=20 > 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 >=20 > Renewal >=20 > 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 th= e > whole Technical Board. > It can be decided either to replace the member, or to redefine the size o= f the > board. > There will be some renewal when it will be felt as needed. >=20 > Meetings >=20 > A short meeting happens on IRC every two weeks. > The quorum required for a meeting to proceed is a 70% majority of the > Technical Board. > 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. >=20 > Roles >=20 > 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 w= ill 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 casti= ng > vote. >=20 > Feedback >=20 > Minutes are sent to dev@dpdk.org so anyone can comment. > However, the technical discussions should happen in the original thread. >=20 > -------------------------