From: "Simon Kågström" <simon.kagstrom@netinsight.net>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK.org Community Call - Sept 24 - Discuss Growth, Improvements
Date: Thu, 24 Sep 2015 10:40:25 +0200 [thread overview]
Message-ID: <5603B6F9.8070504@netinsight.net> (raw)
In-Reply-To: <1806720.jzdZcVXP9E@xps13>
On 2015-09-24 10:36, Thomas Monjalon wrote:
> 2015-09-23 23:56, St Leger, Jim:
>> This call is aimed to get more open dialogue in the community.
>
> I wonder how a call can "get more open dialogue"?
> Because of being "live", a lot of people cannot attend at this time.
> A call is also a place where only people having the strongest voice will be heard.
> Finally it will be really well understood only by english-native people
> (depending on the accent of speakers).
>
> I know only one way to be really open and we are using it for this discussion.
One good thing would be if someone could write a summary of the
community call discussion for further discussion on the mailing list.
// Simon
next prev parent reply other threads:[~2015-09-24 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 7:14 St Leger, Jim
2015-09-23 21:00 ` Dave Neary
2015-09-23 23:56 ` St Leger, Jim
2015-09-24 8:36 ` Thomas Monjalon
2015-09-24 8:40 ` Simon Kågström [this message]
2015-09-24 15:35 ` Butler, Siobhan A
2015-09-28 20:44 ` O'Driscoll, Tim
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=5603B6F9.8070504@netinsight.net \
--to=simon.kagstrom@netinsight.net \
--cc=dev@dpdk.org \
/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).