• blind3rdeye@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 months ago

    The full list: https://code.gouv.fr/sill/list

    Hold on. That page does not list VLC or KeePass. Is there more info about this other than the list? Or is the info in the title of this post incorrect?

    [edit]

    I see now. The page does not list VLC or KeePass, but those two both do come up if you put them into the search box. The software listed on the page is a very long list, but it is apparently on the ‘most popular’ stuff - not the entire list. (Although it is strange to see a heap of niche stuff, and stuff I’ve never heard of on the ‘most popular’ list while VLC doesn’t make the cut.)

    I’m not sure this list is a very strong endorsement by the French Government. It seems to just be listing free software options, and then asking other people to sign up to say which ones they use.

    • Jolteon@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Haven’t they also been trying to put back doors into everything for the last decade?

  • dwazou@jlai.luOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 months ago

    To be clear. This is a government agency endorsing the software as safe and effective. So bureaucrats and employees can’t be reprimanded they use them.

    This isn’t the French Prime Minister announcing the country will cancel Microsoft Office subscriptions and build a fund to support FOSS projects. Gimp has nowhere near the ressources they actually need.

  • Aatube@kbin.melroy.org
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    Redis is also on the list, but not Valkey. Gitea is on the list, but not Forgejo. Still nice to see governments endorsing the open-source-ish software they know and FOSS principles, though!

    • Tja@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      To be fair, I know redis and gitea (barely, gitlab is way more popular) and not the other two. Enterprise support and name recognition are quite important for government usage.

      • Aatube@kbin.melroy.org
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        Valkey was created recently as Redis changed their license, having clauses which made the user choose between being “discriminatory against users of the software that use proprietary software within their stack, as the license requires the open-sourcing of every part interacting with the service, which under these circumstances might not be possible” or being non-commercial. Forgejo was created when Gitea decided to go the JetBrains route a few years ago. It’s since absorbed Gitea’s clout.

          • Aatube@kbin.melroy.org
            link
            fedilink
            arrow-up
            0
            ·
            2 months ago

            Yeah, and you have to pay for that. Lots of open source software have enterprise support and usage limit licenses but having to pay for something isn’t open source. I am personally ambivalent at non-commercial licenses but I agree that the restriction against using proprietary software with Redis in commercial usage is kinda bad.

            • Tja@programming.dev
              link
              fedilink
              English
              arrow-up
              0
              ·
              2 months ago

              Of course you have to pay for a commercial license, it’s in the name. Development, tooling, support, etc, all costs money.

              I like the distinction. If you want to profit from open source, make your code open source. If not, pay up.

              • Aatube@kbin.melroy.org
                link
                fedilink
                arrow-up
                0
                ·
                2 months ago

                Sorry, I didn’t see the notification for some reason. The SSPL would prohibit people from running Redis from Windows, as Windows is proprietary. That forces them to use the source-available RSAL.

                • Tja@programming.dev
                  link
                  fedilink
                  English
                  arrow-up
                  0
                  ·
                  2 months ago

                  I don’t think that’s correct. It maybe prohibits people from building a service to offer redis to third parties on Windows, but you can run redis in your stack on whatever OS you want, as long as what you are building is not “redis as a service”. So any end-user SaaS that just uses redis as a cache is not bound to section 13.

                  And even if you built a redis as a service, the operating system is not explicitly mentioned in the license, so it would be for a lawyer to say whether that’s required…

    • Mouette@jlai.lu
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      They are not only no funding but largely not using it in practice and letting most public institution spent billions in Microsoft Office 365 contract