"Of particular interest to me was a draft policy on the use of LLM-based programming tools in the FreeBSD project. To summarize quite heavily, the policy will forbid the incorporation of LLM-generated code into the project, while allowing their use in the development process in other ways, e.g., to help review patches, or to help write commit messages or other content that is not explicitly licensed. The policy comes out of a desire not to “taint” the FreeBSD project with code of dubious provenance; it is well-known that many LLM models are trained on code with licenses incompatible with the BSD license that we strive to use everywhere in the project, and thus far there is not much legal precedent to suggest that we would certainly be safe from copyright violation claims should the project decide to incorporate their output."
I wonder how they're going to enforce it. I mean, everyone else is failing to deal with it, including the slop deluge.
"Of particular interest to me was a draft policy on the use of LLM-based programming tools in the FreeBSD project. To summarize quite heavily, the policy will forbid the incorporation of LLM-generated code into the project, while allowing their use in the development process in other ways, e.g., to help review patches, or to help write commit messages or other content that is not explicitly licensed. The policy comes out of a desire not to “taint” the FreeBSD project with code of dubious provenance; it is well-known that many LLM models are trained on code with licenses incompatible with the BSD license that we strive to use everywhere in the project, and thus far there is not much legal precedent to suggest that we would certainly be safe from copyright violation claims should the project decide to incorporate their output."
I wonder how they're going to enforce it. I mean, everyone else is failing to deal with it, including the slop deluge.