Change license to Apache 2.0 like SAM and SAM2

Thank you for this excellent work!

I wanted to raise a flag about the custom license. Using a non-standard license significantly complicates enterprise adoption compared to established licenses like Apache 2.0.

Meta has previously released repositories under Apache 2.0, including earlier SAM versions as well as other widely-successful models like DINOv2. This licensing choice was a key factor in their widespread enterprise adoption.

In enterprise environments, custom licenses trigger lengthy legal review processes which often take weeks or months with no guarantee of success. In contrast, well-known licenses like Apache 2.0, MIT, or BSD typically have pre-approved status, enabling immediate adoption.

Would you consider relicensing SAM3 under Apache 2.0 or another standard open-source license? This change would greatly increase the model's accessibility and impact in enterprise settings.

Thank you for considering this feedback.