| ▲ | overfeed 8 hours ago | |||||||
The line between AI-assisted clean-room reverse-engineeing and open-source-license-laundering is a thin one, and I think the one described in the article crosses over to laundering. In classic clean-room design, one team documents the interfaces - not the code. | ||||||||
| ▲ | dhon_ 5 hours ago | parent | next [-] | |||||||
In this case though, the new driver has the same license as the project it was based on and explicitly credits the original project | ||||||||
| ||||||||
| ▲ | Avamander 5 hours ago | parent | prev | next [-] | |||||||
It heavily depends on what you mean by "not the code", if all the code does is implement the necessary steps for the interface, then it's part of the interface. It's an interpretation of an interpretation of a datasheet. | ||||||||
| ▲ | 7 hours ago | parent | prev | next [-] | |||||||
| [deleted] | ||||||||
| ▲ | nicman23 33 minutes ago | parent | prev [-] | |||||||
i mean clean room was always license laundering and an AI agent cannot hold any copyright and it is largely not the same code | ||||||||