[WIP] Update license from Apache 2.0 to GNU GPL v3.0

[Copilot]

License Change from Apache 2.0 to GPL-3.0

Changes Required:

• Replace LICENSE file content with official GPL-3.0 license text
• Update CONTRIBUTING.md to reference GPL-3.0 instead of MIT License
• Verify composer.json license field (already correct: GPL-3.0)
• Verify .github/copilot-instructions.md (already correct: GPL-3.0)
• Run consistency check to ensure no remaining Apache 2.0 references
• Request code review

Files to Update:

1. LICENSE - Replace Apache 2.0 text with GPL-3.0 text
2. CONTRIBUTING.md - Update contribution license statement from MIT to GPL-3.0

Files Already Correct:

• ✅ composer.json (already has GPL-3.0)
• ✅ .github/copilot-instructions.md (already mentions GPL-3.0)
• ✅ README.md (generic reference to LICENSE file)
• ✅ Source files (no license headers present)

Original prompt

We need to change the license of the OpenForgeProject/mageforge repository from Apache License 2.0 to GNU GPL v3.0.

Tasks:

1. Update the root LICENSE file

   • Replace the existing Apache 2.0 license text with the full official text of the GNU General Public License version 3 (GPL-3.0).
   • Ensure the copyright header refers to the project and credits the existing owner (OpenForgeProject) and year ranges appropriately (e.g., 2024–2026 or according to existing headers in the repo).

2. Update any references to the license in the repository

   • Search the repository for references to "Apache License", "Apache-2.0", or similar.
   • Update composer.json, package.json, pyproject.toml, or other manifest/config files to set the license to GPL-3.0-or-later (or GPL-3.0-only if that matches existing project intent). For a Magento 2 PHP module, this will most likely be in composer.json.
   • Update README and documentation files where the current license is mentioned, changing wording from Apache 2.0 to GPL-3.0 (and adjusting badges if present).

3. Source file headers (if present)

   • If PHP or other source files contain license headers that explicitly mention Apache 2.0, update those headers to refer to GPL-3.0 instead, using a standard short GPL header, e.g.:
     "This program is free software: you can redistribute it and/or modify
     it under the terms of the GNU General Public License as published by
     the Free Software Foundation, either version 3 of the License, or
     (at your option) any later version."
   • Keep existing copyright notices and author names.

4. GitHub metadata

   • Make sure that any GitHub-specific files (e.g., .github templates, FUNDING, etc.) that reference Apache 2.0 are updated to GPL-3.0.

5. Consistency check

   • Ensure there are no remaining references to Apache 2.0 in the repo.
   • Run any existing linters or tests (if configured) to confirm no automated checks fail due to the license change.

Scope notes:

• Do NOT change any functional code or behavior beyond updating license headers and metadata.
• Do NOT add new dependencies or features.

Deliverables:

• A pull request against the main branch of OpenForgeProject/mageforge with all of the above changes applied.
• A clear PR title and description explaining that this is a license change from Apache 2.0 to GPL-3.0 and listing the main updated files (LICENSE, composer.json, README, headers, etc.).

This pull request was created from Copilot chat.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.