DPDK website maintenance
 help / color / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: thomas@monjalon.net
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, 8 Nov 2018 08:13:13 -0500
Message-ID: <CAOE1vsPucqZBSxMN4N_FE=p_3Ccam2ppczNtF018JOEtcSUfVQ@mail.gmail.com> (raw)
In-Reply-To: <3354634.DNSllWXiY1@xps>

Hi All,

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.

Cheers,
Lincoln

On Thu, Nov 8, 2018 at 3:14 AM Thomas Monjalon <thomas@monjalon.net> wrote:

> Note: such patch must be sent to web@dpdk.org.
>
> 08/11/2018 08:46, Ali Alnubani:
> > --- a/content/perf-lab/_index.md
> > +++ b/content/perf-lab/_index.md
> > @@ -3,6 +3,10 @@ title = "Performance Lab"
> >  weight = "8"
> >  +++
> >
> > +<center>
> > +  {{< button href="https://lab.dpdk.org" >}} CI Dashboard {{< /button
> >}}
> > +</center>
>
> 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?
>
>
>

-- 
*******************************************************************************
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies

<https://www.iol.unh.edu>
www.iol.unh.edu
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
lylavoie@iol.unh.edu
<http://www.facebook.com/UNHIOL#>   <https://twitter.com/#!/UNH_IOL>
<http://www.linkedin.com/company/unh-interoperability-lab>

Ars sine scientia nihil est! -- Art without science is nothing.
Scientia sine ars est vacua! -- Science without art is empty.

Broadband Forum Gfast Certified Product List
<https://www.broadband-forum.org/implementation/interop-certification/gfast-certified-products>
*******************************************************************************

  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   ` Lincoln Lavoie [this message]
2018-11-08 13:24     ` [dpdk-web] [dpdk-ci] " 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

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:
  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='CAOE1vsPucqZBSxMN4N_FE=p_3Ccam2ppczNtF018JOEtcSUfVQ@mail.gmail.com' \
    --to=lylavoie@iol.unh.edu \
    --cc=alialnu@mellanox.com \
    --cc=ci@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=thomas@monjalon.net \
    --cc=tim.odriscoll@intel.com \
    --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

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 \
		web@dpdk.org
	public-inbox-index web


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.web


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