Ah - their use of EUPL was actually modified so it is only compatible with "AGPL v3 and OSL v2.1, v3.0" (https://github.com/arp242/goatcounter/blob/master/LICENSE). So really it seems this should be considered as licensed as those two.
Ah - their use of EUPL was actually modified so it is only compatible with "AGPL v3 and OSL v2.1, v3.0" (https://github.com/arp242/goatcounter/blob/master/LICENSE). So really it seems this should be considered as licensed as those two.
They have modified the EUPL license though, which means they have created another license which is incompatible with EUPL. I believe they should use a different name for the modified license. This is confusing.
> So really it seems this should be considered as licensed as those two.
If you create a different work based on the original (EUPL licensed) work and some AGPL code, you still have to abide by the EUPL but you license the resulting work as AGPL, so others have to abide by the AGPL only.
I'm not a lawyer
[1] https://joinup.ec.europa.eu/collection/eupl/matrix-eupl-comp...