From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f178.google.com (mail-wr0-f178.google.com [209.85.128.178]) by dpdk.org (Postfix) with ESMTP id 427D51BBE for ; Wed, 8 Mar 2017 15:45:03 +0100 (CET) Received: by mail-wr0-f178.google.com with SMTP id u108so24817557wrb.3 for ; Wed, 08 Mar 2017 06:45:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id:user-agent:in-reply-to:references :mime-version:content-transfer-encoding; bh=kgJ4KmmoPslzDtSdSGlC/eezCCy35e0td151HMOcYkQ=; b=IVW94Lrb8knnHki7SVAExiXz1tfTv7QRr/qDpIHrtZNXmcYNeMplyaHgos6i1nn40n Jo8Hc2mhQDXC7+pl9TUFC09QnWhOY9Qo/a7opZtPWxUTT75hll26FfOv7IhnHyev3Rw6 dKfQzRzWwGSJ9ZTTO/TTw3+wpsrPvqdOwc3qzGYH9RLsxGXUEEUpEJ0KvBGPA095MJ96 zoov2i8Glj7M9SNVSTwrJmKB/YlfrCMHJ8C3xWJ0p8Z09YSq6HJxjg7qdRVn5A2bziEV oD4QFU4GGetX6IgI2565am8MjFjaIQGvF36Rf6S3DEGSQuBMYuKVxNsC3qVtPHptgh1F lerA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=kgJ4KmmoPslzDtSdSGlC/eezCCy35e0td151HMOcYkQ=; b=cQI8A2dG9ajAGX66sd6q8IFzfLcEKM9x6k3eowOcaYJrEvOMyBNwhByEb94u94NywX OVmNgZRHwIZgbbJ0l2L9/gC0B1xwkoLlrszS0G1oGJ+1kfZKnsD2bPBp3v/o7//S1E8n xMxVIKh07bP2fi6PXs/EFqRUmyj8b6XtAylZp40PTJhhlLYtA1noTRfBwJi2Ikuyj2aL r4PdYt7af6wVRu6+2UxIDa0XzN5dq3VQrEy3B1yEnCaht2V3nA+dBwowUWtJemTw4smk vnaRgB9dXfAYuFpMn3vs7N3lqJMPKTtRievv4PCarnhpLiYQuNz0dzSbdq6lbCXhJfvn cL8w== X-Gm-Message-State: AMke39nMNZ8BCqyNZPixadR3wgpWid5RwG0KWrT80AfHX2/XBPVf0JL2qfqMPldoCGJy7Xqx X-Received: by 10.223.148.35 with SMTP id 32mr5779812wrq.82.1488984302617; Wed, 08 Mar 2017 06:45:02 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id 40sm4459189wry.22.2017.03.08.06.45.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Mar 2017 06:45:02 -0800 (PST) From: Thomas Monjalon To: moving@dpdk.org Date: Wed, 08 Mar 2017 15:45:01 +0100 Message-ID: <2433082.cJ3p5dltz2@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA72319828@IRSMSX108.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA72319828@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, March 7th 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: Wed, 08 Mar 2017 14:45:03 -0000 2017-03-08 13:44, O'Driscoll, Tim: > Adding the charter to the website: > - Thomas proposed on the mailing list that we post the charter on the website and manage changes in git (http://dpdk.org/ml/archives/moving/2017-March/000191.html). Agreed that this is a good idea. > - We need to agree which mailing list should be used for future discussion on the charter once it's baselined. Agreed that the best approach is to rename moving@dpdk.org to charter@dpdk.org when the project is launched, and use it for any future discussion. The archives will still contain the history of discussions on moving to LF. I think any changes in the charter or in the structure could be discussed on moving@dpdk.org. Why renaming? > - After it's baselined, proposed changes to the charter should be made on the charter@dpdk.org list. They can then be discussed in public on the list, and will also be discussed and voted on at a governing board meeting. A member of the board will indicate on the list if the board approves the proposed change. The changes must also be posted to web@dpdk.org. > - We can also set up a private mailing list for the governing board once its members are known, similar to techboard@dpdk.org. > > Membership: > - Mike is working on the membership agreement and expects to have a draft in the next day or two. He'll distribute this as soon as it's available. Is this agreement going to change anything in the charter? If not, I'm going to send a patch for charter integration in the web site.