From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "moving@dpdk.org" <moving@dpdk.org>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-moving] changes in the Technical Board
Date: Tue, 31 Jan 2017 13:40:33 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA722B38BE@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1536736.Y1UUVgnqSY@xps13>
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
>
> 2017-01-25 11:57, O'Driscoll, Tim:
> > Next Meeting:
> > Tuesday January 31st at 3pm GMT, 4pm CET, 10am EST, 7am PST. We can
> discuss any preliminary input that Mike has from his membership
> discussions, discuss the desired budget level, and hopefully get an
> update from the Tech Board on any changes they're planning to make.
>
> I have provided some feedbacks from the Technical Board in the charter.
> Please, could we discuss or approve them in the next meeting today?
Yes, I think that's a good idea.
> We should also discuss about integrating the charter in the website.
> I suggest creating a dedicated page dpdk.org/charter linked from
> the "home" page and from the "about" page.
I think this makes sense too. It will help to make the charter more visible.
next prev parent reply other threads:[~2017-01-31 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 11:57 [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, January 24th O'Driscoll, Tim
2017-01-25 15:48 ` Wiles, Keith
2017-01-25 16:16 ` O'Driscoll, Tim
2017-01-25 16:30 ` Ed Warnicke
2017-01-25 17:10 ` O'Driscoll, Tim
2017-01-25 17:29 ` George Zhao
2017-01-25 17:39 ` Zhu, Heqing
2017-01-25 18:06 ` O'Driscoll, Tim
2017-01-25 18:15 ` Michael Dolan
2017-01-26 1:33 ` Xu, Qian Q
2017-01-31 11:12 ` [dpdk-moving] changes in the Technical Board Thomas Monjalon
2017-01-31 11:55 ` Vincent Jardin
2017-01-31 13:16 ` Thomas Monjalon
2017-01-31 13:40 ` O'Driscoll, Tim [this message]
2017-02-06 12:53 ` [dpdk-moving] [dpdk-techboard] " Hemant Agrawal
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=26FA93C7ED1EAA44AB77D62FBE1D27BA722B38BE@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=moving@dpdk.org \
--cc=techboard@dpdk.org \
--cc=thomas.monjalon@6wind.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).