From: Thomas Monjalon <thomas@monjalon.net>
To: "Melik-Adamyan, Areg" <areg.melik-adamyan@intel.com>
Cc: dev@dpdk.org, "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
"Wiles, Keith" <keith.wiles@intel.com>
Subject: Re: Project move under DPDK.org umbrella.
Date: Fri, 23 Jun 2017 10:12:28 +0200 [thread overview]
Message-ID: <2749701.NIVXY2Dhhr@xps> (raw)
In-Reply-To: <ABCD154DCB698E4BA9B0815185C1385FA2759ECD@fmsmsx104.amr.corp.intel.com>
Hi,
22/06/2017 23:58, Melik-Adamyan, Areg:
> Per our discussion within Intel, I am sending official request to DPDK community to include our cloud network function framework YANFF - https://www.github.com/intel-go/yanff to DPDK.org. As it is using DPDK underneath and provides higher level abstraction for enabling development of cloud network function in a native way, we hope that it will be good addition in enhancing DPDK community.
> Please let me know what are the steps and from our side I am ready to provide more detailed information.
It's good to see more and more projects using DPDK.
I think you should write a page in your project to explain what benefit
it brings to the application developper, compared to directly using DPDK.
>From what I read, I keep the words "framework" and "higher level" which
are not so informative in my opinion :)
About requesting an integration in dpdk.org, it must be approved by
the Technical Board and the Governing Board, as described in the charter:
http://dpdk.org/about/charter
Anyway, it should be added in this page:
http://dpdk.org/about/ecosystem
prev parent reply other threads:[~2017-06-23 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 21:58 Project move under DPDK.org umbrella Melik-Adamyan, Areg
2017-06-22 22:07 ` Stephen Hemminger
2017-06-23 8:12 ` Thomas Monjalon [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=2749701.NIVXY2Dhhr@xps \
--to=thomas@monjalon.net \
--cc=areg.melik-adamyan@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=tim.odriscoll@intel.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 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.