Unclear license

[torakiki]

Hello,
I'm trying to understand the licensing model can you help me out?

• first I strongly suggest you to put a license header on every file so it's clear what is the file license
• second, the caption says An open-source localization platform and if I look at the LICENSE file in the root and in the GitHub details section it says it's APLv2 so to me the project is apache licensed but I found only by chance that the ee module has a different (non FOSS?) license. This is confusing (to say the least), maybe you could consider moving it to a different repo with its own LICENSE file.
• third, the ee LICENSE file is... ehm... not a license file? I'd consider to accept the Enterprise Edition of Tolgee but where is it? No license header, no license text so what's the license of the files in the ee directory? Are they APLv2 or does this useless LICENSE file apply to them?
• and last, so what happens if I clone and run the repo or if I try to self host? I assume I'm running an open source software but am I? or does it bring in some of the ee files, for which I should agree some terms which I cannot find?

Don't get me wrong, I understand the struggle and the frustration to make FOSS financially viable (welcome to the club BTW) but the current state, unless I missed something, is confusing and wrong. The repo says 'open source' in it's README and LICENSE file, you shouldn't have a proprietary license in a random directory

[JanCizmar]

Hello!

Thanks for the query. 🙂

I have to admit that your points are relevant. I will consult this with our legal team, and we will take steps to fix this issue and make the licensing transparent.

The first step is clarifying the licensing without moving the ee code out.

The second step is making the ee directories removable so you can build a fully FOSS version of the version without the need to make other changes to the code. It's planned for 2025 since that wouldn't be an easy task and would slow our development of new features, which is our priority.

However, we don't plan to move the ee stuff to other repository, since that would make our code less manageable and harder to contribute.

[torakiki]

Hello,
great, I think as long as it clarifies what's open source and what's not, whatever works for you I think is fine.
So, just to be fully sure, at the moment if I clone the repo and try to run the application I need what is in the ee directory which is not APLv2, correct?

[JanCizmar]

I have an update! We have made the ee and webapp/src/ee directories deletable, so you are able to remove them to get working community version. We even have added some tests.

I am also currently working with lawyers on providing right EE licence for the ee directories, but for sure we will base it on the Elastic License v2. Also, we will fix the terms so it works fine with the free self-hosted plans - so the licensing is clear when you use Tolgee Docker images and binaries including the ee code.

[torakiki]

Great to see things moving forward on this!