How to contact an official to get the most accurate answer

General Discussion
1

Asking questions in the community is a good choice, but sometimes you will face two problems:

1.No one answered

  1. You don’t know whether the answer is correct

So can I find an official answer to the question? Is there any such channel?

1 Like
2

Best bet is to create a GitHub issue, as long as it respects the guidelines.

2 Likes
3

GitHub is not for user support. Dont ask support questions there, but
here or in the mailing lists.

If you are given a wrong answer, generally it will be corrected. You can
also judge answers by reputation of the person who answers you.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

5 Likes
4

If no one answers, you can try to edit your original post to provide detailed information and/or remove useless text.

If you don’t know if the answer is correct, do some research about the answer, use a test qube to see how it works, etc. If you are still not sure, ask others to confirm.

2 Likes
5

I mentioned GitHub with the explicit disclaimer “as long as it respects the guidelines”.

Implementation design choices or issues for instance are better discussed on GitHub IMO as it’s related to the code and development, but it’s really not a place for support question obviously.

3 Likes
6

I thought it best to be explicit.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

2 Likes
7

In that case, either no one knows the answer, or those who know the answer are unwilling to answer (e.g., they’re too busy). You can’t force people to answer your questions. Even if you were to try to contact official people directly, you would likely not receive an answer. If you want to pay someone to help you directly, you could try this:

The official documentation is the best solution:

We have the qubes-devel mailing list for questions and discussion about code and development topics:

This list is primarily intended for people who are interested in contributing to Qubes or who are willing to learn more about its architecture and implementation. Examples of topics and questions suitable for this list include:

  • Questions about why we made certain architecture or implementation decisions.
    • For example: “Why did you implement XYZ this way and not the other way?”
  • Questions about code layout and where code is for certain functionality.
  • Discussions about proposed new features, patches, etc.
    • For example: “I would like to implement feature XYZ.”
  • Contributed code and patches.
  • Security discussions which are relevant to Qubes in some way.

By contrast, GitHub issues (qubes-isssues) should be reserved exclusively for actionable bug reports, feature requests, and tasks. The only questions or discussions allowed there are those required to take action on specific issues.

5 Likes