All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: dev@dpdk.org
Subject: Tech Board Meeting Minutes, Nov-01, 2023
Date: Fri, 01 Dec 2023 10:30:15 -0500	[thread overview]
Message-ID: <f7tjzpyj5yw.fsf@redhat.com> (raw)

* Attendees
** Nathan Southern
** Thomas Monjalon
** Honnappa Nagarahalli
** Kevin Traynor
** Hemant Agrawal
** Jerin Jacob Kollanukkaran
** Ben Thomas
** Patrick Robb
** Lincoln Lavoie

* Agenda

** UNH Retrospective
*** Patrick presented the retrospective at
    https://docs.google.com/document/d/1Gxro7ga2Ml_DKAKeGrOcb2VxkkcUrU8DVkeAv28i0R8/edit?usp=sharing
*** Questions regarding the on going work related to hardware and DTS,
    but Patrick assures that most of the items will get done.

** Priority list voting
*** SOW Priority list items were presented to the :
    https://docs.google.com/spreadsheets/d/1DL1t_h-JOz1tTcO7hc8EpJnUQsHyj8YxJqx-JxrvKz0/edit#gid=0
    (NOTE: you'll need to now send a request to edit)
*** There does need to be a round of scoping from UNH to determine which
    items are feasible to do.  Aaron will be going to UNH tomorrow to
    discuss.
*** A follow up meeting needs to be scheduled for completing the review.

NOTE: The technical board meetings are on every second Wednesday at 3 pm
      UTC.
      Meetings are public, and DPDK community members are welcome to
      attend.
      Agenda and minutes can be found at
      http://core.dpdk.org/techboard/minutes
      
      Next meeting will be on Wednesday 2023-Nov-15 @ 3pm UTC, and will
      be chaired by Bruce.


                 reply	other threads:[~2023-12-01 15:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=f7tjzpyj5yw.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.