DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ori Kam <orika@nvidia.com>, Aaron Conole <aconole@redhat.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dev <dev@dpdk.org>,
	 "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: Proposal: AI-Based Code Review for DPDK
Date: Fri, 27 Jun 2025 13:31:03 +0530	[thread overview]
Message-ID: <CALBAE1MTeqJKGy1EzXV1oCq2SxmN-Y4fm4LwwkAwcHbDy_2w3Q@mail.gmail.com> (raw)
In-Reply-To: <ccab20d4-8620-407c-b7a9-de5b81c4d6e8@nvidia.com>

On Thu, Jun 19, 2025 at 7:42 PM Ori Kam <orika@nvidia.com> wrote:
>
>
> Nice idea,
> Some comments:
>
>
> 1. The first link is broken for me.

Yes.  https://github.com/DPDK/dpdk-ai-code-review is the proposed name
of the repository. It is not created yet.

>
> 2. I like the idea that there is a separate GitHub repository. If I
>     understand correctly the new repository is a clone of the main one,
>     and only used by the bot is that correct?

Yes.

>
> 3. I think main usage is also for the reviewer, just like in your example.

Yes

>
> 4. The only thing I’m missing is that there is no “personal touch”
>     meaning that each reviewer puts emphasis on different things. It will
>     be great if the AI can learn from previous reviews of the reviewer
>     and add review accordingly.

Yes. However, It looks like https://docs.sourcery.ai/Code-Review/ dont
have that feature.

>
> 5. It will also be great if the AI could target people who may be
>     interested in this patch.  And send them some notification or tell
>     the developer to add them in the to

Good input.


Adding @Aaron Conole . He has some plans to implement this workflow.


>
> Best,
> Ori
>
> On 13/06/2025 13:03, Jerin Jacob wrote:
> >
> > 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-27  8:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 10:03 Jerin Jacob
2025-06-19 13:34 ` Ori Kam
2025-06-27  8:01   ` Jerin Jacob [this message]

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=CALBAE1MTeqJKGy1EzXV1oCq2SxmN-Y4fm4LwwkAwcHbDy_2w3Q@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=orika@nvidia.com \
    --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).