Upgrade contribution policy and AI usage#4989
Conversation
|
|
||
| ## Linked Issue (Required in most cases) | ||
|
|
||
| <!-- Link the issue here. The issue must be approved by a maintainer ("yes" or ready-to-work label), unless your PR is an allowed exception. --> |
There was a problem hiding this comment.
| <!-- Link the issue here. The issue must be approved by a maintainer ("yes" or ready-to-work label), unless your PR is an allowed exception. --> | |
| <!-- Link the issue here. If your issue is not approved by a maintainer, don't expect your PR to be merged. --> |
It is ok to submit a PR ahead of approval.
They just have to keep in mind that they may end up in wasting their time, LLM token cost, etc.
|
|
||
| **Not allowed:** | ||
|
|
||
| - Listing an AI tool as a co-author. |
There was a problem hiding this comment.
We can allow this. Being an author in GitHub is different from being an author in academic papers.
There was a problem hiding this comment.
They will not get any copyright, though. Even after being listed as author, at least not with current laws.
Copyright The Lima Authors.
|
|
||
| - Listing an AI tool as a co-author. | ||
| - Co-signing commits with an AI tool. | ||
| - Using `assisted-by`, `co-developed`, or similar commit trailers for AI tools. |
There was a problem hiding this comment.
This contradicts with PULL_REQUEST_TEMPLATE, which recommends assited-by trailer
There was a problem hiding this comment.
And it is probably better to have the ads in the machine-readable trailer, than in the text...
🤖 Generated with [Claude Code](https://claude.com/claude-code)
So using Assisted-by at least puts it all in the same place, and makes it easier to hide.
There was a problem hiding this comment.
I thought only to add the trailer in the PR desc but there are no downsides to adding it to commit messages as well
|
Let me remove this from the v2.1.2 milestone, as it may take more time for discussion. |
|
You might also consider an agents.md at the root of the project even if only to guide how you do / don't want it to behave (and as you suggest economize on token cost). For context, I've observed this being used to good effect: |
|
In the issue there were only two git rules being discussed, for It would be better to list those explicitly here, preferably also with links to DCO and to "Linux" policy? There were some other projects having other rules for Author and Co-Authored-By - but not Lima (yet). It is probably not a bad idea to have a copy of the DCO in the repository? https://developercertificate.org/ |
|
Thanks, but maybe in a separate PR or issue. |
Fixes lima-vm#4982 Signed-off-by: Ansuman Sahoo <anshumansahoo500@gmail.com>
unsuman
force-pushed
the
update-contribution-policy
branch
from
98c24a9 to
991780d
Compare
4 participants
Fixes #4982