Conversation
crystalmoon@chaos.social

the tower fairy

Reply to

@ljs this feels like the Rust on Linux folks were right all along...?

0
0
0
cxberger@mastodon.boiler.social

c-x-b verified verified

Reply to

@ljs is this about https://www.phoronix.com/news/Linux-Kernel-AI-Docs-Rules ?

0
0
0
crystalmoon@chaos.social

the tower fairy

Reply to

@ljs the bit where folks resigned, because compatibility measures were blocked by non-owning maintainers that had merge access

0
0
0
corbet

Jonathan Corbet

Reply to
@ljs No decisions have been made - it *is* an RFC after all. Expect a lot of discussion, and I would be amazed if this doesn't end up as a prominent topic at the Maintainers Summit in December.
0
0
2
corbet

Jonathan Corbet

Reply to
@ljs It *was* sent to linux-kernel.

In any case, it's a docs patch, I'll get my say in things :) More to the point, I don't take policy-relevant docs patches without a pretty clear sense of a consensus behind them.
0
0
2
ptesarik@infosec.exchange

Petr Tesařík

Reply to

@ljs @cxberger
https://distantprovince.by/posts/its-rude-to-show-ai-output-to-people/

1
0
0
pavel

Pavel Machek

Reply to @ptesarik@infosec.exchange
@ptesarik @ljs @cxberger Hehe. Someone should tell that to kernel CoC people. Apparently taking AI hallucinations, signing them with your and sending that out to confuse people is okay... Signing-off patches based on those hallucinations is okay, too.
0
0
0
ptesarik@infosec.exchange

Petr Tesařík

Reply to

@ljs If it gets committed, is it time for a non-AI fork?
Lorenzux?
@corbet

1
0
0
vbabka@mastodon.social

Vlastimil Babka 🇨🇿🇪🇺🇺🇦

Reply to @ptesarik@infosec.exchange

@ptesarik @ljs @corbet Satanix

1
0
2
piggo@piggo.space

Piggo verified_horse

Reply to @vbabka@mastodon.social
@vbabka @ptesarik @ljs @corbet this will make slop more difficult to recognize, right?
1
0
0
vbabka@mastodon.social

Vlastimil Babka 🇨🇿🇪🇺🇺🇦

Reply to @piggo@piggo.space

@piggo @ptesarik @ljs @corbet patch 4 includes some rules how usage of "agents" should be marked. I believe we should only focus on that initially + legal/licensing aspects. In fact this series seems to be sent shortly after a different RFC thread by someone else focusing on just that.

1
0
0
piggo@piggo.space

Piggo verified_horse

Reply to @vbabka@mastodon.social
@vbabka @ptesarik @ljs @corbet can they adhere to it? Thinking of that post where some moron let an ai agent delete production database by accident
1
0
0
vbabka@mastodon.social

Vlastimil Babka 🇨🇿🇪🇺🇺🇦

Reply to @piggo@piggo.space

@piggo @ptesarik @ljs @corbet good point, such requirements should not be just in the part of documentation that's supposed to be processed and followed by the agents themselves, there should be clear rules for the people running them, that they should double check.

0
0
0
ptesarik@infosec.exchange

Petr Tesařík

Reply to

@ljs @vbabka @piggo @corbet
Oh, right, there seems to be some undue pressure! I'm almost getting Jia Tan flashbacks.

0
0
1
ptesarik@infosec.exchange

Petr Tesařík

Reply to

@ljs @vbabka @piggo @corbet Even if we take only the legal aspects into account, what if some jurisdictions decide that AI infringes on other people's copyright? Shall we remove AI-assisted commits again?

0
0
0
ptesarik@infosec.exchange

Petr Tesařík

Reply to

@ljs @vbabka @piggo @corbet you forgot to add /s.
Just curious: Do I get British understatement right if I say: “I am not completely amused by the present situation?”

0
0
0
ptesarik@infosec.exchange

Petr Tesařík

Reply to

@ljs Thank you!
@vbabka @piggo @corbet

0
0
0
vbabka@mastodon.social

Vlastimil Babka 🇨🇿🇪🇺🇺🇦

Reply to

@ljs @pbarker @piggo @ptesarik @corbet two old men yelling at claudes

1
0
0
lkundrak@metalhead.club

AGRO TURBO.EXE SATAN 🇺🇦🇨🇿

Reply to @vbabka@mastodon.social

@vbabka @ljs @pbarker @piggo @ptesarik @corbet very eloquent branch-shaking djentlemen!!!

0
0
1
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: