"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.
Jellyfin LLM/"AI" Development Policy
11–20 of 112 posts
Re: Jellyfin LLM/"AI" Development Policy
#12Re: 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.
But that is translation, not “please generate a pull request message for these changes.”
Re: Jellyfin LLM/"AI" Development Policy
#14This 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…
Re: Jellyfin LLM/"AI" Development Policy
#15love the "AI" in quotes
Re: Jellyfin LLM/"AI" Development Policy
#16Re: Jellyfin LLM/"AI" Development Policy
#17I 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.
Re: Jellyfin LLM/"AI" Development Policy
#18I 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
#19People 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…
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
#20Good 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".
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