From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by dpdk.org (Postfix) with ESMTP id C7E025589 for ; Thu, 26 Jan 2017 23:14:05 +0100 (CET) Received: by mail-wm0-f43.google.com with SMTP id r144so108226726wme.1 for ; Thu, 26 Jan 2017 14:14:05 -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:user-agent:mime-version :content-transfer-encoding; bh=OxRQmXpsyq9n/BqVfW8jCaJDMD9JHzN73pYMcYSluUw=; b=1iRtX8aSBprC7o9CKLyf2xPaft5QkoW0MuVcVgvE+uJNk4fK4Ym2k/YR8uSFK5Wnjj pjZLKLNvpF8YSqMF7o3IsTAZUu4BLlIk5n6LOFIXVkQriOFCKOlP/uMy968y2t2uDk2U CqXCQD/ft1G7cbhFYe7LMp0DxRH2l3m7HAqhZDaoN2QpcDKKq5V2mToaY5xj3OUsw1lq //ci92UdH4WybCju7EeSY51eGjDIRqKno5B4++Gjz9EPYVPkLJPjyWWmyoBQ7VWd/9IN Ii/Zy2Zs04RN8A4LqjYhsuLldrCOHN5an/T+u51xXUL3ghT4lUvQ33Hgvd/wU6aCCWCq cfvQ== 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:user-agent :mime-version:content-transfer-encoding; bh=OxRQmXpsyq9n/BqVfW8jCaJDMD9JHzN73pYMcYSluUw=; b=F/+aberO3PKSLe/eSkegcNTsO5CW4E+4VfjmVYLr1AKVXPLpEPAKRBtTJEMzMPp/ZJ 1ltOZwZSzI6Rfq2Almg5cQuhiw3B3WO9vVcumq/+P4nWt+k/3/2/vnfCtJHCPRgyUAjA vcqj7mn7T/RI3Vj4Xd7yOtMJeh+EtA3KkW/Ki86umDfXGFFu6IpzBLLULhaUoTfEZBzS 2sWfH87EPvLbvuPNlvNV/S1ejwZItjCcvSfcaDhNEA9hlJ8qIgxOXsuoZNMEmhkyUefE aRvXSVNkEbfOcDtzvp2LHf3FyPLW5JFKwA/2Gmpm5jzHwXza7Nda5CpwUjyAYcvAgr8Q BdHw== X-Gm-Message-State: AIkVDXJFOIdKa3GXmTTGu9JI2r9HwikCLa0tU9z5hg3jElkC9PHBdllerfRP0ht0VXlqaSDE X-Received: by 10.28.32.198 with SMTP id g189mr447849wmg.37.1485468845421; Thu, 26 Jan 2017 14:14:05 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id l9sm585392wmf.18.2017.01.26.14.14.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Jan 2017 14:14:04 -0800 (PST) From: Thomas Monjalon To: dev@dpdk.org Cc: techboard@dpdk.org Date: Thu, 26 Jan 2017 23:14:03 +0100 Message-ID: <8512033.OqnvuX0xuh@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [dpdk-dev] technical board meeting minutes 2017-01-25 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2017 22:14:06 -0000 There was a DPDK technical board meeting yesterday. The goal was to reply questions asked recently in the community. Most of them originate from the meetings about moving to Linux Foundation. Here are the minutes. * Should we change the size of the tech board? Yes we must increase the number of members to have a better representation of the community. It is reminded that board positions are held by individuals, not companies. Members can move to a new company and keep their seat as long as they are actively involved in the community. * Should we remove some members? Panu Matilainen resigned because he is not involved anymore. This is different of a removal by the board. However, we must define the removal process. Here it is: 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. * Should we add new members? The Linux Foundation draft charter specifies that employees of a single company should not occupy more than 50% of board seats. The technical board feels that this should be reduced to 40%. So with a board of 8 or 9 members, the maximum for any company is 3. We have chosen (with global consensus) 3 new members to join the technical board. They will be announced soon when we will have their agreement. The new board will probably count 9 members. * Should we have a process to renew the board? There will be some renewal when it will be felt as needed. We would like to open a session at the next userspace meeting to get some feedbacks about the composition of the technical board, and more generally about its role. This annual session at the userspace meeting might be the opportunity to vote for the composition of the technical board. * Should we have regular meetings? We do not want to spend too many time in meetings. However a short meeting (less than a hour) every two weeks may be relevant. * What could be discussed at regular meetings? 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. 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, we 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. If there is nothing to discuss, the meeting will be hopefully really short. * Should we organize regular public IRC meetings? It does not scale to have too many participants in a meeting. In order to keep meetings short, they will be private. Everybody can discuss on the mailing list. * How to report the meeting minutes? The meetings happen on IRC and may use voice if needed. The role of meeting leader - whose role involves taking the meeting minutes - will be rotated among the members so as to share the workload. Minutes will be sent to dev@dpdk.org so anyone can comment. However, the technical discussions should happen in the original thread. Feel free to comment. The next meeting should happen in less than three weeks.