cross-posted from: https://hexbear.net/post/9231158

in part:

Collaboration at danger

It is not purely the digital and civic infrastructures that are impacted by the use of LLMs. The free/libre software ecosystem, of which we consider Codeberg an important part of, is a social phenomenon centered on collaboration. Working in this way is only possible thanks to free sharing and mutual learning. This includes even very small tools that are shared and re-used and around which collaboration can start out. In contrast, by adopting LLMs people tend to code single-use software from scratch. While this leads to an increase in 'shared' code, it is mostly code that not only has not been 'written' by anyone but is also not maintained by anyone.

Losing trust in each other

The widespread use of LLMs in FLOSS is instead becoming a multidimensional attack on the trust between contributors and the very idea of convivial collaboration itself. Maintainers are under an increased work-load due to people submitting (often well-meaning) low-effort, LLM-generated contributions that require substantial amounts of time to review. At the same time it is becoming increasingly less clear which projects are maintained by experienced developers and which ones are LLM-generated without any meaningful human oversight and input. In the case of copyleft projects, LLMs additionally also lead to 'license laundering', where copyleft code is stripped of its reciprocity requirements by 'generating' it out of the training data.

We observe an increasing trend of mistrusting each other, up to the point where people who put in actual effort to analyze issues or share their suggestions are being accused of having used LLMs when they did not. At the same time, others instruct their LLMs to hide their traces and actively avoid common patterns, prompting others in reviewing contributions and communication more carefully for signs of machine generation.

Entering a vicious cycle

Together, these forces make collaboration not only harder but also less rewarding: With the transaction cost of collaboration increasing, people are becoming less likely to contribute to creating high-quality software projects and more likely to 'vibecode' a one-off software that is specific to your need, and won't evolve beyond. We get a vicious cycle where collaboration is becoming less and less rewarding, while the amount of single-use software that's unmaintained and never sees any improvements is going up.

Although often well intentioned, sharing the result of an prompt and calling it "libre software" does not make the world a better place. Codeberg is not and does not want to be a place to dump such generated single-use software that no one else will ever look at. We are a place for people to collaborate and improve software together. Within this context, the recent votes can be understood as a reconfirmation of those principles: As we want to center on human collaboration, we will not actively support or engage in the creation of LLMs and will not put our limited resources to use for storing single-use software that would pollute our FLOSS commons.> ## Collaboration at danger

It is not purely the digital and civic infrastructures that are impacted by the use of LLMs. The free/libre software ecosystem, of which we consider Codeberg an important part of, is a social phenomenon centered on collaboration. Working in this way is only possible thanks to free sharing and mutual learning. This includes even very small tools that are shared and re-used and around which collaboration can start out. In contrast, by adopting LLMs people tend to code single-use software from scratch. While this leads to an increase in 'shared' code, it is mostly code that not only has not been 'written' by anyone but is also not maintained by anyone.

Losing trust in each other

The widespread use of LLMs in FLOSS is instead becoming a multidimensional attack on the trust between contributors and the very idea of convivial collaboration itself. Maintainers are under an increased work-load due to people submitting (often well-meaning) low-effort, LLM-generated contributions that require substantial amounts of time to review. At the same time it is becoming increasingly less clear which projects are maintained by experienced developers and which ones are LLM-generated without any meaningful human oversight and input. In the case of copyleft projects, LLMs additionally also lead to 'license laundering', where copyleft code is stripped of its reciprocity requirements by 'generating' it out of the training data.

We observe an increasing trend of mistrusting each other, up to the point where people who put in actual effort to analyze issues or share their suggestions are being accused of having used LLMs when they did not. At the same time, others instruct their LLMs to hide their traces and actively avoid common patterns, prompting others in reviewing contributions and communication more carefully for signs of machine generation.

Entering a vicious cycle

Together, these forces make collaboration not only harder but also less rewarding: With the transaction cost of collaboration increasing, people are becoming less likely to contribute to creating high-quality software projects and more likely to 'vibecode' a one-off software that is specific to your need, and won't evolve beyond. We get a vicious cycle where collaboration is becoming less and less rewarding, while the amount of single-use software that's unmaintained and never sees any improvements is going up.

Although often well intentioned, sharing the result of an prompt and calling it "libre software" does not make the world a better place. Codeberg is not and does not want to be a place to dump such generated single-use software that no one else will ever look at. We are a place for people to collaborate and improve software together. Within this context, the recent votes can be understood as a reconfirmation of those principles: As we want to center on human collaboration, we will not actively support or engage in the creation of LLMs and will not put our limited resources to use for storing single-use software that would pollute our FLOSS commons.

other discussions
 

cross-posted from: https://hexbear.net/post/9231159

cross-posted from: https://hexbear.net/post/9231158

in part:

Collaboration at danger

It is not purely the digital and civic infrastructures that are impacted by the use of LLMs. The free/libre software ecosystem, of which we consider Codeberg an important part of, is a social phenomenon centered on collaboration. Working in this way is only possible thanks to free sharing and mutual learning. This includes even very small tools that are shared and re-used and around which collaboration can start out. In contrast, by adopting LLMs people tend to code single-use software from scratch. While this leads to an increase in 'shared' code, it is mostly code that not only has not been 'written' by anyone but is also not maintained by anyone.

Losing trust in each other

The widespread use of LLMs in FLOSS is instead becoming a multidimensional attack on the trust between contributors and the very idea of convivial collaboration itself. Maintainers are under an increased work-load due to people submitting (often well-meaning) low-effort, LLM-generated contributions that require substantial amounts of time to review. At the same time it is becoming increasingly less clear which projects are maintained by experienced developers and which ones are LLM-generated without any meaningful human oversight and input. In the case of copyleft projects, LLMs additionally also lead to 'license laundering', where copyleft code is stripped of its reciprocity requirements by 'generating' it out of the training data.

We observe an increasing trend of mistrusting each other, up to the point where people who put in actual effort to analyze issues or share their suggestions are being accused of having used LLMs when they did not. At the same time, others instruct their LLMs to hide their traces and actively avoid common patterns, prompting others in reviewing contributions and communication more carefully for signs of machine generation.

Entering a vicious cycle

Together, these forces make collaboration not only harder but also less rewarding: With the transaction cost of collaboration increasing, people are becoming less likely to contribute to creating high-quality software projects and more likely to 'vibecode' a one-off software that is specific to your need, and won't evolve beyond. We get a vicious cycle where collaboration is becoming less and less rewarding, while the amount of single-use software that's unmaintained and never sees any improvements is going up.

Although often well intentioned, sharing the result of an prompt and calling it "libre software" does not make the world a better place. Codeberg is not and does not want to be a place to dump such generated single-use software that no one else will ever look at. We are a place for people to collaborate and improve software together. Within this context, the recent votes can be understood as a reconfirmation of those principles: As we want to center on human collaboration, we will not actively support or engage in the creation of LLMs and will not put our limited resources to use for storing single-use software that would pollute our FLOSS commons.> ## Collaboration at danger

It is not purely the digital and civic infrastructures that are impacted by the use of LLMs. The free/libre software ecosystem, of which we consider Codeberg an important part of, is a social phenomenon centered on collaboration. Working in this way is only possible thanks to free sharing and mutual learning. This includes even very small tools that are shared and re-used and around which collaboration can start out. In contrast, by adopting LLMs people tend to code single-use software from scratch. While this leads to an increase in 'shared' code, it is mostly code that not only has not been 'written' by anyone but is also not maintained by anyone.

Losing trust in each other

The widespread use of LLMs in FLOSS is instead becoming a multidimensional attack on the trust between contributors and the very idea of convivial collaboration itself. Maintainers are under an increased work-load due to people submitting (often well-meaning) low-effort, LLM-generated contributions that require substantial amounts of time to review. At the same time it is becoming increasingly less clear which projects are maintained by experienced developers and which ones are LLM-generated without any meaningful human oversight and input. In the case of copyleft projects, LLMs additionally also lead to 'license laundering', where copyleft code is stripped of its reciprocity requirements by 'generating' it out of the training data.

We observe an increasing trend of mistrusting each other, up to the point where people who put in actual effort to analyze issues or share their suggestions are being accused of having used LLMs when they did not. At the same time, others instruct their LLMs to hide their traces and actively avoid common patterns, prompting others in reviewing contributions and communication more carefully for signs of machine generation.

Entering a vicious cycle

Together, these forces make collaboration not only harder but also less rewarding: With the transaction cost of collaboration increasing, people are becoming less likely to contribute to creating high-quality software projects and more likely to 'vibecode' a one-off software that is specific to your need, and won't evolve beyond. We get a vicious cycle where collaboration is becoming less and less rewarding, while the amount of single-use software that's unmaintained and never sees any improvements is going up.

Although often well intentioned, sharing the result of an prompt and calling it "libre software" does not make the world a better place. Codeberg is not and does not want to be a place to dump such generated single-use software that no one else will ever look at. We are a place for people to collaborate and improve software together. Within this context, the recent votes can be understood as a reconfirmation of those principles: As we want to center on human collaboration, we will not actively support or engage in the creation of LLMs and will not put our limited resources to use for storing single-use software that would pollute our FLOSS commons.

 

in part:

Collaboration at danger

It is not purely the digital and civic infrastructures that are impacted by the use of LLMs. The free/libre software ecosystem, of which we consider Codeberg an important part of, is a social phenomenon centered on collaboration. Working in this way is only possible thanks to free sharing and mutual learning. This includes even very small tools that are shared and re-used and around which collaboration can start out. In contrast, by adopting LLMs people tend to code single-use software from scratch. While this leads to an increase in 'shared' code, it is mostly code that not only has not been 'written' by anyone but is also not maintained by anyone.

Losing trust in each other

The widespread use of LLMs in FLOSS is instead becoming a multidimensional attack on the trust between contributors and the very idea of convivial collaboration itself. Maintainers are under an increased work-load due to people submitting (often well-meaning) low-effort, LLM-generated contributions that require substantial amounts of time to review. At the same time it is becoming increasingly less clear which projects are maintained by experienced developers and which ones are LLM-generated without any meaningful human oversight and input. In the case of copyleft projects, LLMs additionally also lead to 'license laundering', where copyleft code is stripped of its reciprocity requirements by 'generating' it out of the training data.

We observe an increasing trend of mistrusting each other, up to the point where people who put in actual effort to analyze issues or share their suggestions are being accused of having used LLMs when they did not. At the same time, others instruct their LLMs to hide their traces and actively avoid common patterns, prompting others in reviewing contributions and communication more carefully for signs of machine generation.

Entering a vicious cycle

Together, these forces make collaboration not only harder but also less rewarding: With the transaction cost of collaboration increasing, people are becoming less likely to contribute to creating high-quality software projects and more likely to 'vibecode' a one-off software that is specific to your need, and won't evolve beyond. We get a vicious cycle where collaboration is becoming less and less rewarding, while the amount of single-use software that's unmaintained and never sees any improvements is going up.

Although often well intentioned, sharing the result of an prompt and calling it "libre software" does not make the world a better place. Codeberg is not and does not want to be a place to dump such generated single-use software that no one else will ever look at. We are a place for people to collaborate and improve software together. Within this context, the recent votes can be understood as a reconfirmation of those principles: As we want to center on human collaboration, we will not actively support or engage in the creation of LLMs and will not put our limited resources to use for storing single-use software that would pollute our FLOSS commons.

 

In Brief:

  • Two motions regarding "artificial intelligence" and Large Language Models (LLMs) were voted on among Codeberg e. V. members and passed.
  • We are promising to not use any of your data to train LLM and explain what the planned Terms of Use change mean for 'vibe-coded' projects.
  • We believe that LLMs endanger the free/libre software ecosystem as a whole.

The blog/news post then goes extensively into where Codeberg understands itself to be in the development landscape, and their voting results. They present their interpretation of the current software development and hardware landscape under the influence of LLMs, and the consequences they take. And how it changes not only development in general, but FOSS collaboration and projects specifically.

To us, it seems ridiculous to see projects with a single developer and virtually no users consuming as much or even more resources than some of the largest community projects on Codeberg, which operate frugal with CI/CD and storage resources. We do not believe it is reasonable for Codeberg to invest our precious donation money into hosting of large ghost projects.

 

In Brief:

  • Two motions regarding "artificial intelligence" and Large Language Models (LLMs) were voted on among Codeberg e. V. members and passed.
  • We are promising to not use any of your data to train LLM and explain what the planned Terms of Use change mean for 'vibe-coded' projects.
  • We believe that LLMs endanger the free/libre software ecosystem as a whole.

Codeberg is a Germany based platform for hosting source code, operated by a non profit. With its latest changes to its TOS vibe coded apps are banned from the platform

submitted 1 month ago* (last edited 1 month ago) by to c/technology@lemmy.world