Ian Jackson's general resolution to prevent init system coupling has failed to pass, the majority vote deciding that the resolution is unnecessary. This means that not only will Debian's default init be systemd, but packages will not be required to support other init systems. Presumably, this means that using other init systems on Debian (without using systemd as a base) will not be possible without major workarounds, or possibly at all. It also leaves the future of Debian projects such as kFreeBSD unclear, as systemd is linux specific.
The vote results can be found here
The winners are:
Option 4 "General Resolution is not required"
I would like to see the *BSD leadership teams make official statements about systemd now.
They could make their platforms far more appealing if they come out now and take a very resolute stand against systemd.
The *BSDs, and especially FreeBSD, are going to gain a lot of users once Debian 8 is out, and systemd is ruining workstations and servers left and right.
Knowing that the *BSDs will not tolerate systemd or systemd-like approaches will bring certainty to some victims who have just faced very uncertain times, and may just help keep away the deviants who have destroyed Debian so swiftly.
Why would they have to make such statement? Systemd is linux-only software, the authors have repeatedly said so. *BSD saying they do not plan to support it would be like saying they do not plan to support svchost.exe from Windows.
That is an apt comparison.
I, too, think it would be good to announce. I don't think that anyone would have predicted the current Debian debacle a year ago. But here we are. If it could happen to Debian, it could happen to FreeBSD, even if it is less likely and would take more work. With FreeBSD becoming the replacement for Debian for many users and businesses, it would be good to know that systemd will be defended against at all costs.