Notes about things i found that could use clarification, or are ambiguous while installing and learning to use qubes

[redacted]

carrying on from this thread:

@redacted

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?

@unman

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.

I’ll just use this thread so i don’t clutter the pinned post, for things i feel like could be more clear in the OS preventing new users from having to consult the documentation so much. To be clear, even though i will be presenting examples that i found ambiguous or confusing, i’m not actually looking for help in this thread, in most cases the documentation thoroughly answered my questions. this is just for examples where i notice that usability could be improved or could be more intuitive in my opinion.