From: Neil Horman <nhorman@tuxdriver.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Making DPDK.org more vendor neutral
Date: Sat, 31 Jan 2015 16:55:11 -0500 [thread overview]
Message-ID: <20150131215511.GA28666@localhost.localdomain> (raw)
In-Reply-To: <20150131204710.2bf9f5fa@uryu.home.lan>
On Sat, Jan 31, 2015 at 08:47:10PM +0000, Stephen Hemminger wrote:
> I think that DPDK.org should be as neutral in all public communications.
>
> This bothers me:
> "If you need some specific drivers or networking stacks, you should contact a company that provides such extensions."
>
> This tag line is a link to page describing 6wind and other vendors leaves a biased taint
> on the initial impression. It would be best to only put in historical data
> about the contributing companies and a vague reference to commercial support being
> available.
>
> It is not like kernel.org has links to SUSE and RHEL. We need to make DPDK.org
> independent.
>
I agree. Aspirations to greater neutrality can do nothing but bring in
additional developers.
Neil
prev parent reply other threads:[~2015-01-31 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 20:47 Stephen Hemminger
2015-01-31 21:20 ` Thomas Monjalon
2015-01-31 21:55 ` Neil Horman [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=20150131215511.GA28666@localhost.localdomain \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).