Breaking Down [FEAT] Change Project License From

The shift from Apache 2.0 to AGPL-3.0 isn’t just a legal footnote - it’s a cultural pivot. Once seen as a safe, permissive gateway, Apache now faces fresh scrutiny as AGPL-3.0 demands stronger copyleft terms, reshaping how open source is shared and used. nn- The project now requires AGPL-3.0 for all contributions, changing how plugins, forks, and commercial use are governed.

• Legal texts in concept docs reference Apache-2.0 as a standard example, but AGPL-3.0’s viral copyleft means downstream projects inherit stricter sharing rules.
• Many teams mistakenly believe AGPL-2 or Apache-2.0 suffice for community plugins - AGPL-3.0 closes that gap, enforcing source availability. nnThis isn’t about restriction - it’s about alignment. AGPL-3.0 reflects a growing demand for transparency in open source, especially as platforms increasingly monetize community-driven code. The YAML plugin docs already reflect this shift, using Apache-2.0 as a placeholder, not a mandate. nnBut here is the catch: changing the license at scale risks breaking dependent projects that expect Apache’s loose terms. Misaligned dependencies can silently expose codebases to unexpected legal obligations - or worse, force premature forks. nnThe bottom line: license changes aren’t just technical - they’re cultural. They redefine trust, reuse, and responsibility. As AGPL-3.0 gains traction, developers must ask: are we embracing transparency, or just shifting obligations? Do your team’s workflows match the license’s intent?