From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Tech Board Meeting Minutes - 2025-Jan-08
Date: Wed, 15 Jan 2025 23:23:39 +0000 [thread overview]
Message-ID: <24f74e2509034c859423d53485db1ef3@huawei.com> (raw)
Members Attending
-------------------------
Aaron Conole
Bruce Richardson
Hemant Agrawal
Kevin Traynor
Konstantin Ananyev (chair)
Maxime Coquelin
Morten Brørup
Stephen Hemminger
Thomas Monjalon
NOTE: The technical board meetings are on every second Wednesday at 3pm
UTC. Meetings are public, and DPDK community members are welcome to
attend. Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
Next meeting will be on Wednesday 2025-Jan-[] 22 @ 3pm UTC, and will be chaired by Maxime Coquelin
Agenda Items
============
1) A DPDK summit in Prague at May approved.
The Tech-Board intention is to start CFP process as soon as possible.
2) Discussion of motivation methods for new/existing tree maintainers and reviewers
Initiated by Thomas: what can be done to keep existing maintainers and reviewers interested
and focused, and to bring-up new people for that role.
In particular, it was noted a necessity to encourage more community members for
on-time and high-quality code reviews.
It was suggested to think up possible rewards system for that
(subscriptions, conference attendings, gifts, etc.).
Bruce pointed out that apart from motivating individual contributors, we need to
make member companies realize the importance of such roles within their employees.
Next steps: Thomas to send email to TB with the initial propositions.
TB members to provide their comments and further thoughts that will be compiled
to the final version to propose to the GB.
3) Last but not least: tech-board wishes a very happy NY to all members of the community :)
reply other threads:[~2025-01-15 23:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=24f74e2509034c859423d53485db1ef3@huawei.com \
--to=konstantin.ananyev@huawei.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).