FLOSS virtualization hacker, occasional brewer
I swear people have rose tinted glasses as to the state of the init system before the current generation of system management daemons.
If you really want to have Debian without systemd there is always Duvean but the Debian architects are free to choose the technologies that solve the very real system orchestration problems that exist.
Who are the community employing? Why do they need consulting before code changes are made?
What a pointless drama article this is. FLOSS software does stuff for legal compliance more often than you’d think. The whole point is people can contribute fly by patches and the maintainers make the decision to merge. It seems like being an optional field but potentially providing useful functionality is enough for systemd. If you don’t like it I’m sure there are forks you could join or even use a different init system. No one’s freedom is being oppressed here.
Stable package > back port package > flatpak/snap.
Basically I want everything as stable as possible unless I have a particular need for a newer feature.
The main things I run from flatpak/snap are browsers and the Minecraft launcher because they are both regularly updated.
I expect because it wasn’t a user - just a random passer by throwing stones on their own personal crusade. The project only has two major contributors who are now being harassed in the issues for the choices they make about how to run their project.
Someone might fork it and continue with pure artisanal human crafted code but such forks tend to die off in the long run.
You need adversarialy trained mud splats: https://www.youtube.com/watch?v=uB0gr7Fh6lY
When it comes to export controls and sanctioned entities it doesn’t really matter what Red Hat would like to do - they have to comply with the law in the jurisdictions they work in. Even if it was purely a community project individual contributors face a similar liability if based in those jurisdictions.
When it comes to sanction lists there is a fair amount of commonalty between the US and Europe. This is really something to complain to government about.
Imgur has been offline in the UK since the original investigation. Do they even want to be in the UK market?
There are a fair number of third party boards based on the RP2040/RP2050 silicon. Even esphome can target it even though it originally targeted the esp32.
The silicon itself is pretty nice although the original had done problems with deep sleep.
Are they as well supported? There are lots of SBCs out there but if they are only supported by vendor kernels and have no documentation then i’d rather pay the Pi premium.
ETA: that said for a lot of stuff microcontrollers are a much better bet.
They are pretty good at summarisation. If I want to catch up with a long review thread on a patch series I’ve just started looking at I occasionally ask Gemini to outline the development so far and the remaining issues.
I guess somewhere between 6 and 7…urm 6/7 👐 (and my kids say I don’t understand memes 😅).
I think the OP’s analysis might have made a bit of a jump from overall levels of hobbyist maintainers to what percentage of shipping code is maintained by people in their spare time.
While the experiences of OpenSSL and xz should certainly drive us find better ways of funding underlying infrastructure you do see a higher participation rates of paid maintainers where the returns are more obvious. The silicon vendors get involved in the kernel because it’s in their underlying interests to do so - and the kernel benefits as a result.
I maintain a couple of hobbyist packages on my spare time but it will never be a funded gig because comparatively fewer people use them compared to DAYJOB’s project which can make a difference to companies bottom lines.
The year of Linux on the desktop is whatever year you personally switched over.
Now I’ve read the article it’s unnamed industry analysts and it’s written by an AI. For all I know the AI has hallucinated the number.
I assume microcontrollers. Most of those are invisible to consumers.
Modern machines have TPM so we can do attested boot and validate a system hasn’t been tampered with. They don’t need third party kernel modules to test that.
mu4e inside my Emacs session.
Cost, the reason is cost.
They don’t, just like they don’t with human submitted stuff. The point of the Signed-off-by is the author attests they have the rights to submit the code.