From: Thomas Monjalon <thomas@monjalon.net>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "web@dpdk.org" <web@dpdk.org>,
"O'Hare, Cathal" <cathal.ohare@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Jill Lovato <jlovato@linuxfoundation.org>,
Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
Subject: Re: [dpdk-web] Adding a new hosted project link for PMDT
Date: Wed, 19 Feb 2020 18:26:21 +0100 [thread overview]
Message-ID: <4070340.n0HT0TaD9V@xps> (raw)
In-Reply-To: <CY4PR11MB1512F5300531AE3147C453F7FE100@CY4PR11MB1512.namprd11.prod.outlook.com>
19/02/2020 18:00, Wiles, Keith:
> I guess the techbroad meeting was last week
> and I have not heard the status of that meeting.
> I would like to get the web pages updated,
> so what is the current status?
I was waiting for the minutes to be approved.
Given there are no more feedbacks from the techboard,
I will publish it now.
The decision from the techboard is to approve PMDT hosting
after these guidelines are addressed:
- compile and run on most DPDK supported environments
- no out-of-tree DPDK patches
- no copy of code from another project
- list dependencies
- have a license file or directory
- describe contribution process for patches and issues reporting
Note: these guidelines will serve for any other future project requests.
prev parent reply other threads:[~2020-02-19 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 16:25 Wiles, Keith
2020-02-10 16:32 ` Trishan de Lanerolle
2020-02-10 16:55 ` Wiles, Keith
2020-02-10 17:22 ` Trishan de Lanerolle
2020-02-10 17:36 ` Thomas Monjalon
2020-02-10 18:39 ` Honnappa Nagarahalli
2020-02-10 19:30 ` Wiles, Keith
2020-02-10 19:31 ` Wiles, Keith
2020-02-10 19:47 ` Wiles, Keith
2020-02-10 20:14 ` Thomas Monjalon
2020-02-19 17:00 ` Wiles, Keith
2020-02-19 17:26 ` 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=4070340.n0HT0TaD9V@xps \
--to=thomas@monjalon.net \
--cc=cathal.ohare@intel.com \
--cc=ferruh.yigit@intel.com \
--cc=jlovato@linuxfoundation.org \
--cc=john.mcnamara@intel.com \
--cc=keith.wiles@intel.com \
--cc=tdelanerolle@linuxfoundation.org \
--cc=web@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).