Minutes of Technical Board Meeting, 2022-May-18

[Maxime Coquelin]

Members Attending
---------------------------
-Aaron
-Bruce
-Honnappa
-Konstantin
-Kevin
-Maxime (chair)
-Olivier
-Stephen
-Thomas

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-June-1 @3pm UTC, and will
be chaired by Olivier.

1) DTS into DPDK repo progress
  - DTS patches will require some quality exception to get into main
    repository
  - Patches are being prepared, they will be sent soon

2) CI testing with packet fuzzing
  - Thomas suggests packet fuzzing tools would be useful to find issues
    in drivers
  - The tool could be run on all interfaces to catch use-after-free and
    other kind of issues
  - One possibility could be to use Scapy or other packet generators to
    testpmd. Some concerns that Scapy would be too slow
  - Fuzzing tool should not be used for patch gating
  - Call for ideas for packet fuzzing tools

3) HackerOne bug bounty program
  - Nathan updated that discussions about DPDK enrollment into HackerOne
    program won't be pursued
  - Suggestion about having a hackathon during the DPDK UserSpace event

4) Techwriter hiring update
  - Nathan received 12 applications, he will wait for one more week to
    gather more applicants
  - A first filter will be based on applicants' published work

5) Security process feedback
  - Kevin sent a mail requesting feedback on current process from people
    involved in previous vulnerabilities handling
  - No feedback received for now

6) SPDK vulnerabilities pre-release mailing list membership
  - The techboard approved SPDK membership with 8 votes for
  - Stephen suggests to make the vulnerabilities pre-release mailing list
    more visible on dpdk.org's security pages

7) DPDK UserSpace event update
  - Conference budget has been approved by the Governing Board
  - The boat excursion has not been approved. Cocktail/dinner event will
    need to be approved separately