3 ms·
I really don't like the "hidden" enterprise license. On the surface you might assume it's AGPL 2.0 but upon careful inspection, there lives an enterprise commer
by upupandup 4y ago
I really don't like the "hidden" enterprise license. On the surface you might assume it's AGPL 2.0 but upon careful inspection, there lives an enterprise commercial license in the ee/ directory.
Wish you'd been more up front about this, for many organizations, the license is a make or break, as they often customize it for their use and distribution.
I'm walking away confused. Not sure if using this or creating derivative work from it results in being sent an invoice for an enterprise license or what the deal is.
- eatonphil 4y agoI took inspiration from the structure of Gitlab which commits ee code alongside open source (in the same style of folder structuring where everything outside of ee is open source and everything within ee is proprietary.) I'd like to keep it that way because it simplifies operations. But all the screenshots and website and docs only show open source features. And the core is Apache 2.0, not AGPL, as the license indicates. ee is only extensions on top. But there's not much to say about the ee folder because not much functionality exists yet in the ee version. In fact you can't even install the ee version in any form yet. Only the community edition is available for download. Happy for feedback in being clearer!
- upupandup 4y agoappreciate the response