`BambuStudio` accused of violating `PrusaSlicer`'s AGPL after forking
A closed binary plugin attached to an AGPL fork is the risk. OSS-based products need clean architecture boundaries before distribution.
BambuStudioopened slicer code but allegedly kept the cloud-network plugin closed, creating AGPL compliance risk.- The plugin is described as required for core functionality, so file separation alone may not prove independence.
- AGPL forks are product decisions, not just repo decisions. Closed add-ons need legal and technical boundary checks early.