Thank you for finally opening up Bitcoin donations. Qubes is already quite good, and I’m happy to chip in something to help fund the development, even if it’s only enough for ~1 man/woman-hour or so. I’ll donate as soon as I can.
I’d like to use this opportunity to do exactly what you said not to: a feature request :). One of my main problems with Qubes in its current state is how it handles device attachments. Right now, the Qubes VM Manager handles device attachment in a ‘VM-centric’ way: I have to look at each VM’s attached devices to find the one which has a specific device. But what I find is that I really need a ‘device-centric’ manager: I want to see each device in a list (preferably with an editable label, so I can name my USB controllers ‘rear left’, ‘front right’, etc., at least until proper USB VM support is added) with its attached VM. I should be able to detach a device from its current VM, switch it to a different VM, etc. This would simplify my life quite a bit, and I don’t think it would be too hard. In principle I would be fine to make these changes myself, but I just do not have the time, especially within the next month or so.
For me, the next step would be device-triggered VM attachments, though I imagine this would be a bit more difficult. I envision this working as follows: I plug in my smart card reader, some Dom0 daemon sees the device attachment, finds the reader USB VID/PID in my specified map file, attaches the corresponding USB controller to the map file’s specified VM, then starts that VM. That would be really neat, even if it assumes all devices (or is only restricted to one device) on a controller map to the same VM.
And for what it’s worth, my next most desired feature request is split GPG. I would rather see this feature even without your ‘true’ split idea, where no untrusted external input (public keys) must be imported into the GPG VM–that’s nice and important in theory, but honestly (IMO) not as important in practice.
Thanks for all the good work!