DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2021-08-25
Date: Fri, 10 Sep 2021 14:25:46 +0000	[thread overview]
Message-ID: <DU2PR04MB8630F25B95DA97499C4340FA89D69@DU2PR04MB8630.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <DU2PR04MB8630C0339D3CFB3CDE952B1389D69@DU2PR04MB8630.eurprd04.prod.outlook.com>



Minutes of Technical Board Meeting, 2021-08-25



Members Attending: 11/12

- Aaron Conole

- Bruce Richardson

- Ferruh Yigit

- Hemant Agrawal (Chair)

- Honnappa Nagarahalli

- Jerin Jacob

- Kevin Traynor

- Maxime Coquelin

- Olivier Matz

- Stephen Hemminger

- Thomas Monjalon



NOTE: The Technical Board meetings take place every second Wednesday on  https://meet.jit.si/DPDK  at 3 pm UTC.

Meetings are public, and DPDK community members are welcome to attend.

Agenda and minutes can be found at https://annuel.framapad.org/p/r.0c3cc4d1e011214183872a98f6b5c7db

NOTE: Next meeting will be on Wednesday 2021-09-08 @3pm UTC, and will be chaired by Honnappa





#1 DPDK User list

                * Eco system user list required.

                * A survey may help in generating such list.

                * LF Marketing may also help in getting such list generated from public info.



#2 API/ABI breakage exception approval for vhost API

                - The policy is that one should not break the API/ABI even for LTS releases without previous notification. Exception can be approved for LTS.

              - In this particular case, they shall try to do function versioning. AI- Ferruh to send response.



#3 Documenting criteria on adding/removing members to technical board

    * Document needs further reviews, please review.

    * Will set a deadline for the document review in next meeting.

    * Need clear rules for the review of existing members membership.



#4 ORAN API License

    * ORAN forum is planning to use SCCL license in the API file. Will that be acceptable for DPDK integration?

    * Members need more details. Currently distros may not favor it as it may cause issue in source code distribution.

    * Need to discuss more if TB can send it for review by DPDK GB.


           reply	other threads:[~2021-09-10 14:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <DU2PR04MB8630C0339D3CFB3CDE952B1389D69@DU2PR04MB8630.eurprd04.prod.outlook.com>]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=DU2PR04MB8630F25B95DA97499C4340FA89D69@DU2PR04MB8630.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=techboard@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).