Reminder: #LibreOffice includes no AI features in the software.
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice
Being able to explain how "shit" work, doesn't magically erase the fact that it's "shit". And doing that by perfectly understanding, in the mean time why it's "shit" is somehow quite impressive. -
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice slop is slop
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice LibreClankers?
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice slop is slop, brother. but you know this, despite the theatrics. i hope you're being paid plenty for aiding in raiding the commons and dissolving trust in our communities
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice you accept slop.
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice Ah, another high-quality LibreOffice post. Again
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice So why don't you enforce your "strict policy" on submissions? I went through some random LibreOffice core commits and found three that used LLMs. None of them actually followed this policy.
-
@libreoffice slop is slop, brother. but you know this, despite the theatrics. i hope you're being paid plenty for aiding in raiding the commons and dissolving trust in our communities
@ciatmusings @libreoffice i am pretty sure this guy is just like this, and also i think it's the same one who floated LibreOffice doing blockchain a few years ago
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice "the program is not infested with death machine features, but we do use the death machine responsibly to do it" you're so fucking gross oh my god stand up for something
-
@libreoffice So why don't you enforce your "strict policy" on submissions? I went through some random LibreOffice core commits and found three that used LLMs. None of them actually followed this policy.
@barubary @libreoffice I'd be interested in specific examples, can you share those and the exact violations? Please don't get me wrong here, I'm not pro-LLM or want to defend LO here, I just want to see that myself.
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice nobody was reassured by this response
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice That's the thing: It's all slop.
"Claude, give me a brief paragraph that explains the code you wrote for me so that I can pass LibreOffice's weak 'prohibition' against 'slop'."
-
@barubary @libreoffice I'd be interested in specific examples, can you share those and the exact violations? Please don't get me wrong here, I'm not pro-LLM or want to defend LO here, I just want to see that myself.
@serak @libreoffice "You must be able to ..." is generally unverifiable. The hard requirements in this policy as I see them are:
- The commit message must mention the name of the LLM product.
- The commit message must mention the version of the LLM product.
- The commit message must document "the steps taken", which I'm not sure how much detail they want, but I'd expect at least a high-level description like "I wrote prompt/specification X and told product Y to generate code" or "I originally wrote this code by hand, but I had product X review it and it pointed out the following issues, so I changed it" or something like that.
- The commit message must list the line numbers where an LLM was "involved", which I'd say includes all LLM-generated code and probably also anything written/changed after LLM review.
From what I can see, none of the LLM commits do (3) or (4). (Disclaimer: I'm not sure how useful a list of line numbers would actually be in practice, but the policy says you must have them.)
Examples:
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice expecto puritans
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
-
@serak @libreoffice "You must be able to ..." is generally unverifiable. The hard requirements in this policy as I see them are:
- The commit message must mention the name of the LLM product.
- The commit message must mention the version of the LLM product.
- The commit message must document "the steps taken", which I'm not sure how much detail they want, but I'd expect at least a high-level description like "I wrote prompt/specification X and told product Y to generate code" or "I originally wrote this code by hand, but I had product X review it and it pointed out the following issues, so I changed it" or something like that.
- The commit message must list the line numbers where an LLM was "involved", which I'd say includes all LLM-generated code and probably also anything written/changed after LLM review.
From what I can see, none of the LLM commits do (3) or (4). (Disclaimer: I'm not sure how useful a list of line numbers would actually be in practice, but the policy says you must have them.)
Examples:
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
It strikes me as odd to ban all use of LLM for the _commit message_, but still allow its use for the actual _code_.
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
@libreoffice It wouldn't matter if the LLM code was perfect. You used the methane-powered exploitation machine.
-
Reminder: #LibreOffice includes no AI features in the software. It doesn't rewrite your content, train algorithms, or share your data. There is zero AI functionality in the app.
Regarding the use of LLMs in the development process, we have a strict policy about this: https://wiki.documentfoundation.org/Development/AI_policy – Contributors who use such tools must be able to explain EVERY changed line of code. We do not accept any "slop".
When the LLM brain rot sets in (if it hasn’t already), there will be no “easy hacks” because nobody will know how to write their own code anymore.
-
@svavar I did not intend this to come over this way. I myself am very critical of LLMs and LO's use/acceptance of them and do not support their decision or want to argue in favor of it, I just genuinely wanted to take a look at those commits and thought it wouldn't be much effort for @barubary to share them after already having found them before. He actually took more effort with those explanations than I would've expected and I want to thank him for that.
