TB Attendees
------------
Aaron
Bruce
Hemant
Honnappa
Jerin
Kevin
Konstantin
Maxime
Morten
Stephen
Thomas



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.
Link to join:
https://zoom-lfx.platform.linuxfoundation.org/meeting/96459488340?password=d
808f1f6-0a28-4165-929e-5a5bcae7efeb

NOTE: Next meeting will be on Wednesday 2023-Dec-13 @3pm UTC, and will be
chaired by Honnappa

1. Discussion of mandating DTS test case addition for new features.
   TB discussed the idea of mandating the addition of test cases for each
 new feature being added.
- DTS framework pieces are being merged in the main DPDK repo. It currently
supports Linux.
o Windows is still an exception. 
o Windows maintainers shall plan to make it work soon. 
- First patch that introduces a new feature shall include 1 positive and 1
negative test case.
- Subsequently, other PMDs adding support for this feature, shall add more
than 1 positive and more than 1 negative test cases or modify existing test
cases for code coverage.
- It is module/tree maintainers’ responsibility to
o ensure that test cases are submitted along with the patch
o help identify test cases if the patch owner cannot find one
- Thomas will help in updating it to contributing guidelines.
- As the DTS becomes ready, the TB will review and announce the effective
dates with enough notice in advance. 
- The current tentative timelines for these rules are:  (subject to DTS
readiness and TB approval for each step).
o effective for basic ethdev features on 2024 H2
o effective for all ethdev (including rte_flow) on early 2025
o effective for more libraries in 2025
- Future ideas
o Improve code coverage 
o Other samples applications in addition to testpmd

2. Discuss the outstanding issues in "redistribution" aspects of 
doc: define qualification criteria for external library patch
https://patches.dpdk.org/project/dpdk/patch/20230928054036.645183-1-jerinj@m
arvell.com/

                TB discussed various guidelines to be added to external
library support in DPDK.

- The distribution and usage license details about the external library
shall be documented within DPDK
o It shall be a permissive license such as BSD-3 or Apache and align with
the existing DPDK licenses. No GPL. 
o In case of mandatory components, libraries; Distros shall be able to use
them.
- They shall be optional to use and disabled by default.
- They shall be freely available to build with DPDK.
- They shall be downloadable from a direct link. There shall not be any
requirement to login or sign a user agreement. 
- They may be limited to the OS, they are supporting.
- It is yet to be decided about the applicability of the above rules to the
existing DPDK libraries.
- The voting on the above is not done – as the members wants to first see
the full draft of the rules.