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, 2022-05-04
Date: Fri, 13 May 2022 10:02:02 +0100
Message-ID: <e8e2b680-01b4-dd0b-b517-1761e6a99fcd@redhat.com> (raw)

Minutes of Technical Board Meeting, 2022-May-04

Members Attending
-Kevin (chair)

NOTE: The technical board meetings are on 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 2021-May-18 @3pm UTC, and will
be chaired by Maxime.

1) Enrollment DPDK into HackerOne bug bounty program
    - Discussed if the DPDK security process/resourcing should be
      beefed up in advance of engagement into any bug bounty program
    - Kevin to send email to security team to identify any areas that
      need more resources or improvements to process

2) DPDK UserSpace 2022 event schedule
    - Not enough feedback so far about suggested event
    - Kevin to poll TB members

3) DTS into DPDK repo progress
    - Honnappa shared status/plans on integrating DTS into DPDK repo
    - Patches to integrate it will aim to be based on incremental
      features and functional boundaries
    - A roadmap for this will be provided
    - Honnappa indicated that as this is a big migration of existing
      code, with limited resources, some aspects of the workflow will
      need to be best effort. e.g. coding standards
    - These will be noted and can be discussed as they arise on the ML
    - Overriding goal is that DTS can shine and be easily
      adopted/developed by DPDK developer base
    - Honnappa to send email to gather goals which can then provide the
      basis for where flexibility on workflow is allowed

                 reply	other threads:[~2022-05-13  9: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:

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

  git send-email \
    --in-reply-to=e8e2b680-01b4-dd0b-b517-1761e6a99fcd@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=dev@dpdk.org \


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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/dev/0 dev/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 dev dev/ http://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

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