mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: [musl] Proposed "AI" policies
Date: Sat, 19 Oct 2024 19:40:45 -0400	[thread overview]
Message-ID: <20241019234045.GQ10433@brightrain.aerifal.cx> (raw)

Some mentions here and there of ChatGPT/"AI" in musl- and
musl-adjacent contexts has had me thinking we really should have some
explicit policy on this stuff, which could be posted on the wiki as
well as in final form here, and wherever else it may be appropriate,
before it becomes an issue.

In a sense I don't even see these as "AI policies", just provenance,
authorship-credit, honesty, license-honoring, etc. policies, but
unfortunately it's "AI" that's made it necessary to spell them out
explicitly. So, here's roughly what I have in mind:

1. Please DO NOT submit "AI generated" code/patches for inclusion in
   musl. These do not have clear authorship, are derived from models
   that are clearly derived from a plethora of copyrighted works
   without license or attribution, and thereby cannot be licensed by
   the submitter. Being that most patch contributions to musl are
   small and simple enough that it's dubious whether copyright applies
   at all, this may not be an issue in all cases, but it's still
   dishonest and wastes our time reviewing code that the submitter did
   not write and does not have any reasonable basis to assume is
   correct. Often the changes proposed by these models are blatently
   incorrect and introduce bugs/vulns into previously-correct code.

2. Please DO NOT submit "AI generated" or otherwise automated bug
   reports without disclosing the provenance (or lack thereof). This
   wastes everybody's time. If you are using tooling to identify
   potential bugs, please either confirm before reporting that you
   have actually found a bug (not just that the tool said it's a bug),
   or clearly state in the report that it's unconfirmed, which tools
   you used, and why you think the alleged bug may be legitimate -- or
   if you don't know you're just asking whether it might be.

3. Even being a permissive license, the MIT license requires
   attribution and preservation of copyright notice. It thereby does
   not permit incorporation of musl sources (or other MIT licensed
   code) into models or derived outputs of models where the necessary
   attribution and preservation of copyright notice are not possible.

Anything I'm missing or that seems like it should be changed?

Rich

             reply	other threads:[~2024-10-19 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 23:40 Rich Felker [this message]
2024-10-21 17:15 ` Quentin Rameau

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=20241019234045.GQ10433@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).