From: Stephen Hemminger <stephen@networkplumber.org>
To: Bagh Fares <Fares.Bagh@freescale.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"CHIOSI, MARGARET T \(mc3124@att.com\)" <mc3124@att.com>,
"Pradeep Kathail \(pkathail@cisco.com\)" <pkathail@cisco.com>
Subject: Re: [dpdk-dev] Proposals from project governance meeting at DPDK Userspace (was Notes from ...)
Date: Mon, 2 Nov 2015 09:21:53 -0800 [thread overview]
Message-ID: <20151102092153.3b005229@xeon-e3> (raw)
In-Reply-To: <BLUPR0301MB16517A68D5DB10053F353753982F0@BLUPR0301MB1651.namprd03.prod.outlook.com>
There were two outcomes.
One was a proposal to move governance under Linux Foundation.
The other was to have a technical steering committee.
It was agreed the TSC would be based on the contributors to the project,
although we didn't come to a conclusion on a voting model.
I would propose that TSC should be elected at regular user summit from nominees;
in a manner similar to LF Technical Advisory Board.
next prev parent reply other threads:[~2015-11-02 17:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 18:01 Bagh Fares
2015-11-02 16:04 ` CHIOSI, MARGARET T
2015-11-02 17:21 ` Stephen Hemminger [this message]
2015-11-02 17:28 ` CHIOSI, MARGARET T
2015-11-02 17:31 ` Dave Neary
2015-11-02 17:44 ` Bagh Fares
2015-11-02 17:55 ` Dave Neary
2015-11-02 18:02 ` Bagh Fares
2015-11-02 21:44 ` O'Driscoll, Tim
2015-11-02 23:16 ` Pradeep Kathail
2015-11-03 12:43 ` O'Driscoll, Tim
2015-11-03 13:03 ` Thomas Monjalon
2015-11-03 22:05 ` Bagh Fares
2015-11-03 22:47 ` Vincent JARDIN
2015-11-03 15:17 ` CHIOSI, MARGARET T
2015-11-03 23:35 ` Stephen Hemminger
2015-11-04 17:02 ` Pradeep Kathail
2015-11-02 18:01 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2015-10-11 0:36 [dpdk-dev] Notes from project governance meeting at DPDK Userspace Dave Neary
2015-10-12 16:45 ` [dpdk-dev] Proposals from project governance meeting at DPDK Userspace (was Notes from ...) Dave Neary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151102092153.3b005229@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=Fares.Bagh@freescale.com \
--cc=dev@dpdk.org \
--cc=mc3124@att.com \
--cc=pkathail@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).