[dpdk-dev] DPDK techboard minutes (2019-04-10)

[dpdk-dev] DPDK techboard minutes (2019-04-10)

[Olivier Matz]

Hi,

Here are the meeting notes of the DPDK technical board meeting held on
2019-04-10.

Attendees:

- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon

1) DPDK development process and tools survey
============================================

Reference: https://mails.dpdk.org/archives/dev/2019-March/126114.html

The objective of the survey is to detect problems (if any) in our
current process.

- The survey is now closed.
- Unfortunately the number of received responses is low compared to the
  number of active DPDK developers.
- The answers and feedback will be gathered and summarized by mail.
- There will be a Q&A session on this topic at next Europe DPDK summit.

2) DPDK API Stability discussion
================================

Reference: https://mails.dpdk.org/archives/dev/2019-April/128969.html

- Following the discussion on the ML, there is a consensus that API/ABI
  stability is a direction where the DPDK project should head for.
- Adding automated tools to check API/ABI stability is a good first step.
  Here is a list of ABI checker tools:
  - ABI Laboratory: https://abi-laboratory.pro/index.php?view=timeline&l=dpdk
  - https://sourceware.org/libabigail
  - https://lvc.github.io/abi-compliance-checker
  - The current dpdk tool, validate-abi.sh, is based on abi-compliance-checker.
- Patches like this one proposed by Stephen Hemminger should be generalized
  to other parts of DPDK (everything that is not rx/tx path):
  http://patches.dpdk.org/project/dpdk/list/?series=4248
- An "ABI/API stability" item will be added to techboard recurring topics.
- The documentation (guides/contributing/versioning,
  guides/contributing/design) and website (including roadmap) should be
  updated to highlight and explain the intent (Ray proposed himself).
- No calendar/deadlines was decided, let's discuss it again at next
  techboard meeting.

3) SPDX licenses
================

There are still some old license headers in Intel driver base code, they
will be replaced by new shared code drops.

[dpdk-dev] DPDK techboard minutes (2019-04-10)

[Olivier Matz]

Hi,

Here are the meeting notes of the DPDK technical board meeting held on
2019-04-10.

Attendees:

- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon

1) DPDK development process and tools survey
============================================

Reference: https://mails.dpdk.org/archives/dev/2019-March/126114.html

The objective of the survey is to detect problems (if any) in our
current process.

- The survey is now closed.
- Unfortunately the number of received responses is low compared to the
  number of active DPDK developers.
- The answers and feedback will be gathered and summarized by mail.
- There will be a Q&A session on this topic at next Europe DPDK summit.

2) DPDK API Stability discussion
================================

Reference: https://mails.dpdk.org/archives/dev/2019-April/128969.html

- Following the discussion on the ML, there is a consensus that API/ABI
  stability is a direction where the DPDK project should head for.
- Adding automated tools to check API/ABI stability is a good first step.
  Here is a list of ABI checker tools:
  - ABI Laboratory: https://abi-laboratory.pro/index.php?view=timeline&l=dpdk
  - https://sourceware.org/libabigail
  - https://lvc.github.io/abi-compliance-checker
  - The current dpdk tool, validate-abi.sh, is based on abi-compliance-checker.
- Patches like this one proposed by Stephen Hemminger should be generalized
  to other parts of DPDK (everything that is not rx/tx path):
  http://patches.dpdk.org/project/dpdk/list/?series=4248
- An "ABI/API stability" item will be added to techboard recurring topics.
- The documentation (guides/contributing/versioning,
  guides/contributing/design) and website (including roadmap) should be
  updated to highlight and explain the intent (Ray proposed himself).
- No calendar/deadlines was decided, let's discuss it again at next
  techboard meeting.

3) SPDX licenses
================

There are still some old license headers in Intel driver base code, they
will be replaced by new shared code drops.