DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, dpdk-techboard <techboard@dpdk.org>
Cc: fengchengwen@huawei.com, mb@smartsharesystems.com,
	ferruh.yigit@amd.com,
	"Nathan Southern" <nsouthern@linuxfoundation.org>,
	"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: [ADDENDUM] Technical board meeting agenda for 2023-09-20
Date: Tue, 19 Sep 2023 11:51:05 +0200	[thread overview]
Message-ID: <5880754d-0996-9f49-6c09-f5c9ac53335b@redhat.com> (raw)
In-Reply-To: <524fc5ae-229c-7ee8-ba1b-cfd1fcc71235@redhat.com>

Dear community,

One topic was missed to be added to tomorrow's meeting agenda:

On 9/18/23 22:20, Maxime Coquelin wrote:
> Dear DPDK community,
> 
> Following topics are planned to be discussed at the next Technical board
> meeting, which will take place on Sept. 20th @3PM UTC:
0- Event dispatcher library inclusion

>   1- Memarea library inclusion
>   2- Power management brainstorming
>   3- Bugzilla maintenance: request for volunteers
>   4- Process to add new drivers
> 
> The order the topics will be discussed may change based on their
> priority/urgency. Some topics might have to be postponed to the
> following meeting if time does not allow to cover them.
> 
> If time permits, below recurring items will be checked:
>   - Security process
>   - Community Lab
>   - Doc maintenance
>   - Bugzilla status
>   - Examples to drop or move


  reply	other threads:[~2023-09-19  9:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 20:20 Maxime Coquelin
2023-09-19  9:51 ` Maxime Coquelin [this message]
2023-09-19 13:53   ` [ADDENDUM] " Morten Brørup
2023-09-20  9:57     ` Ferruh Yigit
2023-10-08  1:04 ` fengchengwen

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=5880754d-0996-9f49-6c09-f5c9ac53335b@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@amd.com \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=mb@smartsharesystems.com \
    --cc=nsouthern@linuxfoundation.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).