DPDK website maintenance
 help / color / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: ci@dpdk.org, alialnu@mellanox.com, lijuan.tu@intel.com,
	tim.odriscoll@intel.com, web@dpdk.org
Subject: Re: [dpdk-web] [dpdk-ci] [PATCH] add a link to the CI dashboard
Date: Thu, 08 Nov 2018 14:28:24 +0100
Message-ID: <32826685.tUcjU3XkpW@xps> (raw)
In-Reply-To: <CAOE1vsPucqZBSxMN4N_FE=p_3Ccam2ppczNtF018JOEtcSUfVQ@mail.gmail.com>

08/11/2018 14:13, Lincoln Lavoie:
> On Thu, Nov 8, 2018 at 3:14 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> > 08/11/2018 08:46, Ali Alnubani:
> > > +  {{< button href="https://lab.dpdk.org" >}} CI Dashboard {{< /button
> >
> > It is important to keep in mind that we support a distributed CI approach.
> > This lab is an important part of the CI, but we can run other tests
> > in other labs. That's why I think we must really stick with a specific name
> > for this lab.
> > Several names were mentionned so far:
> >         - performance lab
> >         - UNH lab
> >         - reference lab
> >         - community lab
> >
> > I think we must decide which name we want to use.
> > Opinions?
> Would "UNH-IOL Performance Lab" be acceptable?  I'm thinking this would be
> along the lines of Host / Purpose.  So, taking an example, if Acme hosted a
> build lab, it could be "Acme Build Lab" or something like that.  In terms
> of project branding, maybe we need to develop some messaging around how the
> labs are part of the project.  I'm thinking similar to how OPNFV has the
> "Pharos Labs," which they describe as "a federated NFV testing
> infrastructure of community labs around the world."  I think the goal would
> be to describe the labs as a community resource, supporting to DPDK project
> and it's developers.

I agree we must improve the communication about the distributed CI.
Starting with good naming is a good step for communicating :)

Let's discuss your proposal "UNH-IOL Performance Lab".
About "UNH-IOL", yes it is accurate, but we may want to show it as
THE lab which is shared by several community members, not only
the lab hosted at UNH.
About "Performance" word, I think we should avoid that name
because the lab will probably be used for functionnal testing as well.

Another proposal sent in parallel of this mail by Tim: "DPDK Open Lab".
I am in favor of "DPDK Community Lab".

      parent reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181108074622.5215-1-alialnu@mellanox.com>
2018-11-08  8:14 ` [dpdk-web] " Thomas Monjalon
2018-11-08 13:13   ` [dpdk-web] [dpdk-ci] " Lincoln Lavoie
2018-11-08 13:24     ` O'Driscoll, Tim
2018-11-08 13:31       ` Lincoln Lavoie
2018-11-08 14:23         ` O'Driscoll, Tim
2018-11-08 13:28     ` Thomas Monjalon [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32826685.tUcjU3XkpW@xps \
    --to=thomas@monjalon.net \
    --cc=alialnu@mellanox.com \
    --cc=ci@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=tim.odriscoll@intel.com \
    --cc=web@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK website maintenance

Archives are clonable:
	git clone --mirror http://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/ http://inbox.dpdk.org/web \
	public-inbox-index web

Newsgroup available over NNTP:

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