Skip to content

Usage of AI and LLMS clarification #7228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

oussama-madimagh
Copy link
Contributor

Title

Usage of AI and LLMS clarification

Pull Request Type

  • Documentation

Related issue

Just a documentation clarification about using AI and LLMS

Description

I included a note cautioning contributors against using AI and LLM tools, particularly when editing documentation. The intention is to promote contributions that are human-written, lucid, and consistent with the voice and tone of the project.

Desktop

  • **OS:**windows 10

  • **OS Version:**22H2

  • **FreeTube version:**v0.23.3 Beta

@github-actions github-actions bot added the PR: waiting for review For PRs that are complete, tested, and ready for review label Apr 18, 2025
@FreeTubeBot FreeTubeBot enabled auto-merge (squash) April 18, 2025 20:09
@@ -20,6 +20,7 @@ Please follow these guidelines before sending your pull request and making contr
* Please test your code. Make sure new features work as well as existing core features such as watching videos or loading subscriptions. New features need to work with both the Local API as well as the Invidious API
* Please make sure your code does not violate any standards set by our linter. It's up to you to make fixes whenever necessary. You can run `npm run lint` to check locally and `npm run lint-fix` to automatically fix smaller issues.
* Please limit the amount of Node Modules that you introduce into the project. Only include them when **absolutely necessary** for your code to work (Ex: Using nedb for databases) or if a module provides similar functionality to what you are trying to achieve (Ex: Using autolinker to create links to outside URLs instead of writing the functionality myself).
* Avoid the use of LLMs and AI tools, especially when making documentation changes.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

especially when making documentation changes.

I disagree with this. It shouldnt be used at all.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

especially when making documentation changes.

I disagree with this. It shouldn't be used at all.

thank you for your feedback, i only added it because people doesn't pay much care to documentation usually and that results to a low quality content as @absidue stated in one of my requests where i used some AI to refine my content , but if it s for the betterment of the project i ll remove that part if others agree with that

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My comment on low quality was not just about documentation. I agree with @efb4f5ff-1298-471a-8973-3d47447115dc we don't want AI/LLM stuff at all, this is what we are adding to the pull request template Do not create PR's with AI! (PRs created mainly with AI will be closed. They waste our team's time. We ban repeat offenders.).
There is a big difference between a person writing some code which needs some adjustments and we are fine giving feedback to them to help them improve versus someone submitting some AI generated rubbish and then expecting us maintainers to do all the work to turn it into something decent.

Also for the record I highly doubt the AI actually refined your pull request, it mostly likely just made it worse. It's actually quite sad that you are happy submitting something as your own work, that was made worse by AI. If another human took your work and made it worse, you would probably act completely differently and not be happy submitting it as your own work...

@efb4f5ff-1298-471a-8973-3d47447115dc efb4f5ff-1298-471a-8973-3d47447115dc added PR: changes requested and removed PR: waiting for review For PRs that are complete, tested, and ready for review labels Apr 20, 2025
Copy link
Contributor

github-actions bot commented May 5, 2025

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.

Copy link
Contributor

This PR was closed because it has been stalled for 14 days with no activity.

@github-actions github-actions bot closed this May 19, 2025
auto-merge was automatically disabled May 19, 2025 02:11

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants