TLDR: It’s compatible with other copy-left licenses like GPLv3. However, it’s available in multiple languages, which technically makes it more applicable.

I started using it for my own project. If you want a practical example: https://github.com/TimoKats/emmer

  • yetAnotherUser@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    1
    ·
    16 days ago

    I am not an expert in copyright law, which is what these licenses are based upon and cannot analyze the text.

    Still, couldn’t you make it even more straightforward by forking twice yourself?

    1. Take the original EUPL code and fork it under the LGPL
    2. Take the LGPL code and fork it under the LGPL
    3. This second fork has all EUPL conditions removed

    I’d by surprised if the license authors did not consider this. Lawyers wrote this with consideration of EU law after all, not some laypeople.

    If I had to guess: Any inclusion of EUPL code in another project would have to be marked as being under the EUPL. This is solely to inform anyone who wants to fork this section and distribute the code in form of SaaS to abide by source code requests.

    It’s like an EU variant of the AGPL whose many conditions about linking apparently don’t hold up in EU court. The GPL’s are all primarily considering US copyright law after all.