4 ms·
If you don't know about the referral to the Debian Technical Committee, then there's a lot that you do not know (including to be wary of threads where "systemd"
by JdeBP 8y ago
If you don't know about the referral to the Debian Technical Committee, then there's a lot that you do not know (including to be wary of threads where "systemd" is mis-spelled "SystemD", as that is a common shibboleth).
There was a whole Hoo-Hah. It was years long. People resigned over it. The votes and discussions are often misrepresented by people recounting the tale. (Common misrepresentations: presenting it as a two-way contest between van Smoorenburg init+rc and systemd, when OpenRC and Upstart were both included, and both favoured over van Smoorenburg init+rc; presenting it as a single vote when there were several, including some votes on Debian General Resolutions by all of the club members; presenting the wiki pages written by the partisans and ignoring the lengthy technical reports from the TC members.)
- bayindirh 8y agoI'm aware of the Debian's Technical Committee, but I was unable to follow them all-along during that so-called discussion. During this period, I was a developer and so-called tech lead of a Debian derivative distro. We were working on some absurd requirement about generating system responses on some events, pulling continuous all-nighters. One day systemd packages arrived to Debian (sid or testing, I don't remember), and using it solved our problem. This is how I became aware that Debian packaged systemd, and it's gonna be the next default init, that's all. As I said before, I don't blindly support systemd or anything. I'm just using Debian for 14 years or so, and I'm riding on what comes along. I don't have time to devote serious development time to them, however I wish I was able to contribute into Debian or any serious FOSS project. Hmprhf.