DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, DPDK Techboard <techboard@dpdk.org>
Subject: Re: [dpdk-dev] Minutes of Technical Board Meeting, 2020-12-16
Date: Tue, 12 Jan 2021 07:53:47 -0800	[thread overview]
Message-ID: <20210112075347.12c840b2@hermes.local> (raw)
In-Reply-To: <20210104075226.GH2631@platinum>

On Mon, 4 Jan 2021 08:52:26 +0100
Olivier Matz <olivier.matz@6wind.com> wrote:

> Minutes of Technical Board Meeting, 2020-12-16
> 
> Members Attending
> -----------------
> 
> - Bruce
> - Ferruh
> - Hemant
> - Honnappa
> - Jerin
> - Kevin
> - Konstantin
> - Maxime
> - Olivier (chair)
> - Stephen
> - Thomas
> 
> NOTE: The technical board meetings every second Wednesday on Jitsi [0]
> at 3pm UTC. Meetings are public and DPDK community members  are welcome
> to attend.
> 
> NOTE: Next meeting will be on Wednesday 2021-01-13 @3pm UTC, and will be
> chaired by Stephen.
> 
> 1/ Lab investments
> ==================
> 
> Did current 101k /year investment reach the goal we set up earlier?
> -------------------------------------------------------------------
> 
> - The lab is currently used for performance tests, CI
> - It helped to find some functional bugs
> - It is needed for baremetal tests or performance tests (which cannot be
>   done by a cloud test infrastructure)
> - The infrastructure is there, we can use it better
> 
> Governing board asks about the proposal to add 30k /year to increase coverage
> -----------------------------------------------------------------------------
> 
> The proposal is to increase from 20 to 40 hours per week coverage,
> adding 2 more student employees.
> 
> One issue now is there is one person every 2 days. Is it possible to
> have the same coverage hours, but having an every-day presence?
> 
> Governing board asks Techboard to come with a single name as lab owner
> ----------------------------------------------------------------------
> 
> A lab owner is a project manager that tracks what was agreed to do, and
> find some help if needed. Ideally, it is a technical person used to
> develop in DPDK.
> 
> No good solution was found. The following ideas have been mentioned:
> 
> a/ Round-robin from techboard? A quarterly basis is too short compared
>    to ramp-up time, and longer periods are too long for one person.
> b/ Can it be managed by Linux Foundation? (maybe ask Trishan?)
> c/ Nobody
> 
> Question to ask to Govboard:
> 
> - What is the detail of the costs (infrastructure, electricity, people)?
> 
> Distributed CI should be high priority, therefore sharing test scripts
> is important. It might be easier for a company to pay someone working in
> its own lab.

I would like to not take all of tomorrows meeting discussing the CI lab.
What are the action items still left on this topic?

      reply	other threads:[~2021-01-12 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04  7:52 Olivier Matz
2021-01-12 15:53 ` Stephen Hemminger [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=20210112075347.12c840b2@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.com \
    --cc=techboard@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).