@kobit any preferences how to name those packages? suggestions for foss: dist-foss, dist-community; suggestions for commercial one: dist-acs, dist-enterprise, dist-non-foss, dist-commercial?

And one more thing @kobit - what should we do with tigase-spam? It's not open-source/FOSS but from what I remember it's mostly because to avoid publishing the anti-spam logic to avoid making life easier for spammers ( @andrzej.wojcik , care to comment as well?)

If we would include Tigase-spam then I would suggest naming “free” package “dist-community” to not confuse people as Tigase-spam is not open source. As for full package including ACS, I would go with “dist-enterprise”

1. Let's make it open source for the tigase-spam.
2. The open source packages, let's use a simple naming like just "dist"
3. For the non-open source, "dist-enterprise" seems like a good way, as it gives us opportunity to put there more than just ACS, if we ever need.

One question though, are we making dist-enterprise a complete Tigase server distribution or just put there non-open source code which then have to be combined with the open source package to have a working system? For simplicity for end-users I think it would be better to have a complete system under dist-enterprise.

I was thinking that dist-enterprise would be a complete distribution to reduce mistakes for end uses, ie. they could mismatch versions of acs with versions of the server, etc.

As for foss version, I think it would be better to make clear statement that this is “free” distribution. But it would be good to clarify if we will still gather metrics from those packages or not.

I was thinking that dist-enterprise would be a complete distribution to reduce mistakes for end uses, ie. they could mismatch versions of acs with versions of the server, etc.

Ok, this makes a lot of sense.

As for foss version, I think it would be better to make clear statement that this is “free” distribution. But it would be good to clarify if we will still gather metrics from those packages or not.

I would like the Tigase to be seen as FOSS first, as our primary and main activity. I am afraid that adding "free" or "foss" or something like this may give out an impression that there is something else hidden, underneath which is not free and not open source. So, I would prefer to have a very simple naming, just "dist". Look at others, like prosody and just other open source projects. They do not put free or foss in their package names.

Look, we are working on our new OS website (tigase.org), where we will not have any mention of our commercial stuff. I want to "convert" Tigase's image to a company offering open source software and services based on open source code: https://tigase.github.io/os-website/. We will only have a link to a different website with our commercial stuff. Right now the link points to our current .net website but we are changing this one too and we have a new .net website under works.

Also, we will not gather any metrics from installations based on FOSS only code. Except, of course, some basic information about installed systems from the updates checker.

I'm not against simple "dist", I was just leaning towards "dist-community", but I see your point.

Yes, both distributions will be "complete" in the sense that they will have complete and working server installation. The only difference will be (well, is) that "enterprise" will have a couple of additional libraries, that's all.

As for name, given complete turn towards FOSS and it being centerstage of all things having simple "dist" (or even "tigase-server-.!) seems to make sense - I'll change it accordingly.

Let's make it open source for the tigase-spam.

I'll open it but first add licence/readme.

@kobit one more thing that struck my attention - until now we provided docker image with "dist-max" version. Should we create two docker images accordingly as well?

EDIT: while working on Dockerfile for 8.2.0 I added support for two flavours: https://github.com/tigase/tigase-xmpp-server-docker/commit/0f1775551a9b407f1e17edc1be15b443e549d3cd - we can probably go with it.

Yes, we need 2 docker images for each package.

I see that you generate the docker image by TYPE, very clever, good work.

I think it is better to put "support@tigase.net" instead of office@tigase.net.

Updated e-mail address. Will generate images once 8.2 is release (~in a week)