From: Jerin Jacob <jerinj@marvell.com>
To: dev <dev@dpdk.org>, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Proposal: AI-Based Code Review for DPDK
Date: Fri, 13 Jun 2025 10:03:16 +0000 [thread overview]
Message-ID: <BY3PR18MB478574FF76D2777FFACB1B00C877A@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
Goals
-------
# Leverage modern AI-powered code review tools to accelerate and supplement human review efforts.
# Prevent AI-generated comments from cluttering the mailing list or polluting the main DPDK GitHub repository.
Setup
-------
# Create a dedicated repository:
Set up a new repository, for example: https://github.com/DPDK/dpdk-ai-code-review, under the official DPDK GitHub organization.
This ensures that AI-generated pull requests do not interfere with the main repository (https://github.com/DPDK/dpdk).
# Select an AI review tool:
Use a free, open-source-friendly AI code review service.
One potential candidate is Sourcery: https://sourcery.ai/pricing
# Connect the tool:
Integrate Sourcery with the new repository via: https://app.sourcery.ai/?product=prod_opensource
# Trigger AI reviews:
Once integrated, any pull request to this repository will automatically trigger a code review by the AI tool.
Example of a test PR reviewed by the AI bot:
https://github.com/MarvellEmbeddedProcessors/dao/pull/2
Workflow
-------------
# When a patch is sent to the DPDK mailing list, a bot will convert it into a GitHub pull request on the dpdk-ai-code-review repository.
# The AI tool will review the pull request and leave comments directly on the PR.
# Once the AI review is complete, the bot will close the PR and share the PR URL:
- As a comment in Patchwork URL for the given patch
- With the patch author directly.
# The author can review the AI-generated comments by visiting the PR URL, if they choose to do so.
reply other threads:[~2025-06-13 10:03 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=BY3PR18MB478574FF76D2777FFACB1B00C877A@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.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).