Create ecosystem map

[drivingreturns]

The problem you're addressing (if any)

Newcomers have a limited ability to discover the Qubes ecosystem, and who is investing in Qubes by using it.

The website currently contains selected endorsements, close working partners like Whonix, and research links, but presumably this is a small proportion of public users and omits some exciting active projects.

Tails, as an example with some common ground, does "who's using us" in a similar way to Qubes. However, it also includes a derivatives statement, including an assertion that they don't know of any current derivatives. With Qubes, I understand from the forum that there's at least one project being built on top (I'm unclear from the discussion whether it's okay to call it out - some posts have been flagged - so I won't here).

Original thread

The solution you'd like

A maintainable list of who works with Qubes, particularly including people building solutions on top of Qubes.

It's been suggested that the core team should not own such a list, out of concern that it would look like endorsement. This needs considering against the costs of not self-promoting effectively and making the community work harder to find useful information. It seems like it should be possible to implement in a way that can't reasonably be interpreted as endorsement, though a little caution is appreciable.

If it's something the core team would like to see but not to take responsibility for then saying so may make it more likely to happen.

The scope is information that is already public. The problem is mostly discoverability.

This could be done as part of a broader ecosystem map that also covers downstream partners ("what's inside of Qubes" does this at a high level, like a bill of materials). That's not the ask, but I'm mentioning it in case it's preferred.

The value to a user, and who that user might be

Newcomers might include users, analysts, potential collaborators, or funders, so there's good potential for missed connections we never find out about.

Non-newcomers may miss news about related projects, or may benefit from seeing everything in one place.

Completion criteria checklist

(This section is for developer use only. Please do not modify it.)