All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Stephen Hemminger
	<stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Making DPDK.org more vendor neutral
Date: Sat, 31 Jan 2015 22:20:23 +0100	[thread overview]
Message-ID: <4503715.e93PdNNrNX@xps13> (raw)
In-Reply-To: <20150131204710.2bf9f5fa-CA4OZQ/Yy2Lykuyl+CZolw@public.gmane.org>

Hi Stephen,

2015-01-31 20:47, Stephen Hemminger:
> I think that DPDK.org should be as neutral in all public communications.

I agree and thought it was already OK.

> 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.

Maybe that these words leave a biased taint, as you say.
The goal is to show that DPDK ecosystem can offer some services and support
if needed. It's an important information when choosing to use a software.
We can try to reword it as you suggest.

> It is not like kernel.org has links to SUSE and RHEL. We need to make DPDK.org
> independent.

Linux is very well known and its ecosystem is really huge.
I hope that one day, everybody will be confident enough to not hesitate
choosing DPDK. We made huge progress for 2 years by opening the development
process but I feel it's too early to be compared with kernel.org ;)

Thank you for your report, we'll try to fix it at best.
-- 
Thomas

  parent reply	other threads:[~2015-01-31 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31 20:47 Making DPDK.org more vendor neutral Stephen Hemminger
     [not found] ` <20150131204710.2bf9f5fa-CA4OZQ/Yy2Lykuyl+CZolw@public.gmane.org>
2015-01-31 21:20   ` Thomas Monjalon [this message]
2015-01-31 21:55   ` Neil Horman

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=4503715.e93PdNNrNX@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.