Maintainers who never expected their code to train models are adding clauses: no training without attribution, no use in certain applications, no commercial models. Each clause solves a grievance and breaks compatibility with the licences the ecosystem depends on.
The compatibility problem
Code under restricted terms cannot be combined freely with code under standard ones. Foundations are drafting guidance. The likely outcome is a new category of source-available licences and a lot of confusion in between.
Key takeaways
- Training restrictions are appearing in licences
- Compatibility with standard licences breaks
- Foundations are drafting guidance
This story is part of our ongoing coverage of policy & privacy. We will update it as more details emerge.
