From: Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>, dpdk-web <web@dpdk.org>,
Jill Lovato <jlovato@linuxfoundation.org>,
dpdk-techboard <techboard@dpdk.org>
Subject: Re: [dpdk-web] Hosted project
Date: Mon, 2 Dec 2019 16:07:40 +0200 [thread overview]
Message-ID: <CAFXL6f_QWZjQtHwVtP7Oq43JqmgKmckFvgjVOzFZkj9Eyun0aA@mail.gmail.com> (raw)
In-Reply-To: <3395816.fun287xAU0@xps>
Yes. The licensing should be the same. If not, an exception from the board
is required.
It would be good to give clarification around what type of projects would
be hosted by us as DPDK. How do they tie back to DPDK and what value do
they bring, for instance.
Trishan
On Mon, Dec 2, 2019, 3:01 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> 02/12/2019 13:14, Ferruh Yigit:
> > Hi Trishan, Thomas,
> >
> > What do you think documenting process of hosting a project under
> dpdk.org in the
> > hosted projects page [1] ?
> >
> > I think it can be something like that:
> > "
> > Hosting a project under dpdk.org requires the Technical Board approval,
> please
> > send the project hosting requests to techboard@dpdk.org.
> > "
>
> I agree, it is required.
>
> > Not sure if we should list the required conditions (licensing, purpose,
> > maturity, etc...) for hosting a project, if so we should define them
> fist J,
> > cc'ed tech board for it.
>
> I think the code of all projects should comply with the same rules
> as DPDK (BSD and/or GPL).
> Trishan, do you confirm?
>
>
> ,
next prev parent reply other threads:[~2019-12-02 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 12:14 Ferruh Yigit
2019-12-02 13:01 ` Thomas Monjalon
2019-12-02 14:07 ` Trishan de Lanerolle [this message]
2019-12-19 20:37 ` 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=CAFXL6f_QWZjQtHwVtP7Oq43JqmgKmckFvgjVOzFZkj9Eyun0aA@mail.gmail.com \
--to=tdelanerolle@linuxfoundation.org \
--cc=ferruh.yigit@intel.com \
--cc=jlovato@linuxfoundation.org \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
--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).