• Avid Amoeba@lemmy.ca
          link
          fedilink
          arrow-up
          5
          ·
          edit-2
          2 months ago

          10 years security updates, plus security patches for community packages (instead of waiting on community patches). It’s basically the corporate support plan provided for free for up to 5 machines per account.

          • Cyborganism@lemmy.ca
            link
            fedilink
            arrow-up
            4
            ·
            2 months ago

            security patches for community packages (instead of waiting on community patches)

            I’m not sure I understand that part. Is Canonical implementing the patches instead of the open source project/package developers? I’m confused.

            • Avid Amoeba@lemmy.ca
              link
              fedilink
              arrow-up
              3
              ·
              edit-2
              2 months ago

              Exactly. In Debian, the community implements security patches. In Ubuntu, Canonical implements security patches for a part of the repo (main), the community implements them for the remainder (universe). This has been the standard since Ubuntu’s inception. With Ubuntu Pro, Canonical implements security patches for the whole repo (main and universe).

                • Avid Amoeba@lemmy.ca
                  link
                  fedilink
                  arrow-up
                  2
                  ·
                  edit-2
                  2 months ago

                  Not necessarily. For all of these cases, Debian, Ubuntu, Pro, the community and Canonical are package maintainers. Implementing patches means means one of: grabbing a patch from upstream and applying it to a package (least work, no upstream contribution); deriving a patch for the package from the latest upstream source (more work, no upstream contribution); creating a fix that doesn’t exist upstream and applying it to the package (most work, possible upstream contribution). I don’t know what their internal process is for this last case but I imagine they publish fixes. I’ve definitely seen Canonical upstreaming bug fixes in GNOME, because that’s where I have been paying attention to at some point in time. If you consider submitting such patches upstream as actively involved in project development, then they are actively involved. I probably wouldn’t consider that active involvement just like I don’t consider myself actively involved when I submit a bug fix to some project.

      • BeardedGingerWonder@feddit.uk
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        2 months ago

        Yeah, it’s fine. Haven’t had too much trouble in a good 10 odd years, once the WiFi drivers settled. Mind you I’m not fucking upgrading to 24.04 for another couple of weeks.

      • iopq@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        2 months ago

        Spent a ton of time trying to install GrapheneOS because web USB doesn’t work in snap version of chrome. How about letting me install the normal deb version? Nope, can’t let the user choose

        • tsugu@slrpnk.net
          link
          fedilink
          arrow-up
          3
          ·
          2 months ago

          Pretty much. Canonical made a few questionable choices in the past but overall they’ve done a lot for the Linux community. And their distro is very good. There is a reason why distros choose it as their base.