DPDK community structure changes
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: moving@dpdk.org, opensource@jilayne.com
Cc: matt.spencer@arm.com
Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, March 28th
Date: Fri, 31 Mar 2017 11:13:53 +0200	[thread overview]
Message-ID: <2723281.CbpgGnzJFD@xps13> (raw)
In-Reply-To: <2437706.mFK5Q2ocKm@xps13>

2017-03-31 02:49, Thomas Monjalon:
> 2017-03-29 15:07, O'Driscoll, Tim:
> > - Agreed that we should post the charter on the website.
> > Thomas can do this, but we need Mike to confirm
> > if the version in google docs is the final version.
> 
> I've checked both versions.
> They are identical.
> 
> I am preparing the HTML version.

Any new modifications (like the ones suggested recently by Jilayne Lovejoy)
should be suggested on top of the HTML version
and approved by the Governing Board and LF as stated in section 12.

      reply	other threads:[~2017-03-31  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 15:07 O'Driscoll, Tim
2017-03-31  0:49 ` Thomas Monjalon
2017-03-31  9:13   ` Thomas Monjalon [this message]

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=2723281.CbpgGnzJFD@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=matt.spencer@arm.com \
    --cc=moving@dpdk.org \
    --cc=opensource@jilayne.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).