Hi @Sven! I’ll ask the question naively in the hopes that it’s useful. If it’s not, please disregard.
If there is already a solution being worked on (on GitHub), isn’t it somewhat late to determine if solving the problem now aligns with the current priorities?
I love the idea of opening a thread to discuss problems, define them, understand their impact then discuss priorities and possible solutions.
I do believe that the forum is probably a better place than GutHub to do that because I think it is more accessible to a more diverse crowd. (The forum is also where some (a lot of?) problem symptoms are first raised, which may prove convenient.)
I have no doubt that when the time comes to work on a solution, the GitHub issue will be more useful if it can be focused the technical aspects (the how) because the problem to solve has been scoped (the what and who, considering there is the Qubes OS team and contributors) and its priority established (the when) in the forum.
That being said, all that assumes that the conversations happens before the work on a solution is started.
Additional (but related) question: when it comes to finding out what priority to assign to any given problem, is there any place where the current goals are published?
I suppose there are roadmaps somewhere, but don’t know if they are not public already. In my opinion, having a public list of priorities to refer to would be helpful when finding out if a given piece of work is more suited for community contributions or should be driven mainly by the Qubes OS team. And maybe once decisions are made contributors can refer to that same list in order to ensure their constibutions are effective. (That’s the part that interests me the most at the moment )