* Simo Sorce: > Well given that copyright protects actual works and not their style or > the ideas behind them I am really hard pressed to consider the risk > high enough to be that concerned.
People say that ideas aren't covered, but at the same time, literary characters and plots are clearly protected under copyright law. > But most Copyright laws protect only works made by humans. Mechanical > transformations almost universally so not indeed give rise to new > copyright or shift copyright to other people. Are you saying that because something isn't copyrightable as a new work, it can't be infringing? I don't think this kind of reasoning is valid. > But at the same time a LLM does not just spit copies oc other people > code. IT *can* do that if prompted to do so, but generally I think > there is quite some creative process in instructing the AI on what to > do, and unless you are literally just asking the AI to write the same > piece of code other wrote, the chance of literal copies diminish > quickly, and IMHO they are no different than the chance of you > reproducing the same code others did because it is the natural thing to > do in the specific language for the specific task. That depends on what you use it for. For a niche application, if there's a competing implementation that the model has been trained on, isn't leakage pretty likely? Because there aren't many other sources available? Also keep in mind that for many application domains (compression, some security protocols), code produced by models would still not be allowed into Fedora even if the generated code is not infringing copyright. > Clearly nobody is going to accuse you of copying their code for having > created a for loop to parse the argv argument of a C program main > function and using the variable "i" as the counter ... That's just a regular IDE coding assistant that's been around for decades at this point. And the copyright of larger IDE code templates is up to the IDE to decide. > Ultimately the questions are: > 1. can you effectively police it? > 2. How like is this going to be an actual problem (ie what is the level > of risk) ? > > To 1) I answer NO. > To 2) I think the answer is "LOW" I don't necessarily disagree withat *that*. But I would strongly object to Fedora publishing a guideline that says or implies that certain type of generated code is not copyrightable. We can reach an agreement about risks without making specific claims about the legal situation. > I may be wrong, but I do not think making hypothetical contrived cases > is useful, you need to think about the practical cases and likely > consequences IMHO. I don't think what I wrote is particularly contrieved. It's a coding editing tool. Its results in terms of copyright depend on what you do with it. Thanks, Florian -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
