# Erupt Governance

## Maintenance

This project is maintained by YuePeng and contributors. Decisions are made by the maintainer with input from the community via GitHub Discussions.

## License Commitment

The open-source Erupt framework — including but not limited to `erupt-core`, `erupt-annotation`, `erupt-jpa`, `erupt-mongodb`, `erupt-upms`, `erupt-security`, `erupt-web`, `erupt-ai`, `erupt-ai-claw`, `erupt-cloud`, `erupt-job`, `erupt-monitor`, `erupt-generator`, `erupt-magic-api`, `erupt-notice`, `erupt-print`, `erupt-terminal`, `erupt-websocket`, `erupt-toolkit`, `erupt-tpl`, `erupt-excel`, and all current and future modules within the [`erupts/erupt`](https://github.com/erupts/erupt) repository — is and will always remain licensed under the **Apache License 2.0**.

We commit to the following:

- **No relicensing of the open-source core.** We have no plans to relicense to BSL (Business Source License), SSPL (Server Side Public License), Commons Clause, Elastic License 2.0, or any other non-OSI-approved license.
- **No retroactive license changes.** Code that is currently Apache 2.0 will remain Apache 2.0. Future contributions to the open-source repository are accepted under Apache 2.0.
- **Independent evolution.** Commercial extension modules (such as `erupt-chart`, `erupt-flow`, `erupt-tenant`, `erupt-cube`) are maintained in separate private repositories and do not affect the licensing, roadmap, or feature set of the open-source core.
- **Open-source first.** Bug fixes, performance improvements, and general utility features default to the open-source core. Only clearly enterprise-grade, advanced-scenario features (multi-tenant infrastructure, semantic-layer BI, workflow engines, etc.) are released as commercial modules.

If you are evaluating Erupt for long-term internal use, you can rely on the above commitment. The open-source license guarantees you the freedom to use, modify, and redistribute the framework forever — independent of any future direction the project or its maintainer may take.

## Decision-Making

- Routine maintenance, bug fixes, and feature implementation decisions are made by the maintainer.
- Larger architectural changes are discussed in [GitHub Discussions](https://github.com/erupts/erupt/discussions) before implementation.
- Anyone can propose a feature, report a bug, or submit a Pull Request; see [CONTRIBUTING.md](./CONTRIBUTING.md) for the process.

## Contact

- GitHub: [@erupts](https://github.com/erupts)
- Email: erupts@126.com