What about someone trying to use AI to make a new version of Qubes OS?
Similar to the problem described here, where someone used AI to rewrite Chardet and release it with a different license.
I don’t know if this is legal, but it does seem like something that has the potential to become problematic in the future.
I think Windows 11 uses AI and lacks sufficient testing and validation. However, if people contribute code after doing thorough testing, and if the acceptance process includes enough verification and testing, it probably wouldn’t cause too much negative impact. Besides, compared to mainstream Linux desktop environments, the number of people contributing code to Qubes OS is already quite small anyway.
Somewhat off topic, but given how many ways there are to contribute, the
number is very small.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
I would just like to bring up a way in which using AI can actually increase the number of all code contributions, be it exclusively man-made or AI-augmented work. AI can be used to protect against supply chain attacks, along the lines of what socket.dev does. This would lower the burden that individual developers have to carry when it comes to securing their private keys and thus lower the barrier to entry to developing new software for Qubes OS, a situation that I find myself in.
This becomes more relevant as the user count and total value secured by Qubes OS goes up – but we saw very strong growth in the last couple of months already.