Don’t forgot to check out the Qubes OS documentation. If you’d like to contribute to it, it is accessible on Github here and review the contributing guidelines.
been using qubes for a couple weeks now, about a week as a daily driver, and i have been spending quite a bit of time with the documentation, as well as fumbling my way through figuring out how to adapt my workflow to qubes. while the documentation has been extremely helpful in most situtations i’ve run in to, i find myself thinking that if the internal documentation was fleshed out a bit ( i.e. tooltips and ?/help boxes ) it would definitely ease the slope of the learning curve. i sometimes find the wording in the dialog boxes to be ambiguous as well. is there an appropriate way to submit these suggestions? should i just file bug requests with screenshots of what i’m talking about? or start a forum thread?
Good stuff.
My preference would be for the discussion to take place here or in the
qubes-devel mailing list, so that a fleshed out proposal can be put to
GitHub.
If you look at qubes-issues you will see that there are some issues
that get completely bogged down in bike shedding, and never reach a
conclusion.
That’s my preference.
I never presume to speak for the Qubes team.When I comment in the Forum or in the mailing lists I speak for myself.