mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Quentin Rameau <quinq@fifth.space>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Proposed "AI" policies
Date: Mon, 21 Oct 2024 19:15:57 +0200	[thread overview]
Message-ID: <20241021191557.494ed725.quinq@fifth.space> (raw)
In-Reply-To: <20241019234045.GQ10433@brightrain.aerifal.cx>

Hi,

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

>    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

Maybe that part above could be reworded a bit, although I believe what
you say is true, the problem is just that those are completely opaque
regarding training sources, and so cannot be proven of good faith
at all, enven if in practice it was actually trained
from truly righteous material.

> 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.

Maybe the bug reporting part should be emphasized on its own,
disregarding the source of it, I think that's valable for computers
and humans altogether.
Then the AI part could be an addition to it, instead of the inverse.

      reply	other threads:[~2024-10-21 17:16 UTC|newest]

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

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=20241021191557.494ed725.quinq@fifth.space \
    --to=quinq@fifth.space \
    --cc=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).