Actually, 100% of what I said is true. Let’s go through it together
Microsoft does not own systemd
True.
The closest thing to an “owner” the project has would be Red Hat (not owned by MS), but it’s had over 2000 authors in its time.
And even if they did, and put copilot into it, distros could still choose to not use it
True.
This in fact happens already. Lots of distros that use systemd only use some components of it. It’s GPL code, you can do that…
Now let’s move on to Lennart Poettering.
Yeah, he was one of the top people behind systemd, and he has now moved to a job within Microsoft. What’s your point? That doesn’t mean systemd is Microsoft property now. That’s not how it works lol. PulseAudio isn’t either.
They own Linux, too. Just wait for systemd-copilot.
They dont own it, they just own seats at the foundation table and thats not even 50% of the seats :p
Microsoft does not own systemd
And even if they did, and put copilot into it, distros could still choose to not use it
Nothing you wrote is true. Google Lennart Poettering.
Actually, 100% of what I said is true. Let’s go through it together
True.
The closest thing to an “owner” the project has would be Red Hat (not owned by MS), but it’s had over 2000 authors in its time.
True.
This in fact happens already. Lots of distros that use systemd only use some components of it. It’s GPL code, you can do that…
Now let’s move on to Lennart Poettering.
Yeah, he was one of the top people behind systemd, and he has now moved to a job within Microsoft. What’s your point? That doesn’t mean systemd is Microsoft property now. That’s not how it works lol. PulseAudio isn’t either.