Does Whonix need to draft something, or will it work like last time, if coders put their hand up for a Qubes-Whonix (cross platform to non-Qubes-Whonix) application or whatever, it can be considered in the Qubes list like last time?
OK, so I guess that is a developer to developer discussion i.e. riding on their coattails if they are accepted again for 2018, and you’d just need to list 2 (maybe 3) things a young student could spend 3 months on then over at qubes-os.org link (below) - with enough detail as per other things listed there.
And it would have to be Qubes-Whonix specific, or preferably cross platform i.e. non-Qubes Whonix and Qubes-Whonix.
Could you please elaborate a little bit on the network and web fingerprint you are referring to? Do you mean that when Whonix supports and prefers connection to IPv6 Tor guard relays, it may be different from normal Debian Tor users?
Other than the IPv6 support, I identify Whonix localization as something very important:
input methods in non-Qubes-Whonix ( and maybe Qubes-Whonix )
different fonts selection and installation
switch from gui-message to gettext
setup translation groups and invite translators to translate at least GUI applications
split locale_settings wizard from Whonix-setup-wizard as a standalone wizard
integrate locale_settings wizard into Whonix-setup-wizard as a module
The localization may attract more users in the areas where Whonix is needed most. Localization for Whonix is very important partly because English may not be widely spoken or used by people in heavily censored areas.
I will definitely take is as a goal in my daily development. But do you consider Whonix localization as a good GSoC idea?
Hi @iry just an FYI I brought this up in my mail to Roger and will let you know of any updates when I hear back from him. Thanks for your awesome work on connection wizard. You’ve solved a big UX pain point for us.