From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: moving@dpdk.org
Subject: Re: [dpdk-moving] Summary Slides
Date: Tue, 07 Mar 2017 14:29:31 +0100 [thread overview]
Message-ID: <1551673.pXFurQyEQ1@xps13> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA7230FAF9@IRSMSX108.ger.corp.intel.com>
2017-03-07 12:27, O'Driscoll, Tim:
> I've also spoken to Mike Dolan about the need for a membership agreement. He's working on that, but needs another day or two because some changes are being made to the standard LF template and he wants to make sure they're included. This should be available soon.
I am preparing the conversion of the charter doc to a dpdk.org web page.
When it will be accepted to switch the draft in the HTML version, it
would become the new reference. So from this point, any modification
would be recorded in the git tree http://dpdk.org/browse/tools/dpdk-web/
after submission and acknowledgement on the mailing list web@dpdk.org
(+ cc moving@dpdk.org).
It would provide a better visibility to the whole community.
What do you think of this process?
prev parent reply other threads:[~2017-03-07 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 12:27 O'Driscoll, Tim
2017-03-07 13:29 ` 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=1551673.pXFurQyEQ1@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).