DPDK community structure changes
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: moving@dpdk.org
Subject: Re: [dpdk-moving] Board Names
Date: Wed, 16 Nov 2016 18:44:47 +0100	[thread overview]
Message-ID: <1712528.kSnG0XNraU@xps13> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA676143A8@IRSMSX108.ger.corp.intel.com>

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

> 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

  parent reply	other threads:[~2016-11-16 17:44 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 [this message]
2016-11-16 20:00   ` Wiles, Keith
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=1712528.kSnG0XNraU@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=moving@dpdk.org \
    --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).