Video download link
Summary: We continue to look at the gory and embarrassing details about Intel and its mishandling of "Linux" (and of developers who actually have a clue)
TODAY we present more examples of the sorts of things happening inside Intel. This focuses on lack of understanding of GNU/Linux itself. Does Intel actually "love" Linux? Does it merely tolerate Linux? Does Intel only pretend while hiring a few people to maintain this pretence?
In the
introduction as well as
Part I,
Part II,
Part III,
Part IV,
Part V, and
Part VI we have shown that Intel may be lying about its relationship with GNU and Linux. The evidence suggests a serious problem and "what also becomes clear from the video," told us one person regarding Part VI, "is that Intel will always be in the Microsoft camp with one foot as well as keep their own employees and developers developing for their processors in that same camp, because there is always a way out (intentionally or not) and, what is worse, this prevents a lot of GNU/Linux developers from ever looking beyond Intel, so it's a bit like a WSL strategy to keep developers in the fold..."
The above video is a giveaway.
We're not going to write about the video itself and the video does not merely parrot what's shown, either. But it seems clear that Intel's quarter-hearted affair with GNU/Linux is barely even quarter-hearted. As one source once told us, "one interesting bit is a report submitted -- indicating there were non-technical teams (developer experience and even some engineers) who refused to use the FOSS BKMS and requested GNU Linux devs/authors to use proprietary software when FOSS processes were in place."
We're going to show that report at a later stage.
More information about the shortcomings of these staff (with no "GNU Linux" skills) making errors is presented in the video, but I think the interesting bit is that at Intel they "have a FOSS process," as a source explained to us, "and the teams REFUSED to use [the] FOSS process [which] is interesting information."
The plan from here onwards is to cover more examples of the above (or like the above), then show some of the internal battles over processes. Eventually we'll show Microsoft lurking in the shadows and release large documents, either redacted or mildly redacted (this will depend on various factors, unforeseeable for now).
⬆
