public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Alejandro Colomar <alx@kernel.org>,  linux-man@vger.kernel.org
Subject: Re: [PATCH] CONTRIBUTING.d/ai: Add guidelines banning AI for contributing
Date: Tue, 14 Oct 2025 15:16:04 -0700	[thread overview]
Message-ID: <87y0pd5duj.fsf@gmail.com> (raw)
In-Reply-To: <e6af212b-7efa-4f36-b39d-35f3856f657c@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

Carlos O'Donell <carlos@redhat.com> writes:

>> My main concern with accepting AI contributions is the current lack
>> of
>> legislation and case law in the United States with respect to the
>> copyright-ability of the output. I also don't trust AI answers much, but
>> that theoretically could change in the future as technology improves (or
>> less people blindly trust the output).
>
> ... and what about EU contributors?
>
> Upstream has to deal with the complex jurisdictional intersection of laws.
>
> I recommend simple and easy to follow policy.

Thanks for mentioning it. I didn't mean to imply that the EU and other
jurisdictions are not important. I just do not know much about their
situations.

Collin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2025-10-14 22:16 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 21:27 [PATCH] CONTRIBUTING.d/ai: Add guidelines banning AI for contributing Alejandro Colomar
2025-10-14 21:32 ` Carlos O'Donell
2025-10-14 21:52   ` Alejandro Colomar
2025-10-14 21:55     ` Carlos O'Donell
2025-10-14 21:39 ` Collin Funk
2025-10-14 21:59   ` Alejandro Colomar
2025-10-14 22:03     ` Carlos O'Donell
2025-10-14 22:10       ` Alejandro Colomar
2025-10-14 22:20         ` Alejandro Colomar
2025-10-14 23:59           ` Carlos O'Donell
2025-10-14 22:00   ` Carlos O'Donell
2025-10-14 22:16     ` Collin Funk [this message]
2025-10-14 23:58       ` Carlos O'Donell
2025-10-14 21:54 ` Carlos O'Donell
2025-10-14 22:15   ` Alejandro Colomar
2025-10-15  0:16     ` Carlos O'Donell
2025-10-15  2:13       ` Collin Funk
2025-10-15 10:49       ` Alejandro Colomar
2025-10-14 22:03 ` [PATCH v2] " Alejandro Colomar
2025-10-15 11:21 ` [PATCH v3] " Alejandro Colomar
2025-10-15 12:29   ` Alejandro Colomar
2025-10-15 13:25   ` Carlos O'Donell
2025-10-15 14:03     ` Alejandro Colomar
2025-10-15 14:46       ` Carlos O'Donell
2025-10-15 14:51         ` Sam James
2025-10-15 15:31           ` Alejandro Colomar
2025-10-15 16:09             ` Sam James
2025-10-15 16:20               ` Alejandro Colomar
2025-10-15 16:26                 ` Sam James
2025-10-15 15:50 ` [PATCH v4] " Alejandro Colomar
2025-10-15 16:03   ` Carlos O'Donell
2025-10-15 16:56     ` G. Branden Robinson
2025-10-15 18:11       ` Alejandro Colomar
2025-10-15 19:24         ` G. Branden Robinson
2025-10-15 19:50           ` Alejandro Colomar
2025-10-20 18:47           ` Carlos O'Donell
2025-10-20 19:05           ` Carlos O'Donell
2025-10-15 18:22     ` Alejandro Colomar
2025-10-15 18:49       ` Sam James
2025-10-15 19:03         ` Alejandro Colomar
2025-10-15 19:04           ` Alejandro Colomar
2025-10-15 19:11             ` Sam James
2025-10-15 19:17               ` Alejandro Colomar
2025-10-16 12:26       ` Alejandro Colomar
2025-10-16 16:41 ` [PATCH v5] " Alejandro Colomar
2025-10-20 18:25   ` Carlos O'Donell
2025-10-21 17:01     ` Alejandro Colomar
2025-10-27 17:29 ` [PATCH v6] " Alejandro Colomar
2025-10-28 12:31   ` Carlos O'Donell
2025-10-28 13:09     ` Alejandro Colomar
2025-10-28 13:21   ` [PATCH v7] " Alejandro Colomar
2025-11-10 11:54     ` Alejandro Colomar
2025-11-10 12:01 ` [PATCH v8] " Alejandro Colomar
2025-11-10 13:31   ` Carlos O'Donell
2025-11-10 14:31     ` Alejandro Colomar
2025-11-10 14:36 ` [PATCH v9] " Alejandro Colomar
2025-11-10 16:56   ` Carlos O'Donell
2025-11-10 22:25     ` Alejandro Colomar
2026-03-29 13:42 ` [PATCH] " Günther Noack
2026-03-29 17:55   ` Alejandro Colomar

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=87y0pd5duj.fsf@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=alx@kernel.org \
    --cc=carlos@redhat.com \
    --cc=linux-man@vger.kernel.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox