From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: qin.chunhua@zte.com.cn
Cc: dev@dpdk.org, users@dpdk.org
Subject: Re: Project Governance and Linux Foundation
Date: Wed, 12 Oct 2016 00:43:01 -0700 (PDT) [thread overview]
Message-ID: <3947933.oyJplKdvEH@xps13> (raw)
In-Reply-To: <OF3421A464.9F382155-ON4825804A.001F4E8F-4825804A.001F880D@zte.com.cn>
Hi,
This is a really interesting use case.
Questions below,
2016-10-12 13:44, qin.chunhua@zte.com.cn:
> ZTE is supportive of improving the DPDK project governance including
> moving the project to the Linux Foundation.
> DPDK has been used in lots of ZTE's equipments and solutions such as
> BBU,RNC,EPC,vEPC,vBRAS,vCPE,vRouter,vSwitch,and so on for many years.
> We have also done some optimization in DPDK.
You mean you made some optimizations to DPDK but keep them secret?
> If the DPDK project governance moves to the Linux Foundation,
> we think this will promote ZTE and other companies to contribute in DPDK.
Why it would help you to contribute?
Why not contribute today?
The project is truly open, a lot of major companies are contributing,
why not yours?
next prev parent reply other threads:[~2016-10-12 7:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 5:44 Project Governance and Linux Foundation qin.chunhua
2016-10-12 7:43 ` Thomas Monjalon [this message]
2016-10-13 6:10 ` [dpdk-users] " Muhammad Zain-ul-Abideen
-- strict thread matches above, loose matches on Subject: below --
2016-10-10 8:33 O'Driscoll, Tim
2016-10-17 10:23 ` Hobywan Kenoby
2016-10-17 11:52 ` O'Driscoll, Tim
2016-10-17 21:23 ` Dave Neary
2016-10-18 11:34 ` Jerin Jacob
2016-10-18 13:27 ` Thomas Monjalon
2016-10-18 16:26 ` Jerin Jacob
2016-10-19 8:04 ` O'Driscoll, Tim
2016-10-19 8:40 ` Dave Neary
2016-10-19 9:56 ` Thomas Monjalon
2016-10-19 9:09 ` Jerin Jacob
2016-10-21 14:00 ` Dave Neary
2016-10-21 17:20 ` Wiles, Keith
2016-10-22 19:27 ` Thomas Monjalon
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=3947933.oyJplKdvEH@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=qin.chunhua@zte.com.cn \
--cc=users@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 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.