Contribute! Whonix Development Help Wanted! Check out the open Tasks on our new Issue Tracker!

Migration to our new phabricator bug tracker finished. Thanks to Jason Ayala who did most of the migration work!

Whonix Development Help Wanted!

Check out the list of all open issues (feature requests and bugs) that we would like seeing implemented:

Do you speak python? Check out our tasks with the python label:

Do you speak bash? Whonix’s build script is written in bash and so are most scripts developed by Whonix. Check out our tasks with the bash label:

Do you speak C? Mostly missing features in other upstream projects. Check out our tasks with the C code label:

Interested in Whonix Qubes? Check out the Qubes tag:

Interested in Whonix KVM? Check out the KVM tag:

Interested in Legal Issues? Check out the legal issues tag:

Want to see systemd support? Check out the systemd tag:

Interested in security hardening? Check out the security tag:

Want to improve user documentation? Check out the user documentation tag:

Want to backdoor resistance? Check out Verifiable Builds:

The full list of tags can be found here:

Too technical? Still not busy? Check out our Contribute wiki page:

Please contribute!

Why did we move to our self-hosted phabricator web app? Our Github issue tracker didn’t scale for Whonix since it’s a project at the size of a GNU/Linux distribution. Github doesn’t support roadmaps referencing tickets that are in different repositories/projects. Neither adding tickets to more than one roadmap is supported. And adding all tickets to one bug tracker rendered that tracker too crowded and therefore unusable. We’ve discussed this and agreed to move to use phabricator.

Old Github Issue Tracker:

New Phabricator Issue Tracker:

If you are interested to get e-mail notification about any new issue that is created so you can jump into the discussion, see this wiki link:

some users like @Lilias have created accounts , but they are waiting for account approval.

i dunno if this is good to have as an option , doesnt do any real mitigating to any threat. (spammer can be spammer even after approval).

If we didn’t have manual approval the admins would be spending time deleting spam posts instead of developing. At one point we were getting 20-25 new account requests a day. The sysadmin took measures to help out with this but its only for temporary mitigation until a permanent solution can be found.



1 Like

It been 1 year before, thats not any more temporary.

Very unlikely that any better solution will be found until phabricator implements one.