See also: Why is Qubes OS project team so small? [Edited: link to the root topic]
Perhaps the proposal in issue 8945 would be better suited to an unofficial, community-run, “Qubes universe” organization?
It seems that currently there is the core Qubes project (at github.com-QubesOS, and elsewhere), there is github.com-QubesOS-contrib, and then there is an unorganized constellation of unofficial VCS/forge accounts, package repositories and personal websites run by individuals. (I may be missing something here, I’ve been using Qubes for many years but I don’t always keep up with development news.)
Maybe it could make sense to organize some of those individuals into a somewhat centralized coordination space. Hopefully this could also make it easier for less experienced community members (such as myself) to contribute in a greater way.
A community-run project could in theory iterate faster, and then bundle up their changes and periodically propose pull requests to the Qubes core team. But these pull requests would be less frequent, more polished, and come with built-in process such as reviews.
This would also cut down on the noise in the core team’s issue trackers and mean that the core team would not have to field so much interaction with less experienced contributors (such as myself).
I agree with some of the comments on the GH issue – I too would ideally like to see more review happening in the core Qubes project, not less. (A 2+ review-signature scheme would be great.)
Overall, I really appreciate the approach that the core Qubes team have taken so far. (And very much appreciate their work.)
Is there interest in this? I’m especially curious to know if there is interest from two groups of people:
-
The handful of individuals who already run unofficial Qubes-related VCS/forge accounts, package repositories, etc. that get significant usage by Qubes users.
-
Qubes users and community members who contribute infrequently or not at all, but who would like to contribute more.
