01.08.21

InteLeaks – Part VIII: Microsoft and Its Facilitators Destroying Intel From the Inside

Posted in Hardware, Microsoft at 2:11 pm by Dr. Roy Schestowitz

Video download link

Summary: Intel is being ‘infested’ or increasingly dominated by people who lack technical skills and have an affinity for Microsoft’s proprietary software (even in divisions dedicated to GNU/Linux)

THIS series is getting longer and longer because of additional material and input that we receive (we've invited further contributions/contributors). We now expect at least two dozen parts and we’re grouping these parts based on issues, themes, aspects, and logical chronology. This is not “old news”; this is months old. It is still very much relevant.

“The video ends with a word or two about Microsoft’s role, which we’ll come to later on in the series.”This particular part focuses on Drupal; as we noted in the introduction, there’s also a Microsoft role (with more elements as covered in Part I, Part II, Part III, Part IV, Part V, Part VI, and Part VII).

This whole ‘InteLeaks’ series shows that Intel’s supposed “love” of Linux is mostly posturing or pretences. Check out this post from the so-called “Intel Community”. Intel is a corporation, not a community. They keep misusing that word. But look deeper at what Intel is doing. It’s incredible, isn’t it? Some ‘community’, eh? When we discussed it this morning MinceR said they “should have thought about that before handing money to the Redmond mafia” (they’re proposing Windows as a “solution”…)

“These people really like becoming victims of their own short-sighted decisions,” said to us a person who knows Intel from the inside. They’re harming their own clients. The above video mentions the M.E. as it says a lot about how Intel views its so-called ‘clients’ (that aren’t the United States military/government). MinceR asserted that “they’re too stupid to learn from their own mistakes, regardless of how many times they get burned…”

The video ends with a word or two about Microsoft’s role, which we’ll come to later on in the series. “Maybe Intel management doesn’t know what they want,” MinceR stated the other day, “try to survive [with Microsoft] or tie their destiny to Microsoft and go wherever Microsoft goes [...] then again, maybe they believe that they need to throw us [GNU/Linux users] a few bones temporarily before locking us into Microsoft world again or maybe they’re doing a similar kind of misdirection as the Redmond mafia, just less ad-based…”

The Intel insider said MinceR “is right on the money and this is what has disappointed me for a long time [as] it reeks of Stockholm Syndrome [and] really not much different from Microsoft tactics…”

“One story we heard concerns Drupal’s use and misuse, or even outright rejection.”We’ll make it more apparent later in this series that Intel seems eager to help Microsoft’s proprietary software monopoly (and an attack on software freedom) called GitHub. Why is Intel doing that? And about Drupal, which is also mentioned in length (Intel uses it internally), we’ve heard some truly disturbing stories…

One story we heard concerns Drupal’s use and misuse, or even outright rejection. “Information about the refusal to use a non-proprietary process,” one person told us, is quite a giveaway. It shows who really runs the company and what the real objectives are. Developers are ignored and clueless people override their decisions or veto common sense.

Intel engineers basically “developed a process using git and markdown to create guides,” one source told us. “This process was accepted as a process to create and collaborate on documentation efforts – replacing a proprietary process,” the source emphasised. “The previous proprietary process was using Microsoft or Google Docs with an Adobe-centric process of proprietary roots.”

The developers were eager to get rid of these proprietary monopolies. And they did it! “No to docx. No to your proprietary tools. No to your proprietary formats. Most devs were excited and happy to use this process,” we were told. “The publishing platform was Drupal, so it was about time! After a successful test – the process was in place for all future docs. The validation, product or engineering team would lead a doc project using the internal gitlab.”

“So from a proper, self-hosted, Free software process they moved to passing around Microsoft Word documents.”“The team would self-edit – on their time – and make a push request,” we were told. “After edits/review, the document was pushed to the Drupal instance and staged. Final review and approval – and the content was live. This process sped up time to publish and improved accuracy. The devs owned the doc project and future edits would be easy to apply.”

This was all very standards-based. As one Intel expert told us, “these days Markdown and LaTeX are just as easy to handle using web tools as Google Docs and Microsoft Word with vastly better results, so the problems with using freely available and generally user-friendly tools must be cultural…” (later adding that “this reminds me of what is going on at the Linux Foundation“)

cybrNaut has responded (in IRC) by saying: “I know some aerospace engineers who “can’t handle” LaTeX, so the project opted for genuine Microsoft Word, which of course is a complete disaster when checking binary docs into Clearcase and then doing a diff for reviews.”

“I didn’t accept the rationale,” he added, “that they can’t handle it… I think management just hates engineers to maintain docs that alienates managers [as] low-tech managers like Microsoft Word, and that preference gets imposed on engineers doing the real work. The project manager said “we don’t use LaTeX because no one knows it”. Then I went to a university and asked “why are these science students using Google Docs instead of LaTeX?” The reply was: “Because LaTeX is not in industry”…”

Going back to Intel, the same thing happened in Intel even after a proper process had been put in place and worked well.

“The preferred method was markdown,” we were told. “There was flexibility for rst or asciidocs as an alternate [format] if needed. The guides were published (in the end) as HTML.”

“After the process was in place,” we learned, “several teams (mostly low-technical or even close to what could be considered non-technical) refused to conform to the process and requested, first, to use Google Docs for a GNU/Linux project – this request was refused. A manager suggested reporting the non-conformity to other management.”

“To my knowledge,” we were told, “this was never pursued.”

One can guess where that went next.

Eventually the clueless dissenters decided to impose OOXML (docx) on everybody else. “The format was used with 0 versioning and multiple versions being passed around with no confirmation as to the “current” version.” What a mess. Welcome back to the 1990s with large E-mail attachments of proprietary Microsoft files.

“It sounds like the have a gaggle of Microsoft resellers embedded in the organization and, despite being on the payroll, working against the company to advance Microsoft goals against it from within.”
      –Anonymous
“After insisting the git process be conformed to,” we learned, “a resource reminded the group of a looming deadline at this point, and forced an exception in this case. First, the content of docs were staged in gitlab by a writing resource – in markdown.”

Welcome Microsoft mindset: “The engineering team stated they did not know markdown. Those on the team in another capacity – content strategy, still refused to edit in gitlab passing multiple versions of [OOXML] format after Google Docs was outright refused for this GNU/Linux project.”

So from a proper, self-hosted, Free software process they moved to passing around Microsoft Word documents. This is how you can quickly drive out any GNU/Linux talent you’ve managed to attract.

“This resonates strongly with me,” said a person who knows Intel insiders (former and current staff), “as their HR people’s attempt to reach out to potential candidates doesn’t even seem genuine. They know they need those people with GNU/Linux skills, but don’t even mention anything about the job out of a fear of never being able to attract them in the first place, if people knew what was going on from the inside.”

As someone else put it (having witnessed the above): “It sounds like the have a gaggle of Microsoft resellers embedded in the organization and, despite being on the payroll, working against the company to advance Microsoft goals against it from within.”

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

What Else is New


  1. InteLeaks – Part XXX: Harbor Research's Pseudo-scientific 'Research' for Intel, Bizarrely Suggesting a Microsoft Partnership for a Domain Largely Controlled or Dominated by Linux

    The full document that Intel paid for and in turn used to justify cracking down on Free software (obliterating Free software-based workflows inside Intel), instead outsourcing all sorts of things to proprietary software traps of Microsoft



  2. Chromium and Chrome Are Not Free Software But an Example of Microsoft-Fashioned Openwashing Tactics

    It's time to reject Google's Web monopoly (shared with other companies but still an oligopoly); removing its Web browser would be a good start



  3. Links 23/1/2021: Chromium Pains and New Debian Maintainers

    Links for the day



  4. InteLeaks – Part XXIX: Harbor Research Did Not Produce a Study But an Elaborate Hoax for Intel, Suggesting Microsoft Partnership and Outsourcing Based on Zero Evidence and No Solid Rationale

    The pseudo-scientific ‘report’ from Harbor Research is more of the same nonsense we’ve grown accustomed to; unethical if not rogue firms are being paid to lie — or to perpetuate falsehoods which someone stands to gain from



  5. Video: The State of Communities Surrounding GNU/Linux Distributions

    A discussion about the state of volunteer efforts going into the development, maintenance (in the 'maintainership' sense) and support/advocacy of GNU/Linux distros



  6. IRC Proceedings: Friday, January 22, 2021

    IRC logs for Friday, January 22, 2021



  7. InteLeaks – Part XXVIII: Intel Served Report From Microsoft Boosters, Who Provide No Actual Evidence and No Science to Back Their Supposed 'Findings'

    Findings and recommendations from Harbor 'Research' aren't based on any scientific methods, just perceived loyalty, branding, and a bunch of unsourced quotes (from unnamed people with ridiculous job titles like a soup of buzzwords)



  8. Erosion of Communities, Ascent of Corporate-Industrial Fake Communities

    Despite the attempts to manipulate/trick developers (and sometimes users) into becoming unpaid workforce of for-profit companies, there's an exodus back to real communities, which aren't subjected to the fury of wealthy shareholders who utterly dislike or simply don't care for software freedom



  9. The Corporate 'Left' and the Open Source Pseudo 'Movement'

    President Biden may not be as bad as his predecessor, but that hardly means very much; software freedom is still threatened, along with many other things



  10. Links 22/1/2021: pfSense Plus, Endless OS Foundation, and Many Laptops With GNU/Linux

    Links for the day



  11. The Linux Foundation is Trying to Obscure Racism Using Microsoft-Inspired Tactics (Vouchers Disguised as Actual Money)

    The Linux Foundation and its PR stunts don’t help combat racism; one might argue that the Foundation is leveraging racism, which prevails in the US, to paint itself as benevolent and caring (offering immaterial things and self-serving press releases)



  12. InteLeaks – Part XXVII: 'Pulling a Nokia' on Intel (Outsourcing to Microsoft)

    The recommendation of an Intel marriage with Microsoft (even in units that deal mostly with Linux) is an insulting slap across the face of developers employed there; we take a look at recommendations made to IoTG (Intel) by a firm with Microsoft orientation



  13. IRC Proceedings: Thursday, January 21, 2021

    IRC logs for Thursday, January 21, 2021



  14. InteLeaks – Part XXVI: Harbor Research is Horrible 'Research', Lacking Actual Technical Background

    Having looked at the members of staff of Harbor Research (individually), it seems clearer now why they have an affinity for Microsoft and why they're directing Intel to liaise with Microsoft and become a prisoner of Microsoft (even in areas where Microsoft is increasingly irrelevant)



  15. Links 21/1/2021: Raspberry Pi Pico, Ubuntu 21.04 Picks GNOME 3.38, KDE Plasma 5.21 Beta

    Links for the day



  16. How a Newly Inaugurated President Biden Can Advance Software Freedom (If He Actually Wishes to Do So)

    Techrights has 'Four Suggestions' to President Biden, the 46th 'front end' of American plutocracy



  17. InteLeaks – Part XXV: Intel's Brain Drain Leads to Unusual Measures

    As the company once known as 'chipzilla' loses its relevance and dominance in the market it's reaching out to retired people, trying to get them back onboard



  18. Hey Hi (AI) is Just a Trojan Horse for Illegal Software Patents, According to EPO Management and Litigation Firms It's in Bed With

    The longtime pushers or the lobby of patent profiteers just carry on pushing for software patents, nowadays latching onto the inane and unwarranted media hype around Hey Hi (AI) — a hype wave that was co-opted by EPO management to grant unlawful patents



  19. The Central Staff Representatives (CSC) of the EPO Are Petitioning to End the Assault on EPO Staff

    The EPO, just one month after the staff went on strike, is about to receive a compelling petition to stop the assault on EPO staff



  20. InteLeaks – Part XXIV: Love for Microsoft, Not for Free Software or Whatever Replaces Microsoft

    Intel is basing its big decisions on buzzwords and firms that master buzzwords; it's sad that instead of listening to Intel's own (in-house) engineers it's relying on a bunch of clowns who push 'Clown Computing' and 'apps' and 'UX'...



  21. IRC Proceedings: Wednesday, January 20, 2021

    IRC logs for Wednesday, January 20, 2021



  22. Links 21/1/2021: Google Tightens the Screws on Chromium, VideoLAN VLC 3.0.12

    Links for the day



  23. IBM Panics and Resorts to 'Customer Retention' Tactics With Red Hat Enterprise Linux (RHEL)

    IBM 'frees' RHEL but with limitations that can restrict growth of small companies (or subject them to financial barriers, originally unforeseen)



  24. Recent Techrights Articles About President Joe Biden

    Instead of writing yet more stuff about the latest US president, let's look back at what we wrote in recent weeks/months



  25. Links 20/1/2021: LibreOffice 7.1 RC2 and the RHEL Contingency

    Links for the day



  26. InteLeaks – Part XXIII: Intel Paying for Bogus 'Research' 'Insights' Which Merely Seek to Justify Outsourcing to Microsoft and Imposing Microsoft's Proprietary Software on Free Software Developers

    Intel's preference for Microsoft monopoly (an imposed/top-down decision) was seemingly certified by so-called 'consultants' and 'analysts' from the outside rather than the inside, basically manufacturing a false perception of consent after managers had already made up their minds



  27. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part V: How FSF Secrecy Ended Up Insulting People, Alienating Trans Developers

    Having just uploaded this introductory video, we delve into the backstory or the real reason the FSF sank into somewhat of a crisis with the trans community almost half a decade ago



  28. InteLeaks – Part XXII: Bubbles and Buzzwords, No Substance at Intel's Internet of Things (IoT) Group (IOTG)

    The video above is continuation of the previous part about a document full of superficial buzzwords (not technical jargon anywhere), in effect recommending to managers that they blindly follow trends and cargo cults (such as Clown Computing) and not what’s most suitable for technical excellence



  29. IRC Proceedings: Tuesday, January 19, 2021

    IRC logs for Tuesday, January 19, 2021



  30. Links 20/1/2021: WireGuard for pfSense and New US President

    Links for the day


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts