Minutes of Technical Board Meeting, 2022-April-20
Members Attending --------------------------- -Aaron -Bruce -Hemant -Honnappa -Jerin -Konstantin (chair) -Maxime -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-May-4 @3pm UTC, and will be chaired by Kevin. 1) Testpmd gRPC support https://patches.dpdk.org/project/dpdk/cover/20220407214707.29730-1-ohily...@iol.unh.edu/ Discussion summary: In general seems like a move in a right direction, though there are some concerns about amount and complexity of the new code to be added. Need to implement some realistic test-case to better understand/estimate all complexities and implications. CLI/gRPC interface: while gRPC should be very useful for CI, we still need to support CLI interface for developers (and current testing environment). So both interfaces should co-exist. For future direction: to minimize amount of code and simplify CLI support, we may consider to re-implement existing CLI commands on top of gRPC interface. Conclusion: TB recommendation to go ahead with RFCv2 that should cover some realistic testpmd scenario (http://git.dpdk.org/tools/dts/tree/test_plans/nic_single_core_perf_test_plan.rst or so). 2) Enrolment DPDK into HackerOne bug bounty program https://www.hackerone.com/ Q&A session: - align with the big community of hackers - H1 team can do the initial investigation of reported vulnerabilities - Disclosure policy can be defined by the community itself - Mostly finding and reporting tool at that moment: actual fixing is usually out of scope, but might be encouraged by reward policy. - Kubernetes involvement (http://hackerone.com/kubernetes) as an successful example of open-source project enrolment. - Can be tried/evaluated for limited amount of time (year/few months). Concerns raised: - Could be a lot of false-positives that H1 triage wouldn't be able to cope with (at least at initial stage), so still would require significant effort from DPDK security team (and rest of the community) for further evaluation and (/or) fixing. No final decision met, discussion to continue. 3) Technical Writer interview process Bruce and Stephen (as native English speakers) agreed to conduct. Suggested to inform other TB members about forth-coming interviews, so other interested people (Thomas, Jerin, Konstantin) can participate too. 4) DPDK UserSpace 2022 event schedule Discussion in progress.
