Live data from Hacker News

Jellyfin LLM/"AI" Development Policy

jellyfin.org

11–20 of 112 posts

Re: Jellyfin LLM/"AI" Development Policy

#11
People can write horrible PRs manually just as well as they do with AI (see Hacktoberfest drama, etc).

"LLM Code Contributions to Official Projects" would read exactly the same if it just said "Code Contributions to Official Projects": Write concise PRs, test your code, explain your changes and handle review feedback. None of this is different whether the code is written manually or with an LLM. Just looks like a long virtue signaling post.

Re: Jellyfin LLM/"AI" Development Policy

#13

> LLM output is expressly prohibited for any direct communication I would like to see this more. As a heavy user of LLMs I still write 100% of my own communication. Do not send me something an LLM wrote, if I wanted to read LLM outputs, I would ask an LLM.

I’m glad they have a carve out for using LLMs to translate to, or fix up English communications. LLMs are a great accessibility tool that is making open source development truly global. Translation and grammar fix up is something LLMs are very, very good at!

But that is translation, not “please generate a pull request message for these changes.”

Re: Jellyfin LLM/"AI" Development Policy

#14

This seems fair, tbh. And I fully agree on the policy for issues/discussions/PRs. I know there will probably be a whole host of people from non-English-speaking countries who will complain that they are only using AI to translate because English is not their first (or maybe even second) language. To those I will just say: I would much rather read your non-native English, knowing you put thought and care into what you…

There is a carve out exception for this in the doc.

Re: Jellyfin LLM/"AI" Development Policy

#17

I suspect the vast number of individuals in developing countries currently spamming LLM commits to every open source project on earth, and often speak neither the project or programming language are not going to pay much attention to this policy. It’s become a numbers game of automation blasting “contributions” at projects with name recognition and hoping you sneak one in for your resume/portfolio.

Policy is not put in place to prevent anything. Policy is put in place so that you have a sign to point at while you lock a PR thread.

Re: Jellyfin LLM/"AI" Development Policy

#18
I'm not sure when this policy was introduced, but fairly recently Jellyfin released a pretty major update that introduced a lot of bugs and performance issues. I've been watching their issue tracker as they work through them and have noticed it's flooded with LLM generated PRs and obviously LLM generated PR comments/descriptions/replies. A lot of the LLM generated PRs are a mishmash of 2-8 different issues all jumbled into a single PR.

I can see how frustrating it is to wade through those and they are distracting and taking time away from them actually getting things fixed up.

Re: Jellyfin LLM/"AI" Development Policy

#19

People can write horrible PRs manually just as well as they do with AI (see Hacktoberfest drama, etc). "LLM Code Contributions to Official Projects" would read exactly the same if it just said "Code Contributions to Official Projects": Write concise PRs, test your code, explain your changes and handle review feedback. None of this is different whether the code is written manually or with an LLM. Just looks like a lon…

Virtue signaling? That seems like an uncharitable reading.

The point, and the problem, is volume. Doing it manually has always imposed a de facto volume limit which LLMs have effectively removed. Which I understand to be the problem these types of posts and policies are designed to address.

Re: Jellyfin LLM/"AI" Development Policy

#20
post #16

Good AI policies (like this one) can be spotted since the TLDR is "Don't submit shitty code". As such, good AI policies should be replaced by "Contribution policies" that says "Don't submit shitty code".

I think the gist and the "virality" of this policy is:

1) we accept good quality LLM code

2) we DO NOT accept LLM generated human interaction, including PR explanation

3) your PR must explain well enough the change in the description

Which summed together are far more than "no shitty code". It's rather no shitty code that YOU understand

Post reply on HN