Skip to content

Add P4 Consortium Policy: AI Tool Use in Contributions#3

Open
Dscano wants to merge 4 commits intop4lang:mainfrom
Dscano:main
Open

Add P4 Consortium Policy: AI Tool Use in Contributions#3
Dscano wants to merge 4 commits intop4lang:mainfrom
Dscano:main

Conversation

@Dscano
Copy link

@Dscano Dscano commented Feb 28, 2026

Hi All,

Here’s the draft document for the P4 Consortium Policy: AI Tool Use in Contributions. This document was prepared by @fruffy, @smolkaj, and @asl. I supported them in drafting the proposal and finalizing it.

The draft is in good shape. The only thing missing is the Examples section, where we should add concrete examples to clarify the P4 Consortium Policy: AI Tool Use in Contributions.

Signed-off-by: Dscano <d.scano89@gmail.com>
Copy link
Member

@smolkaj smolkaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me!

AIPOLICY.md Outdated
- Comments and feedback on pull requests

# Contributor Responsibility
To ensure meaningful self-review and ownership, contributors should write PR descriptions themselves, AI tools may be used only for translation or copy-editing. PR descriptions must clearly cover the motivation, implementation approach, expected impact, and any open questions, to the same standard as non-AI contributions.First-time contributors who use AI tools must disclose that use in the PR description, commit message, or wherever authorship is normally indicated; long-time contributors and maintainers are exempt from mandatory disclosure but remain responsible for ensuring contributions comply with Linux Foundation and P4 community guidelines. A human must remain in the loop. Agents or automation may not take actions in project spaces, such as opening PRs, pushing commits, or posting review comments, without explicit human approval.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"contributors should write PR descriptions themselves"

I must admit I haven't always adhered to this myself because claude code is eager to do it (w/out asking).

I would also say that claude code's PR descriptions are less than ideal -- too much low level detail, too little upleveling in my view.

All that is to say, I think this is a good policy!

Dscano added 2 commits March 2, 2026 17:47
Signed-off-by: Davide Scano <d.scano89@gmail.com>
@Dscano
Copy link
Author

Dscano commented Mar 2, 2026

@fruffy @qobilidop we can use this PR p4lang/gsoc#98 as a good example to list within the Examples section what do you think?

@qobilidop
Copy link
Member

qobilidop commented Mar 2, 2026

@Dscano I don't fully understand what the examples are expected to demonstrate in order to tell whether this is a good example to use. Could you explain the purposes of these examples a bit more? Thanks!

@Dscano
Copy link
Author

Dscano commented Mar 2, 2026

@Dscano I don't fully understand what the examples are expected to demonstrate in order to tell whether this is a good example to use. Could you explain that a bit more? Thanks!

As you can see in LLVM’s AI Tool Policy (https://llvm.org/docs/AIToolPolicy.html
), they include a set of examples.I’d like to do the same in the P4 AI policy—i.e., provide contributors with a clear idea of what a “good PR” looks like.

@qobilidop
Copy link
Member

qobilidop commented Mar 2, 2026

@Dscano Got it! Thanks! Sounds good to me then. I would probably ask whether that example PR is too simple? But I guess the examples can be easily updated when there are better ones.

Signed-off-by: Davide Scano <d.scano89@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants