DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2023-March-22
Date: Fri, 24 Mar 2023 10:02:39 +0000	[thread overview]
Message-ID: <0f972134-f071-e6ec-a9d7-ed589cd411ed@redhat.com> (raw)

Minutes of Technical Board Meeting, 2023-March-22

Members Attending
-----------------
-Aaron
-Bruce
-Hemant
-Jerin
-Kevin (Chair)
-Maxime
-Stephen
-Thomas

NOTE: The technical board meetings every second Wednesday at
https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.

NOTE: Next meeting will be on Wednesday 2023-April-05 @3pm UTC, and will
be chaired by Konstantin.

1) Marketing update (Nathan)
-We need to provide content to maximise the marketing resources
-A good example is Morten's content on using DPDK
https://www.dpdk.org/wp-content/uploads/sites/35/2023/02/DPDK_UserStory_SmartShare_020223.pdf

2) Event planning (Nathan)
-Dublin in September is most likely venue
-Difficult to estimate in-person attendance based on previous years and
economic environment
-Nathan will send out a survey to try and gauge interest for in-person
attendance

3) Technical Writer (Nathan)
-The hiring interviews are currently in progress.

4) Policy for obsolete patches (Bruce)
-A lot of pages in patchwork, should older patches be moved to a new
obsolete state?
-Adding a new state would cause difficulties for patchwork upgrade
-Reject state could be used
-A script to do automatically and send an email with links etc would be best
-Ali may be able to investigate a way to automate this

5) Code formatting tools (Bruce)
-Any way to better automate formatting of code?
-clang-format was suggested and already being used by some
-Stephen has been looking at this, he will send a patch to kick off

6) Multiple MAC address support and API behavior were discussed (Ferruh)
-Pros and cons to each approach
-Ferruh will propose solution for vote on email by techboard

7) Bugzilla usage (breakout from previous topic)
-Is it being used enough? Are bugs getting the right level of attention etc?
-Konstantin to add this as a topic for next techboard meeting


                 reply	other threads:[~2023-03-24 10:02 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=0f972134-f071-e6ec-a9d7-ed589cd411ed@redhat.com \
    --to=ktraynor@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 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).