DPDK community structure changes
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
	"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] Board Names
Date: Wed, 16 Nov 2016 20:00:43 +0000	[thread overview]
Message-ID: <E4835C96-B5B3-43BD-8A0F-15C67AF71EE0@intel.com> (raw)
In-Reply-To: <1712528.kSnG0XNraU@xps13>


> On Nov 16, 2016, at 11:44 AM, Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> 
> 2016-11-16 16:50, O'Driscoll, Tim:
>> For the board itself, there are several options including:
>> 1.a Governing Board. This is frequently used in other LF projects.
>> 1.b Board of Directors. This is also frequently used in other LF projects.
>> 1.c DPDK Board. This is a bit more neutral and doesn't imply that the board governs the technical aspects of the project.
>> 1.d DPDK Marketing & CI Board. This is more specific, but is a bit misleading as the board only manages the budget for CI, not all aspects of CI.
> 
> I do not like 1.a, 1.b and 1.c because it is not descriptive enough.
> We must avoid giving the impression that the technical part of the project
> is influenced by those paying a membership.
> 
> Why not simply one these new proposals?
> 1.e Budget Board
> 1.f Financial Board

I am not a big fan of trying to label this board as it does a bit more then just budgets or financial. It also does marketing, CI allocation and general bottle washer :-) I wish I could come up with a better name that works.

How about this then:

- DPDK Governing Committee (DGC) or DPDK Governing Board (DGB)

- Technical Steering Committee (TSC)

my $0.02 worth, does that make my a gold member :-)
> 
>> For the technical board, the options include:
>> 2.a Technical Board. This is the current name.
>> 2.b Technical Steering Committee. This is the name typically used on other LF projects.
> 
> OK for both

Regards,
Keith

  reply	other threads:[~2016-11-16 20:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 16:50 O'Driscoll, Tim
2016-11-16 17:09 ` Wiles, Keith
2016-11-16 17:44 ` Thomas Monjalon
2016-11-16 20:00   ` Wiles, Keith [this message]
2016-11-16 20:19 ` Dave Neary
2016-11-17  9:16   ` Vincent JARDIN

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=E4835C96-B5B3-43BD-8A0F-15C67AF71EE0@intel.com \
    --to=keith.wiles@intel.com \
    --cc=moving@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    --cc=tim.odriscoll@intel.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).