From: Daniel Gomez <da.gomez@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>,
Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
Mel Gorman <mgorman@techsingularity.net>, Jan Kara <jack@suse.cz>,
David Bueso <dave@stgolabs.net>,
Qazi@infradead.org, Shoaib Asif <shoaibasif@vt.edu>,
"Liam R . Howlett" <liam.howlett@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
kdevops@lists.linux.dev
Subject: Re: [PATCH] docs: declare kdevops a software 3.0 enabler
Date: Wed, 23 Jul 2025 21:19:31 +0200 [thread overview]
Message-ID: <7751a3cc-5c44-4610-be37-cb79c866103c@kernel.org> (raw)
In-Reply-To: <20250723012150.899773-1-mcgrof@kernel.org>
On 23/07/2025 03.21, Luis Chamberlain wrote:
> For a long time we've worked hard to make it easier to extend kdevops
> with strict rules and clear declarative language. We've been so strict
> on some of these policies I'm quite sure it discouraged some developers.
> The projections and hope was that these strict goals would reduce the
> barrier to the use of generative AI for extending kdevops.
>
> Although we've been experimenting with different AI agents on kdevops
> for a while now, advanced AI agent tools such as Claude Code bring this
> closer to home, enabling prompts to complete about 70-95% of the tasks.
> In a short span of about one week we've been able to cut through a huge
> back log of work which would have otherwise taken us considerable amount
> of time. This, and our automated tests put in place gives us confidence
> to declare that the time is here and now and it should be easy for
> others to also extend kdevops for their needs with generative AI.
>
> Extend our documentation with the rationale of the implicit long term
> goals we had, make these explicit, and also provide guidance for Claude
> Code. We also provide some recent prompt examples and respective commits
> merged which should be useful for users wishing to look to extend
> kdevops.
>
> CLAUDE.md [0] is a special file that Claude automatically pulls into
> context when starting a conversation. This makes it an ideal place
> for documenting:
>
> - Common commands folks should be aware of that we run
> - Core files and utility functions
> - Code style guidelines
> - Testing instructions
> - Repository etiquette (e.g., branch naming, merge vs. rebase, etc.)
> - Developer environment setup
> - Any unexpected behaviors or warnings particular to the project
> - Other information you want Claude to remember
>
> We extend this to ensure the DCO is respected and also give it
> a few prompts examples and target historical commits with respective
> grades.
>
> Also, extend the video documentation links with the recent kdevops talk
> in Open Source Summit North America [1] where I mentioned for the first time
> publicly that kdevops was Software 3.0 enabler for Linux kernel development.
>
> Link: https://www.anthropic.com/engineering/claude-code-best-practices # [0]
> Link: https://www.youtube.com/watch?v=VF-jr_ZE-9Y&list=PLjaT52x3HVboZtdwZnONSHQHM8217ELcc # [1]
> Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
Same as Chuck, no objection and no expertise (for now).
Acked-by: Daniel Gomez <da.gomez@samsung.com>
I've also installed Claude Code and checked if the new files were read by the
AI and it looks good. It just works out of the box. I've also tested with a few
TODOs I had pending to solve from these series [1] and with a few iterations it
managed to be successful and very useful [2]. Looking forward to wipe out my
kdevops backlog with this Generative AI.
Link: https://lore.kernel.org/kdevops/0083fcfe-5c6d-4a9b-8ea6-1fb08a93e23f@kernel.org/T/#t [1]
Link: https://github.com/dkruces/kdevops/commits/b4/ansible_cfg_inventory [2]
Tested-by: Daniel Gomez <da.gomez@samsung.com>
next prev parent reply other threads:[~2025-07-23 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 1:21 [PATCH] docs: declare kdevops a software 3.0 enabler Luis Chamberlain
2025-07-23 14:44 ` Chuck Lever
2025-07-23 20:03 ` Luis Chamberlain
2025-07-23 19:19 ` Daniel Gomez [this message]
2025-07-23 20:00 ` Luis Chamberlain
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=7751a3cc-5c44-4610-be37-cb79c866103c@kernel.org \
--to=da.gomez@kernel.org \
--cc=Qazi@infradead.org \
--cc=cel@kernel.org \
--cc=da.gomez@kruces.com \
--cc=dave@stgolabs.net \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=kdevops@lists.linux.dev \
--cc=liam.howlett@oracle.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=mcgrof@kernel.org \
--cc=mgorman@techsingularity.net \
--cc=shoaibasif@vt.edu \
--cc=slava@dubeyko.com \
--cc=vbabka@suse.cz \
/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