Whonix is growing to a point, where I will be no longer able by time constraints to test, support or to vouch for everything.
I am still,
- building, sign, upload official images (that can be used for any platform, VirtualBox, KVM, Qubes)
- test VirtualBox / physical isolation compatibility
- VirtualBox / physical isolation leak tests
- maintain Whonix’s build script
- maintain most of Whonix’s packages
Yet, there is growing number of functionality I can not maintain myself. That means, for example I won’t be able to answer all KVM and Qubes specific questions. Neither I will be able to do leak testing for those platforms. I am not even sure I’ll be able to see if images even boot on these platforms.
So the question arises, what are official standpoints by the Whonix project. What is officially supported and what not.
I propose doing it similar to other distributions such as Debian. Several people maintain various stuff.
troubadoour: msgcollector_dispatch_x; AppArmor profiles
We’ll still all cooperate on everything. If I find something interesting about KVM/Qubes/AppArmor/etc. or you find bugs/have suggestions for various functionality of Whonix, we collaboratively work on it just as we do at the moment.
So what the maintainer would do, when new Whonix images are released, just see if everything works on your platform / parts as expected. And monitor the forums and answer specific questions about the parts you’re maintaining.
If that sounds okay, I would also like to document this. The equation and personality cult, Patrick = Whonix is not something I like anyway. So if I get for example a personal mail about KVM or so, I would like to redirect the request to the maintainer of KVM.
What do you think? We can also scratch the whole post and do it some other way.