From: Jonathan Corbet <corbet@lwn.net>
To: Hannes Reinecke <hare@suse.de>, Willy Tarreau <w@1wt.eu>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@kernel.org, tools@kernel.org, workflows@vger.kernel.org
Subject: Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
Date: Wed, 28 Feb 2024 10:43:50 -0700 [thread overview]
Message-ID: <87msrktrft.fsf@meer.lwn.net> (raw)
In-Reply-To: <4fa1cbc7-0f9d-47bf-8ff7-a9b17456431e@suse.de>
Hannes Reinecke <hare@suse.de> writes:
> Out of personal interest I really have to chime in here.
> You are aware, though, that following this line of thought
> and improving the underlying model (which really shouldn't
> be too hard given the vast body of training data which is LKML)
> we will actually putting LWN and its editors out of business.
>
> I would be _VERY_ interesting having a discussion here with the
> relevant parties (Hello Jon!) to see which direction we as a
> community will want to go. Maybe Plumbers and/or Kernel Summit in Vienna
> would be a good place to start.
Trust me, if you're in a business that is in any way associated with
publishing, you're aware of such things.
Whether the kernel community goes in for a tool like this will
ultimately have little effect on LWN's fate - others will certainly pick
this stuff up regardless. There are, after all, certain other sites out
there reporting on the kernel that have looked like bad LLM output for
years anyway...:)
I worry about some of this stuff in general. It seems there's a
definite risk of creating a checkpatchGPT that is allowed to push
developers around far more than would be warranted, for example. But
the tools are out there and getting cheaper; if they are useful I guess
we should use them.
It would be nicer to base them on an open-source (or something close to
it) model, of course.
Meanwhile, in the short term I suspect LWN can find a place for itself.
After that I hope to be retired.
Thanks,
jon
next prev parent reply other threads:[~2024-02-28 17:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 22:32 Konstantin Ryabitsev
2024-02-27 23:35 ` Junio C Hamano
2024-02-28 0:43 ` Linus Torvalds
2024-02-28 20:46 ` Shuah Khan
2024-02-29 0:33 ` James Bottomley
2024-02-28 5:00 ` Willy Tarreau
2024-02-28 14:03 ` Mark Brown
2024-02-28 14:39 ` Willy Tarreau
2024-02-28 15:22 ` Konstantin Ryabitsev
2024-02-28 15:29 ` Willy Tarreau
2024-02-28 17:52 ` Konstantin Ryabitsev
2024-02-28 17:58 ` Willy Tarreau
2024-02-28 19:16 ` Konstantin Ryabitsev
2024-02-28 15:04 ` Hannes Reinecke
2024-02-28 15:15 ` Willy Tarreau
2024-02-28 17:43 ` Jonathan Corbet [this message]
2024-02-28 18:52 ` Alex Elder
2024-02-28 18:55 ` Bart Van Assche
2024-02-29 7:18 ` Hannes Reinecke
2024-02-29 8:37 ` Theodore Ts'o
2024-03-01 1:13 ` Bart Van Assche
2024-02-29 9:30 ` James Bottomley
2024-02-28 19:32 ` Luis Chamberlain
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=87msrktrft.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=hare@suse.de \
--cc=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
--cc=users@kernel.org \
--cc=w@1wt.eu \
--cc=workflows@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