From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by dpdk.org (Postfix) with ESMTP id 8127E6CB7 for ; Tue, 25 Oct 2016 16:00:14 +0200 (CEST) Received: by mail-wm0-f53.google.com with SMTP id b80so165480902wme.1 for ; Tue, 25 Oct 2016 07:00:14 -0700 (PDT) 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:in-reply-to :references:mime-version:content-transfer-encoding; bh=3Pew1WiSbc/xDlborGkalnvJvEREaXIRrJT+FN5QY0Q=; b=UdVE++JzcT8R3/96CzvMnZM6OAk02RnwbTx35JkW3TW2mz21xiOPKkwNXhHqOVL8Ri xdxR8+u3u3JJm5d+43eiOMw8XX5Nj9hQV/cJh9wTc2zMi2YaFpbMoFJgJJyACTMRPYv8 e16sUUgsKEBR3LPZI+BPDcZG6lZ3DPAOABPpJzFebUbnNdcbRutL79rGZhbgdvSCPA+a TaNTBPRsNxxGy2kKdzRXtVtHR9Q7TnCktO7tIHeKwvDHBN7CF12WPSLEUDR+4pg5sLrK mWT+ECrYqG/uEInYcdVaMBeawKYEWEy8v7PmRdB73nfSDjT6nk+BfE4HAqyfqxiNoP/q LDJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=3Pew1WiSbc/xDlborGkalnvJvEREaXIRrJT+FN5QY0Q=; b=U3uIUKzDCUCoQDSCJT119Z2MFWYNcw71PvNXURPyWaBkjcREOPMRwyccEnCZ6LU7TI AwlL6KRTZsL02OIBhjtJdqPbcd9afXbGPtLldP0/yKt/HxEEJXZiAjNjlY0/BdU52BPI kdeC+YIwqGGMbWxsZJv1FZoHKgfXYGOd13FrYA7dF1tyCotdKF7eyP0X9abABXwPK3Hg zbmzQQq1Adv4mfC94QOFFuP8soOQ+wbsWJTcTwwQOlNubZDhbteEZn6evS80XVgSqjj5 Ms8FQjOfghF68DcUqSb9Dvm67+/YRRdP7g9eusgQupPlJdWZEuY+EVyW3k4mm6zGXmA+ yeTg== X-Gm-Message-State: ABUngvebDj1crQgLAvNocwA9IZtxU+2NTZJlaRRdUVjt7Dq/SpTKxxUkGj4OK7wP0Mv0eWJ4 X-Received: by 10.28.31.201 with SMTP id f192mr3508848wmf.132.1477404014019; Tue, 25 Oct 2016 07:00:14 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id j185sm3863821wmg.13.2016.10.25.07.00.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Oct 2016 07:00:13 -0700 (PDT) From: Thomas Monjalon To: moving@dpdk.org Cc: "O'Driscoll, Tim" Date: Tue, 25 Oct 2016 16:00:12 +0200 Message-ID: <4939831.0LCNYxqha0@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA676071BB@IRSMSX108.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA676071BB@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-moving] description of technical governance 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: Tue, 25 Oct 2016 14:00:14 -0000 2016-10-25 11:27, O'Driscoll, Tim: > We also have a gap in terms of documenting technical governance. > Even ignoring the move to LF, Matt in particular was looking for > more clarity on this. > Thomas: would you be willing to create and post a proposal on this? The technical governance is consensus-based. The board was built in case a consensus is not found. There are several projects with their own git trees. DPDK and the web site are two of them. The DPDK project is organized around some git subtrees and the mainline gathers every contributions accepted in the subtrees. The component maintainers are quality responsibles for the code and the git history. They coordinate how improvements and fixes are done. The git tree committers are responsibles of the pace, giving time for reviews and tests while releasing in time. They also do the last checks or call for help when there is no progress on a patch. Is it the kind of information you are looking for? I think the technical governance must be described on the web site in the "development" page. It is already partly described but it may requires more details and updates.