Add guideline about crediting tools as authors
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 48/100
- Issue 類型
- 文件
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- python
研究方向
Start by locating the Devguide’s contributor guidelines and reviewing their existing rules for commit messages and attribution. Decide how those guidelines should address AI tools listed as co-authors, including the concerns raised in this issue, then update the relevant documentation. Done means the guidance clearly states the project’s position on crediting tools as authors.
由索引模型根據 Issue 內容生成。
描述
Describe the enhancement or feature you would like
We now have many commits created with so-called AI tools. Many of them default to adding their name in a co-authored-by line in the commit message, which can end up in the upstream repo commit message if the person merging does not clean up the text box (this is a GitHub issue of defaulting to concatenating all commit messages, but can be changed per-repo to take the PR description).
There is an issue with considering this bots as authors. If a program is an author, is its output copyrightable? Does it infringe on the licenses of projects ingested in the training data? Do the bots need to sign a contributor agreement?
I don’t know why these tools do that; maybe it’s just for marketing (as the authors are visible in all pages with lists of commits), and maybe people keep it in good faith in order to disclose tool usage.
I think these lines should not be present, as they have risky implications or are just dubious free publicity.
Thanks for considering!
Describe alternatives you have considered
No response
Additional context
No response
- 主要語言
- Python
- 星號
- 2.1k
- 分支
- 1.1k
- 平均合併
- 3 天 14 小時
- 30 天內合併 PR
- 13
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
python/devguide 的其他 Issue
-
Feature: Document SELinux bind-mount note for local devcontainer usage可能已有人在做 @pranavchoudhary-tech 於 80 天前認領。 未關閉type-feature
難度 2/5 1-3 小時 新手友好度 68/100
python/devguide#1879 · 5 則留言 ·
維護者通常 1 天內回覆
-
type-feature
難度 2/5 1-3 小時 新手友好度 68/100
python/devguide#1791 · 4 則留言 · 2 個 reaction ·
維護者通常 1 天內回覆
-
Feature: Add instructions about JIT builds可能重新可做 @oloweh 於 27 天前認領，目前沒有進行中的 PR。 未關閉topic-building python type-feature
難度 2/5 1-3 小時 新手友好度 65/100
python/devguide#1620 · 2 則留言 ·
維護者通常 1 天內回覆
-
needs: decision topic-test type-bug
難度 2/5 1-3 小時 新手友好度 78/100
python/devguide#1171 · 10 則留言 ·
維護者通常 1 天內回覆
-
topic-dev process type-feature
難度 2/5 1-3 小時 新手友好度 62/100
python/devguide#319 · 4 則留言 · 3 個 reaction ·
維護者通常 1 天內回覆
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 62/100
earthtojake/text-to-cad#758 ·
維護者通常 1 天內回覆
-
domain:upgrades enhancement needs-triage
難度 2/5 1-3 小時 新手友好度 66/100
gke-labs/kube-agents#4634 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
agardnerIT/opamp-server-py#116 ·
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 78/100
elviskahoro/sdk-python-attio#144 · 1 則留言 ·
維護者通常 1 天內回覆