If I understand Devuian correctly, they will port releases of core software off of systemd and back to init, giving you the option of still using core software packages without systemd.
> Devuan will derive its own installer and package repositories from Debian, modifying them where necessary, with the first goal of removing systemd
Debian is committed to support sysvinit for the next release at least. I really doubt anyone in Debian will add dependencies on systemd "just because": if they do so they may have compelling reasons (eg. ConsoleKit is unmaintained and broken) and the correct reaction would be to fix the issue (eg. like the ConsoleKit2 people are trying to do) rather than forking Debian just to ignore the issue.
Not that forking Debian is bad and people should not do it for whatever irrational reason if they want: it's just that in this case there's no rational reason the same task couldn't have been carried over in Debian itself other than the fact that in your own fork you may accept lower quality contributions more easily.
From what I see on the devuan page, in the spirit of FOSS, the people that prefer to keep init as part of their setup, have forked debian into devuan, and propose to retain the "init based debian", for people that prefer init scripts.
That's the shortest summary I could come up with for you.
Another short writeup by @tinco https://news.ycombinator.com/item?id=9094142
Maybe the downvoter(s) were some of the same folks who raised their concerns in the above thread? Or maybe it's just the typical systemd holy war going on. I'd guess the former though.