DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Trishan de Lanerolle <tdelanerolle@linuxfoundation.org>,
	Jill Lovato <jlovato@linuxfoundation.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>, dpdk-web <web@dpdk.org>
Subject: Re: [dpdk-web] Hosted project
Date: Thu, 19 Dec 2019 21:37:39 +0100
Message-ID: <4250928.EKeNd3h7qM@xps> (raw)
In-Reply-To: <CAFXL6f_QWZjQtHwVtP7Oq43JqmgKmckFvgjVOzFZkj9Eyun0aA@mail.gmail.com>

I think this web update request was forgot.


02/12/2019 15:07, Trishan de Lanerolle:
> 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?
> >
> >
> > ,
> 






      reply	other threads:[~2019-12-19 20:37 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
2019-12-19 20:37     ` 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=4250928.EKeNd3h7qM@xps \
    --to=thomas@monjalon.net \
    --cc=ferruh.yigit@intel.com \
    --cc=jlovato@linuxfoundation.org \
    --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

DPDK website maintenance

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/web/0 web/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 web web/ https://inbox.dpdk.org/web \
		web@dpdk.org
	public-inbox-index web

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.web


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git