Lunduke
News • Science & Tech
Mozilla Sued for Discrimination by Former CEO-To-Be
The story this lawsuit tells is a Game of Thrones style power struggle.
June 18, 2024
post photo preview

The Lunduke Journal has obtained the legal documents regarding a new lawsuit which has been filed against Mozilla, makers of Firefox, by a former C-Level executive.

And parts of it read like a Game of Thrones style power struggle within the browser maker.

  • The Mozilla Chief Product Officer was being groomed to take over as the new CEO.
  • That CEO-to-be took some medical leave to treat cancer.
  • In the days (literally) before the CEO-to-be returns from medical leave... the then-serving CEO of Mozilla, Mitchell Baker was fired -- by the Mozilla Board -- abruptly.  No warning.
  • The Mozilla Board of Directors then installed one of their own Board Members, Laura Chambers, as the new CEO.
  • All before that "CEO-to-be" could return to work, from his medical leave, and take over the CEO position.

There is a lot here -- including a tale of discrimination and abuse inside the Mozilla Corporation.

Below are screenshots of large portions of this lawsuit -- the items of particular interest to tell this story -- with each screenshot followed by a brief description and some additional details.  (If you're short on time, just read the descriptions between each screenshot... that will give you a high level overview of this story.)

 

Lawsuit: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

The lawsuit was filed by Steve Teixeria (the former Chief Product Officer of Mozilla), against Mozilla Corporation, in King County, Washington (Seattle), on June 12th, 2024.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Teixeira, the new Chief Product Officer (CPO) of Mozilla was brought on board in 2022 and was being groomed to become the new CEO (to replace Mitchell Baker).  This appeared to be the plan from Baker and at least one Mozilla Board Member.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

As CPO, Teixeira led roughly 75% of the employees of Mozilla, and oversaw the "entire commercial product portfolio".

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Firefox is reaffirmed to be roughly 90% of Mozilla's revenue.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

As CPO, Teixeira, was given high performance reviews.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Mozilla opened an entire office branch -- in Seattle, WA -- to accommodate Teixeira.  Which would make sense if the plan was to make Teixeira the new CEO.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Through September of 2023, the plan remained to transition Teixeira to become the CEO of Mozilla.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Teixeira was diagnosed with cancer (ocular melanoma) in October of 2023.  He then took leave (under the Family Medical Leave Act) until February of 2024.  Mitchell Baker remained CEO during that time... until the days before Teixeira returned to work.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Mozilla publicly announced their new CEO, Laura Chambers, on February 8th, 2024.

According to this legal filing, that decision was made (by the Mozilla Board), internally, roughly a week prior.  This would be "shortly before Mr. Teixeira" returned from leave on February 1st, 2024.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

This legal filing appears to say that Mitchell Baker was fired, by the Mozilla Board of Directors -- from her role as the CEO of Mozilla due to her "declining performance".

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

The timing here is interesting.

According to the legal filing, the firing of Mitchell Baker as Mozilla CEO was "so abrupt that they did not conduct a search for a successor".

Meaning: They were in a hurry.  For whatever reason, the Mozilla Board needed to act right then.

And the Mozilla Board -- which included Laura Chambers -- voted to install Laura Chambers as the new CEO.

All of this happened the very moment the person who was being groomed to take over as CEO, Teixeira, returned from his medical leave -- and was set to resume overseeing roughly 75% of Mozilla.

Was this the motivation for moving so quickly to install a new CEO?  To do so prior to Teixeira returning and taking over?

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

The first day back as CPO, Teixeira was instructed to lay off 50 (already selected) employees.  He had questions about who had been selected to be laid off.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Teixeira's employees were "explicitly forbidden", by the "Chief People Officer" of Mozilla (Dani Chehak), from briefing and assisting Teixeira as he returned from leave.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Teixeira expressed concerns, with Human Resources at Mozilla, that these layoffs would "disproportionately impact" "female leaders" and "persons of color".

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Teixeira was threatened, by the Chief People Officer (Chehak) to be forcibly placed "back on medical leave" if he "did not execute the layoffs as instructed".

Do what we say, fire these exact people, and don't talk to anyone about it.  Or get out.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

The new CEO, Laura Chambers, and the Chief People Officer, Chehak, insisted that Teixeira not only announce the layoffs... but falsely take responsibility for the layoff decision-making.

According to this document, Laura Chambers was throwing the person that was being groomed to be the CEO under the bus.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Teixeira was "permitted only to speak with the CEO and her direct reports".  His staff -- roughly 75% of Mozilla - was delayed being moved back under his leadership.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

There was an "outside audit" done of Mozilla's performance in "providing a diverse, equitable, and inclusive workplace culture" by Tiangay Kemokai Law, P.C..

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

According to that outside report, Mozilla's leadership provides an "inadequate response to the needs of a diverse culture" and is "incongruent with [Mozilla's] stated values and goals."

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Teixeira's former direct reports expressed, to him, "deep concerns" about leadership in his absence.  Specifically regarding "abrupt changes to strategy" and "inappropriate or abusive interactions" from the Senior VP of Strategy Operations (Suba Vasudevan) and the Chief Marketing Officer (Lindsey O'Brien).

This included complaints made to Human Resources regarding the Chief Marketing Officer.

What those complaints were, we do not know.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

The new CEO, Laura Chambers, hired a consultant to assume Teixeira's core responsibilities after Teixeira returned from medical leave.

Teixeira then received, from the newly installed CEO, his first negative performance review.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Teixeira -- once groomed to be the new CEO -- now was being forced to move into a new role. Which he did not want or ask for.

At this time he was able to work full time and did not request time off for medical care.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Teixeira's family believed that Mozilla was gathering his publicly available medical information, to be used against him in his employment.  His family then begins to remove public information regarding his medical status.

Teixeira disclosed to the new CEO (Laura Chambers) that liver cancer had been detected.

That information was then shared -- according to other statements within the lawsuit, by Laura Chambers -- with all of her direct reports.  

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Mozilla then makes it clear they wished to demote Teixeira (from a C-level executive down to a Vice President role).

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Teixeira declined the demotion (which would come with a 40% pay cut and the job would end, entirely, at the end of the year).

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Mozilla's CEO, Laura Chambers, then disclosed significant, private details of Teixeira's medical conditions to other Mozilla employees.  Without Teixeira's consent.

Chambers also told other Mozilla employees that Teixeira would be demoted (the demotion that he had just rejected).

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

A key note here: Teixeira had "not requested additional flexibility related to his disability."

On April 25th, Teixeira made a complaint, in writing, that he had been discriminated against because of his cancer.  Two days later, on April 27th, the CEO (Laura Chambers), "retaliated against Mr. Teixeira" by telling him, in a nutshell, to "take the demotion or you're fired."

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Mozilla, over the next couple days, began panicking -- instructing Teixeira not to discuss anything related to his employment with Mozilla... with anyone.  Even going so far as to draft up a new "non-disparagement and non-disclosure" document with new restrictions.

By the next week Teixeir was placed on "administrative leave".  His direct reports all reassigned to other executives.  His chief of staff fired.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Mozilla refused to provide a reason for these actions.

Mozilla then cut off Teixeira's access to all Mozilla systems (including email and messaging) -- and instructed Mozilla employees to "not communicate with Mr. Teixeira."

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

A few weeks later an "investigation" was launched into Teixeira's discrimination allegations.  However Teixeira was never contacted to participate in the investigation.  Which is strange, to say the least.

Normally an "investigation" involves all parties involved.

It would be very interesting to see the full results of that "investigation".

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Mozilla continued to falsely state that Teixeira was on "medical leave", and provided Teixeira's medical details to other employees without his consent.

Which, if true, means Mozilla is likely going to be anxious to settle this lawsuit out of court.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

This resulted in multiple Mozilla employees being led to believe that Teixeira "would pass away imminently" -- which, obviously, would be pretty distressing for both the remaining Mozilla employees and Teixeira and his family.

 

Source: Steve Teixeira vs Mozilla Corporation (et al), June 12th, 2024

 

Based on the details of this lawsuit -- should the details all prove accurate -- it certainly doesn't paint Mozilla in a good light.

  • A CEO ousted -- abruptly -- in the moments before a "New CEO-To-Be" returned to work and could take over?
  • The Mozilla Board acting with lightning speed to install one of their own into the CEO position?
  • Silencing.  Scapegoating.  Discrimination.  Abuse.

Raises many, many questions about what has been going on within Mozilla... and how specific individuals rose to power within the organization.

This document, of course, is merely one side of the story.

Should this case move to trial, we would hear Mozilla's side of the story.  That, however, seems unlikely... as these sorts of cases -- especially when they appear this strong -- tend to be settled pre-trial.

The Lunduke Journal has reached out to to both Mozilla and Teixeira for comment.  As this is an ongoing lawsuit -- and Mozilla has a strong track record of silence and secrecy -- no response is expected.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
24
What else you may like…
Videos
Podcasts
Posts
Articles
Linux Logos on Racecars

The Omarchy Linux logo is on a Le Mans racecar, driven by the project founder.

Grab a discounted Lifetime Sub & get on the Wall:
https://lunduke.substack.com/p/behold-the-win-2k-and-mac-system

More from The Lunduke Journal:
https://lunduke.com/

00:07:41
XLibre Turns One Year Old

"XLibre is the most actively developed community-maintained X11 display server."

Grab a discounted Lifetime Sub & get on the Wall:
https://lunduke.substack.com/p/behold-the-win-2k-and-mac-system

More from The Lunduke Journal:
https://lunduke.com/

00:13:48
Win2K & Mac System 1 Walls!

Supporters of The Lunduke Journal have now filled up 8 retro computer themed walls!

Grab a discounted Lifetime Sub & get on the Wall:
https://lunduke.substack.com/p/behold-the-win-2k-and-mac-system

More from The Lunduke Journal:
https://lunduke.com/

00:10:02
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

That was the most boring WWDC keynote I’ve ever seen.

Repromising the things they sold me for my iPhone 2 years ago and never delivered.

I’m an Apple fan, I have LOTS of Apple products. Other than the AirPods Max, every Apple product I own will be replaced by another one someday.

I can only hope they told the truth that they were fixing bugs and focusing on performance improvements instead of lots of new features for MacOS.

I like AI - and all their AI features except the reperspective on the photo were late, meh or invented by Google.

I’ll use AI in all my Apple products, like I already am…from OpenAI, Anthropic, Grok and Gemini.

Oh, voice short cuts also looked cool.

Apple must not be allowing their employees the use of AI software development

22 hours ago

In Search of Vulnerabilities

How real is the threat of AI to OSS? How powerful is AI in doing code and security reviews? I already regularly benefit from AI code and security review of my own work. It’s not even a close call, it is OBVIOUSLY powerful and helpful. But what about all that AI Slop PR’s that are plaguing OSS?

So I picked an OSS that is popular, currently maintained and isn’t “millions and millions” of lines of code. It’s a web server, and that’s all I’m going to say about which project. It’s written in C. I’m not a C developer of any kind. I’m not a security expert of any kind. I’ve never hacked into anything in my life - I’m not a hacker of any kind.

But I have a subscription to ChatGPT/Codex.

I pull down the code and have Codex do a review with Gpt 5.5 high. Code and security review, and explicitly told it to ignore anything trivial. I’m looking for zero days and other “we must fix this now!” issues. The code passed review with no major issues...

June 07, 2026

Not Tested by AI is Inexcusable

Let’s say, as a given, that you can write better code than AI. This isn’t the current debate. You are good, you know you are good. You may have even experimented with AI for coding and have determined it does not pass your muster. All good.

If you aren’t incorporating AI in your testing at this point, I’d say you are being negligent. It doesn’t matter if you are great at coding, nobody who codes loves testing. And if you think your peers are doing a rigorous job in code review - you are naïve.

And if you are a great tester and work for a company where the testers are amazing…time is money. The FIRST line of testing should be automated with AI code and security review.

No developer should be foisting the work of finding his obvious bugs onto humans. He should have complete testing and security coverage that he runs himself - as first step.

Not last step. The ultimate quality gate is the human. But solving all the easy bug and security finding by tools ...

post photo preview
Behold! The "Win 2K" & "Mac System 1" Lifetime Sub Walls!

Woah! The 8th Lifetime Subscriber Wall of The Lunduke Journal (aka “The Windows 1.0 Wall”) is already full! After only one week! That’s nuts!

So I’m opening up two new, retro computer walls!

  • Wall 9 - “The Macintosh System 1 Wall”

  • Wall 10 - “The Windows 2000 Wall”

 

Show your support for The Lunduke Journal, and be immortalized in a retro computer screenshot. Win-win!

If the past is any indicator, these will fill up crazy fast. First come, first served.

Plus: For the entire month of June, Lifetime Subscriptions are discounted down to $125 (regularly $300).

  1. Scroll down and grab a new Lifetime Subscription (at that bonkers discount).

  2. Choose which of the two new Walls you’d like to be on (Mac System 1 or Windows 2000). Totally optional.

How to Grab a Discounted Lifetime Subscription:

There are 3 different ways to pick up a Lunduke Journal Lifetime sub. All of them work great and include the same perks. Choose whichever works best for you!

Get a Lifetime Subscription via Locals:

  1. Go to Lunduke.Locals.com/support.

  2. Select “Give Once“.

  3. Enter “125“ into the amount field.

  4. After checking out, Lunduke will toss you an email once your account is set to full lifetime status. (This usually happens within a few hours.)

Get a Lifetime Subscription via Substack:

  1. Go to Lunduke.Substack.com/subscribe.

  2. Select the “Lifetime Subscription” option.

  3. After checking out, Lunduke will toss you an email once your account is set to full lifetime status. (This usually happens within a few hours.)

If you would also like full, Lifetime access to Lunduke.Locals.com (which is included):

  1. Make a free account on Lunduke.Locals.com.

  2. Email “bryan at lunduke.com” with the email address you use on both Substack and Locals (can be different email addresses).

  3. Lunduke will toss you an email once your account is set to full lifetime status on Locals.

Get a Lifetime Subscription with Bitcoin:

Bonus: Save an extra $10 with the Bitcoin option, as Bitcoin processing has fewer fees associated with it.

bc1qyjakve8fywm8pz2v99v57yhjj0vzr2vjze6fcq

  • Email “bryan at lunduke.com” with the following information: What time you made the transaction, how much was sent (in Bitcoin), and the email address you use (or plan to use) on Locals.com or Substack.com.

-Lunduke

Read full Article
Windows 1.0 Wall almost full! Last call!

Holy Guacamole, Batman!

The 8th Lifetime Subscriber Wall (“The Windows 1.0 Wall”) of The Lunduke Journal launched exactly one week ago… and it’s already almost full! Bonkers!

 

At the current rate, the “Windows 1.0 Wall” will be full sometime tomorrow (Saturday).

Want your name immortalized in that glorious 1985 styled goodness, proclaiming to the world your support of The Lunduke Journal?

Don’t have a Lifetime Subscription?

  1. Grab one for $125 (normally $300).

  2. You’ll get a confirmation email (within just a few hours). Reply to that email with how you would like your name displayed on a Lifetime Wall.

  3. Then enjoy the other perks of being Lunduke Journal subscriber. Forum access, MP4 downloads, and PDF eBooks.

Already have a Lifetime Subscription?

  1. Just toss an email to bryan [at] lunduke.com with how you would like your name displayed on a Lifetime Wall.

Easy peasy.

First come, first served. Once the “Windows 1.0 Wall” is full, the final version will be added to Lunduke.com and the 9th Lifetime Wall will debut!

-Lunduke

Read full Article
The "Windows 1.0" Lunduke Lifetime Wall is here!

Two awesome tidbits:

  1. The 7th Lifetime Subscriber Wall (aka “The Solaris Wall”) is full! No room for any more names! You can see the final version on the bottom of Lunduke.com (and at the end of new shows).

  2. The 8th Lifetime Wall will make its debut on Monday! The retro computing platform chosen for Wall number 8 will be… Windows 1.0!

If you would like to see your name immortalized in a screenshot of the very first version of Windows, from 1985, displayed on both Lunduke.com & at the end of all Lunduke Journal shows (you know you do):

Support the Lunduke Journal… and, at the same time, have your name immortalized in a screenshot of the operating system with (arguably) the worst color scheme in human history.

It’s a win-win.

 

-Lunduke

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