Simon - speech activated user interface for KDE (KDE.News)

I did not say that it did. Fedora's policy is more nuanced than what is strictly allowed by the GPL. If individual users want to use the proprietary toolchain, they are free to, but at the project level Fedora puts a heavy emphasis on an open toolchain for contributors to use in testing and maintenance. I can use intel's icc compiler on my own systems for its parallelization support..Fedora's not going to stop me...but I can't be expected to submit code to Fedora packages which require icc specific features to be useful. If dependency has to be built with a proprietary toolchain, its inclusion would be exceptional and would require significant discussion methinks.

The devil's in the details. I think a lot of people would need to study up on the details of this codebase interaction with proprietary bits, this is not a fire and forget situation by any means. The point is, this isn't a common situation in terms of licensing a functional software stack, nor is it ideal. It outside standing policy and common practise.

-jef