01.03.21
Gemini version available ♊︎InteLeaks – Part II: The GNU Linux Developer Experience at Intel Under Siege
Summary: Today we start the examination of documents from Intel staff; they show growing dissatisfaction among members of staff, who mean well but aren’t being listened to (despite having vastly better understanding of the subject at hand)
IN THE introduction and part I we presented a bit of a preview and a spoiler. The nature of the leaks is technical, it is not about something like financial fraud or a war crime, and it shows how Intel basically fakes its commitment to Free software or even the watered-down “Open Source”. When Intel talks about “openness” it means something like openwashing and outsourcing to Microsoft.
The series took a while to kick off/prepare/commence for several reasons, notably Christmas in the middle (bad time to attain high exposure) and the need to digest, then organise, the information. As explained this morning in a video, we’re going to present the material in bite-sized chunks. Wikileaks did a lot of that over the years, albeit it outsourced almost everything to Twitter and “tweets” are subjected to censorship, throttling, algorithmic manipulation (promotions and demotions), de-platforming and all sorts of other things (including spying in the background, not just on posters but also mere viewers).
“As promised, we’ll work on redacting the full raw material (redacted for source protection) in order to post it in full at the end…”Linking to pertinent items that we show will be a lot simpler if we isolate those items and post them as separate parts. As promised, we’ll work on redacting the full raw material (redacted for source protection) in order to post it in full at the end (so that nobody can accuse us of cherry-picking or taking things out of context).
Let’s start with the (almost) cover page:
What’s this all about? I’ve decided to make a video of it because it’s simpler and faster.
In the next part we’ll advance to some of the ‘beef’ of the concerns, or some of the things which alarmed Intel insiders. █