I believe that’s their usual release process.
I believe that’s their usual release process.
Linux Genuine Advantage
SystemD also contains things like a network manager, dns resolving, ntp time sync and more, which I agree should not be so tightly coupled to the core init system.
Yeah I totally agree, I hate that they keep adding new stuff instead of focussing on their core business. It’s especially annoying as the Android Protonmail app and the regular web mail client are really bare bones and have several long standing issues. Honestly if I had set it up with my own domain instead of the @pm.me (which admittedly is a nice suffix) I probably wouldn’t be a paying customer anymore.
Exactly, it’s why I don’t buy Logitech anymore!
Sorry if I misunderstood your comment, it seemed like a metaphor for social media but perhaps I assumed too much. My bad!
You know you don’t have to doomscroll social media right? You can just, you know, not do social media.
I feel this is missing a couple of !important statements :)
I never said anything about Onyx, I don’t own one but have considered them. They look nice and open.
I do own a couple of Kobo devices though and just wanted to say it’s not running Android of any kind but it’s still relatively open. Especially compared to phones, tablets and Kindle. The firmware/OS point you’re trying to make is irrelevant there and I think you know it :)
There is NickelMenu and you can telnet into it. You can also install other OS like KOReader easily, it doesn’t have a locked bootloader or anything like that. So imho that’s pretty accessible and open.
We are talking about the Kobo right? It’s not running any kind of Android or AOSP fork.
No it’s not running Android.
Using Calibre you could probably glue that together. I wouldn’t want Android on an ereader personally.
It’s not open source but it is easily rooted and you can install custom add-ons or even replace the os.
If it’s important that it keeps running then it should just be redundant and taking one node down for an update shouldn’t be an issue. I know this is wishful thinking for a lot of services but I refuse to be on call for something if the client can’t be bothered to make it redundant.
That’s no longer a technical process issue but more of a teamcoach/HR kind of issue then. You should be able to assume good intentions from colleagues, imho.
We use a CI pipeline check which prevents merges to master if the code contains a TODO. A precommit hook only works if the developer has the hooks configured.
“The project is under very active development. Expect bugs and changes. Do not use it as the only way to store your photos and videos!”
If you want to simplify the maintenance burden of nagios-like setups, look into OMD by CheckMK.
You could also see it as you preventing someone else from learning from their own mistakes. Maybe reframing it like that could help with skipping :)