Idk if its accurate to rote project the policies of OpenBSD to OpenSSH, yes technically its a subproject but in practice stewardship and thus effective policy is pretty much all damien.
If they disagreed about something so fundamental as the attribution of copyright, it would be a serious schism, from my outside perspective it seems along the lines of something that would lead to a fork or separation between the projects.
I also just read more context on the thread and it seems like Damien Miller is in there saying much the same thing as Theo. He wrote:
... use of AI-written code now [will] expose us to legal risk.
This was in the context of a contribution to add (IIRC) ext4 filesystem support to OpenBSD. In this case, I was worried that the AI was just regurgitating code that was in its training corpus because how many ext4 implementations are there?
I think AI generated bugfixes and smaller features that don't duplicate fairly unique pieces of work in other projects are much less problematic from a copyright perspective at least.
Comments
Idk if its accurate to rote project the policies of OpenBSD to OpenSSH, yes technically its a subproject but in practice stewardship and thus effective policy is pretty much all damien.
If they disagreed about something so fundamental as the attribution of copyright, it would be a serious schism, from my outside perspective it seems along the lines of something that would lead to a fork or separation between the projects.
I also just read more context on the thread and it seems like Damien Miller is in there saying much the same thing as Theo. He wrote:
This was in the context of a contribution to add (IIRC) ext4 filesystem support to OpenBSD. In this case, I was worried that the AI was just regurgitating code that was in its training corpus because how many ext4 implementations are there?
I think AI generated bugfixes and smaller features that don't duplicate fairly unique pieces of work in other projects are much less problematic from a copyright perspective at least.