Add guideline about crediting tools as authors

Offen
  • Stimmt etwas nicht?
#1,950 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
48/100
Issue-Typ
Dokumentation
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
python
Bereich
documentation

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

type-feature
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

Vorherrschende Sprache
Python
Sterne
2.1k
Forks
1.1k
Ø Merge
3 T. 14 Std.
Gemergte PRs (30 T.)
13

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus python/devguide

Alle Issues in python/devguide

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.