DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Minutes of Technical Board Meeting, 2023-01-11
Date: Fri, 5 May 2023 08:05:13 -0700	[thread overview]
Message-ID: <20230505080513.529663b1@hermes.local> (raw)
In-Reply-To: <DS0PR11MB73090EC350B82E0730D0D9A197CE9@DS0PR11MB7309.namprd11.prod.outlook.com>


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 2023-01-25 @ 3pm UTC, and will
be chaired by Bruce.

Agenda Items
============

1) C99 standard
---------------

Future support for C11 atomics raised the question of should C99 be
required for DPDK. Several places use C99 already but it is not project
wide. DPDK is using C11 now but marked as extension where used.

The open issues are:
  - do not want to require application to require C99 but
    want to allow applications using C99. This impacts inline in headers.
  - Need to announce. Should not cause API/ABI breakage.
  - the testing and infrastructure are impacted as well.
  - need to keep inline for performance reasons.

Bruce is adding build support for test and compatibility.
Investigating what fallout is from project wide enablement.

2) Technical Writer
------------------

Possible candidate did not work out. Two candidates under
review.

3) MIT License
--------------

Original Governing Board wording for MIT license exception
became overly complicated. Linux Foundation legal expert
revised it. Governing Board is reviewing.

4) Governing Board
------------------

DPDK Technical Board member to Governing Board:
  - past Stephen; current Thomas; next Aaron

Recent vote on modification to charter to codify treasurer role.

Discussion on marketing. The existing Linux Foundation model
has DPDK project paying for things that are not necessary and
not getting the expected support.

           reply	other threads:[~2023-05-05 15:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <DS0PR11MB73090EC350B82E0730D0D9A197CE9@DS0PR11MB7309.namprd11.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=20230505080513.529663b1@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).