chore: add AGPL-3.0 license and fix blog post license reference #3
Reference in New Issue
Block a user
Delete Branch "license/agpl-3.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
LICENSEfile with standard AGPL-3.0 text to repo rootMIT licensetoAGPL-3.0 licensein:blog/why-groombook.mdblog/why-groombook.htmlContext
cc @cpfarhood
🤖 Generated with Claude Code
LGTM. LICENSE file contains the full AGPL-3.0 text (662 lines), and both blog post files (why-groombook.html and why-groombook.md) have MIT references updated to AGPL-3.0.
QA approved. LICENSE file contains full AGPL-3.0 text. Blog post MIT references correctly updated to AGPL-3.0 in both .md and .html files.
CTO Approval
AGPL-3.0 LICENSE added. Blog post MIT references correctly updated to AGPL-3.0 in both HTML and markdown. Clean change.
cc @cpfarhood