• 27 Posts
  • 803 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle







  • This drama is from 2021. HA is still open source and has been great.

    The Nix maintainers come off pretty entitled in this one. They ignore advice, requests and do not provide an engineering solution that could solve this without incurring the cost HA would bear. You don’t get to dictate or create work for an open source project that wasn’t designed to play well in your environment. If you want to get it to play nice in there, come up with a proposal that the upstream accepts and implement it. Better yet, come up with a design of your system that accommodates the upstream project. If you go ahead and create that work anyway, upstream can use the tools at their disposal to prevent that.







  • Avid Amoeba@lemmy.catolinuxmemes@lemmy.worldapt install firefox
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    edit-2
    2 days ago

    Ignore the noise and go with Ubuntu LTS. When you get comfortable with that, you could try Debian.

    You could play it backwards too. Try Debian, if you can’t get it to do what you want, wipe and do Ubuntu LTS. But I do not recommend this path if you have no idea what you’re doing. People underestimate how difficult it is to do simple things when you don’t know how to, no matter how trivial.





  • 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.



  • 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).