React got a foundation. Lovely. Now show me the charter, the voting rules, the employer cap, and the part where power stops being a vibe.

Because right now this looks a lot like moving a messy apartment into a nicer building and calling it urban renewal. The logo changed. The press release got softer. The Linux Foundation is in the room. Cool. But the thing that actually matters — who gets to decide React’s technical direction when the boardroom starts sweating — is still hiding behind a “we’ll share more in the coming months” sentence like it owes somebody money.

Here’s the official shape of the thing: React, React Native, and JSX were moved into the React Foundation, which is hosted by the Linux Foundation. There’s a board of corporate members. There’s a provisional leadership council. There is, at least for now, no public technical charter worth pointing at and saying “yes, this is governance.” That part is still in the future tense. Which is a bit rich for a project that powers a disgusting amount of the web.

And yes, foundations matter. They can pay bills, hold trademarks, maintain infrastructure, and keep one company from being the sun around which every roadmap orbits. That part is good. Necessary, even. But a foundation without a clear technical constitution is just a nicer lobby. It tells sponsors where to send the money, not contributors how power gets exercised.

That distinction is the whole damn game.

If you want a model that actually looks like governance, go peek at Node.js. It has a published TSC charter, a consensus-seeking process, and an explicit rule that no more than one-fourth of voting members can be from the same company. That doesn’t make Node perfect, obviously. Nothing run by humans and mailing lists is perfect. But it does mean the rules exist before the fight starts. That is the difference between a system and a promise.

React, meanwhile, is asking everyone to relax while the important bits remain provisional. Maybe that will be fine. Maybe the charter will arrive and be sensible and boring and everyone will move on with their lives. I hope so. But until then, “vendor-neutral” is just marketing with a nicer tie.

And I do not say that to be theatrical. I say it because I have watched too many “neutral” open source transitions turn into ceremonial theater where the sponsor still quietly owns the gravity. The board handles the money. The engineers handle the code. The company that used to own the project still supplies the people, the momentum, the institutional memory, and half the muscle. Everyone stands around saying the magic words while the actual power structure gets a fresh coat of paint.

That is not evil. It is just unfinished. But unfinished governance should not be sold like a completed moral victory.

So here is the short list of what React needs before anyone starts handing out trust like party favors:

  • a public technical charter
  • a real employer cap for voting members
  • conflict-of-interest and recusal rules
  • public voting or decision records
  • a clear way to amend the charter without turning it into a sponsor knife fight

If that sounds boring, good. Governance should be boring. It should be the least exciting part of the project. The moment it becomes dramatic, somebody has already failed to do the paperwork.

React is too important to run on “don’t worry about it, we’re working on it.” That phrase is what people say when the hard part has not been solved and the slide deck is due in twenty minutes.

So yes, congrats on the foundation. I mean that.

Now publish the constitution before the press release starts pretending it already exists.