Lunduke
News • Science & Tech
SUSE's ex-CEO ousted after greenlighting "risky deals"
New details uncovered about the abrupt departure of the Linux company's CEO earlier this year.
December 01, 2023
post photo preview

On March 22nd of this year, the CEO of SUSE (Melissa di Donato) was unexpectedly announced to no longer be working for the Linux company -- effective that very day.

At the time, it seemed likely (but unconfirmed) that di Donato was fired from her position simply based on her less than stellar performance in the role.

  • She oversaw the IPO of SUSE on the German Stock Exchange, which had results which were "not great" at first.  Then it got worse.
  • As time went on, di Donato oversaw SUSE as it lost close to half of the company's valuation (eventually leading the majority shareholders to seek a de-listing of the company).
  • The CEO was so desperate for positive press, that SUSE paid multiple companies to give her fake awards.  Seriously.  That actually happened.

In the days following di Donato's ousting, confidential sources suggested to The Lunduke Journal that there was more to the story -- that there were significant, non-public reasons for her "immediate departure".  More than simply poor performance and cringe-worthy, self-awards.

Thanks to new reporting from Reuters, we might be gaining new insight into what those reasons might be.

Apparently, under di Donato, the SUSE Board felt it was necessary to create a new "Deal Desk" to research and authorize any sizable corporate deal -- to ensure that it was not a "high risk" deal for SUSE.  Even going so far as to issue a warning, to shareholders, about such potentially risky existing deals.

When a corporate Board establishes a new system to review "risky" deals made under specific leadership... that is a pretty strong indicator that "risky" deals were being made.

Where there's smoke... there's fire.

From the Reuters article:

"SUSE may enter into high-risk or commercially inappropriate deals if it does not exercise effective control over the Sales organization," it said in the report. The company noted that "'Commercial governance' is a newly identified risk this year" and a heatmap in the report ranked the risk as "possible" and its impact on the business as "high".

A warning to shareholders -- along with assurances the the company would be protected from future risky deals by the new "Deals Desk" -- was issued on January 19th.  The SUSE CEO was ousted, without notice, on March 22nd.

So what, exactly, happened in the 63 days between those two events?

It turns out... big, risky deals.  And those new deals did not get reviewed by that "Deal Desk".

"According to four documents reviewed by Reuters and two of the people with knowledge of the situation, Di Donato greenlighted the commercial terms of a roughly $1.4 million sale to South African utility Eskom in late January, bypassing the deal desk's scrutiny in order to speed the process, less than two weeks after SUSE told investors the desk would help to improve controls."

Reuters obtained internal SUSE emails that appear to corroborate this:

"On January 30,  after commercial terms of the Eskom deal had been agreed, a senior SUSE executive said in an email to other company officials that the terms had not been submitted to the deal desk.

 

In late February, an executive told colleagues in an email that the sale had not been scrutinized by the deal desk."

Then, a few weeks later, di Donato was -- without warning -- no longer the CEO of SUSE.  The departure was so abrupt and unplanned... that SUSE was left without a CEO over a month and a half.

At this point, things appear to be in damage control mode for SUSE -- with shareholders voting in November to de-list the company from the stock exchange and take SUSE private.  SUSE no longer being a publicly traded company will significantly reduce the requirements on what sort of information gets reported publicly... including, potentially, about specific, risky deals.

As for Melissa di Donato, she appears to have lawyered up.  When Reuters reached out to di Donato for comment... those comments were handled entirely by her attorneys.

What all of this means for the future of the world's longest running Linux company remains to be seen.

The Lunduke Journal has reached out to sources at SUSE for confirmation regarding some details of this report.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
16
What else you may like…
Videos
Podcasts
Posts
Articles
LibreOffice Developer's Hotmail Account Locked After LibreOffice Criticizes Microsoft

"Wow that looks bad," says Microsoft employee.

00:08:41
Asmongold: "Internet Real ID is Inevitable"

Elon Musk and Asmongold talk about Internet ID, Authentication tokens, & Government vs Corporate oversight.

00:20:13
IBM & Red Hat Taking DEI "Under the Radar"

Whistleblowers provide details on how IBM & Red Hat are simply renaming "Diversity" programs, as the company continues discriminatory hiring practices.

The Article:
https://lunduke.substack.com/p/ibm-taking-dei-under-the-radar

00:16:33
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

Update on the patching: Had a hiccup last night where the install of macOS Sequoia on the 2010 iMac failed. After sleeping on it, I remembered that I was never prompted to sign into a wifi network. Turns out the Sequoia installer didn’t pick up the AirPort card in this Mac so it wasn’t able to complete the installation updates. My router is too far to run a cable so I used my 2008 Snow Leopard MacBook as an Ethernet bridge using Internet sharing and reran the installer. Worked like a charm and I’m now booted into the Sequoia set up.

Pardon the messy desk. The last two days have been too busy for me to care about cleaning it up right now. In any event, I decided it was time to make the jump with that 2010 iMac. I’ll let you all know how it holds up.

I’m expecting some graphical issues due to this Mac predating Metal by several years (and I haven’t upgraded the GPU in it). I’m also curious to see if the USB and FireWire ports still work afterward. The USB may be fine as they’re USB 2.0, but there was a note on the OCLP documentation about Sequoia lacking USB 1.1 drivers under this particular model. Who knows though, the OpenCore Legacy Patcher team do some phenomenal work on getting hardware support fixed up with the newer OSes.

I suspect everybody here might already know, but for anybody interested, the kickstarter 3 for the ZX Spectrum Next is on and will end by mid August...
You can get yours here:
https://www.kickstarter.com/projects/spectrumnext/zx-spectrum-next-issue-3-0

I know is kickstarter and all that, but the ZX Next guys have already a track record of delivering twice.

post photo preview
IBM Taking DEI “Under the Radar”
Whistleblowers provide details on how IBM & Red Hat are simply renaming “Diversity” programs, as the company continues discriminatory hiring practices.

Back in April, The Lunduke Journal broke the story of IBM “ditching DEI policies” company wide — including at their subsidiary, Red Hat. This change was announced in the wake of multiple lawsuits against IBM (for their DEI policies) and executive orders against DEI from President Trump.

At the time, activist employees at Red Hat / IBM were not happy (to say the least). Encouraging and planning protests, “raising hell”, and even “killing fascists”.

But, now that a little time has passed, let’s take a look inside at IBM and see how their “ditching DEI” change is actually going.

DEI Staying “Under the Radar”

Thanks to whistleblowers within IBM, we know that employee groups focused on DEI still, in fact, exist. They are simply changing names in order to “stay under the radar” and avoid having “a target on their back”.

 

The “diversity-inclusion” corporate Slack channel, for example, is now named “inclusion-at-ibm”. They simply dropped the word “diversity”.

The DEI Department is Still There

Employees are using that IBM DEI Slack channel to clarify corporate changes to DEI policy. Which, again, thanks to whistleblowers… we have screenshots of.

A few key items:

  • The “DEI Department” has been renamed to “Inclusion” — and now reports to Kitty Chaney Reed (the Chief Leadership, Culture and Inclusion Officer).

  • IBM is no longer part of the Human Rights Campaign — “the HRC no longer align with IBM priorities”.

  • “People can still identify their preferred pronouns in all of IBM systems.”

  • The game-ified “Allyship Badge” system has been removed.

 

As we can see, some DEI policies and programs are gone, while others remain. And IBM is making a point of renaming their DEI Department within HR.

We gain these insights thanks to Ruth Davis — an IBM Executive and who currently identifies as a “DEI Advocate”.

 

These clarifications were published by a current member of the IBM HR team… who was originally hired as a “Diversity and Inclusion Intern”.

 

In short: DEI advocates continue to control IBM HR, and DEI departments continue to exist.

IBM / Red Hat Discriminatory Quotas

Up until recently, both IBM & Red Hat had discriminatory hiring policies — including sex and skin color quotas and even rewards for executives for hiring fewer white men.

We learned, as part of the original leaks supplied to The Lunduke Journal back in April, that “diversity goals are no longer part of the executive incentive program”.

 

Which begs the question, now that a few months have passed, is IBM still discriminating against White Men?

Getting hard numbers on the demographics of new IBM / Red Hat employees is not likely to happen for quite some time — if ever. But here is a picture, posted yesterday, of new Red Hat interns.

That might give us some indication of where things are heading.

 

Well. Huh.

Finding the “White Guys” in this photo of Red Hat interns isn’t quite as challenging as a round of “Where’s Waldo?”… but it’s close.

Now for me, personally, I truly don’t care what the demographic ratios are of employees & interns within a company. Hire the best people for the job, regardless of their sex or ethnicity. Meritocracy is a good thing.

That said, considering the multiple pending lawsuits against IBM and Red Hat — specifically regarding their discriminatory policies towards White Men (and their previously stated goals of hiring less of them) — it is more than a little interesting that their latest crop of Red Hat interns is almost entirely… people who are not White Men.

Results Are Mixed

There are a few good signs in here of IBM dropping DEI related policies — including no longer being involved in the Human Right Campaign and the removal of the (rather repulsive, anti-White) “Allyship Badges”.

Unfortunately, most of the rest of what we’re seeing is less encouraging.

  • “DEI” groups simply being renamed to “Inclusion” in order to stay on the right side of the law.

  • What appears to be continued discriminatory hiring at Red Hat (despite lawsuits and stated policy changes).

  • Executives and HR still heavily controlled by “DEI Advocates”.

  • Corporate systems still using “preferred pronouns”.

While making significant changes to corporate policies can take time — especially across large organizations like IBM — some of these internal reports indicate an unwillingness to drop DEI policies on the part of key IBM leadership.

The Lunduke Journal will continue keeping tabs on both IBM and Red Hat.

Any employees looking to become whistleblowers can find whistleblower resources at Lunduke.com.

Read full Article
post photo preview
LibreOffice Developer’s Hotmail Account Locked After LibreOffice Criticizes Microsoft
“Wow that looks bad,” says Microsoft employee.

Mike Kaginski, a LibreOffice developer (who works for Collabora), has had his Microsoft-hosted email account, which he uses for open source development, locked for “activity that violates our Microsoft Services Agreement”.

 

Kaginski discovered this when attempting to send an email to the LibreOffice development mailing list (hosted by FreeDesktop). It remains unclear if that specific email (which he sent via another address and was rather bland and technical) was the reason for the ban… or if attempting to send the email was simply the first time the ban was noticed by him.

This happened just days after LibreOffice officially accused Microsoft of engaging in a “Lock-in” strategy by creating “artificially complex”, XML-based office documents.

Are the two events related? Hard to say with any certainty.

To make matters worse, Kaginski has had no success in getting Microsoft to lift his locked email account — with the company making him jump through numerous, impossible hoops (such as requiring him to sign in to submit an appeal for his account being locked… but not allowing him to sign in… because his account is locked).

You got that? Sign in to fix the account you can’t sign in with.

Gotta love a good Catch-22.

Good job, Microsoft.

The Lunduke Journal reached out to a contact, within Microsoft, who made it clear that their group was not aware of the LibreOffice Developer’s locked account, but they were aware of the LibreOffice complaint article regarding “artificially complex” XML lock-in. Adding, “wow that looks bad”.

The Lunduke Journal’s Analysis

The odds of locking a LibreOffice developer’s email account being an official Microsoft corporate decision seems highly unlikely.

Microsoft, as a company, makes a lot of bad decisions — but this would just be too stupid for words. A massive PR blunder.

But could a single employee, feeling grumpy, have done it on an impulse? As some sort of revenge for LibreOffice’s “harsh” words about Microsoft? Sure. That seems entirely plausible?

Though, it’s also entirely plausible that some poorly designed AI-driven “naughty activity” detection bot flagged his account. Or, perhaps, the developer was reported by some random Open Source hooligan who likes to cause chaos (there’s a lot of those).

Either way, the fact that Microsoft requires people to log in — on accounts which cannot log in — in order to file an “appeal” is incredibly amusing. And is very, very typical Microsoft.

Read full Article
post photo preview
Open Source “Political Protest Forks” Thriving
Many called XLibre & Redot nothing more than “political protests” that would quickly die and be forgotten. Boy were those naysayers wrong.

Over the last year, we’ve seen a couple of high profile forks, of large Open Source projects, which were inspired — in part — by a desire to move away from the political discrimination and Leftist Extremism within the original projects.

At the time, when each of these forked projects were started, many predicted that they would go nowhere. That they were nothing more than “political protest forks” — and they would die out quickly.

Let’s check in on both of those project to see if that has happened.

XLibre - The Xorg Fork

Since officially launching, at the end of June (last month), the XLibre project has published a handful of official releases (now up to version 25.0.0.5)… with a significant number of changes and fixes.

 

In fact, considering the significant new features (such as XNamespace Extensions), the first release of XLibre is larger (in every way I can think to measure) than any Xorg release in the last decade. With the number of contributors growing.

How about Operating System support? Many predicted that XLibre would be ignored by every Linux distribution on the planet. That it would go nowhere and nobody would use it.

According to the “Are we XLibre yet?” wiki, a number of systems have already (officially) adopted XLibre. Including: Devuan, Artix, GhostBSD, and (my personal favorite) OpenMandriva.

 

This is important to note: All of that support has occurred even though XLibre has only existed for one month. Several systems already officially supporting it is nothing short of “crazy impressive”. Borderline unprecedented.

In addition, a number of systems have 3rd party repositories which allow users to install and use XLibre. Including: Arch, FreeBSD, Gentoo, NixOS, Slackware, and (seriously) macOS.

 

In short: Growing group of developers. Rapidly growing platform support. New releases which put the original project (Xorg) to shame.

Redot - The Godot Game Engine Fork

The Redot project — which forked off of Godot back in October of 2024 — had a stable release (4.3.1) back in June, and just had a new test release (4.4 Alpha 2). Both with both new features and fixes.

 

In fact, Redot has had 13 releases since the project started late last year.

With an absolutely massive number of commits since then.

 

In short: Steady, new releases. New features and bug fixes. Both stable and testing releases.

These Projects are Thriving

It’s hard to look at either of these projects and come to any conclusion other than they are absolutely thriving.

At this point, it’s looking like those who predicted rapid failure for these “Political Forks” were not only wrong… but wildly, obscenely wrong.

There’s a lesson in there.

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals