Chrysanthemum Yellow Tenders, Author Out: The Open Source Harvesting Mechanism Behind Avalonia's HarmonyOS Port Suspension
Opening in One Sentence
On May 9, 2026, developer B announced on GitHub that his personally led open-source Avalonia port for HarmonyOS would be suspended, with developed content no longer publicly available.
Hundreds of followers were stunned in the comments. But what’s truly stunning isn’t the project’s suspension itself—it’s the precisely engineered mechanism behind it that structurally and “legally” sidelined a passionate contributor.
This isn’t an isolated case. It’s a complete specimen of open-source ecosystem arbitrage.
The Phenomenon: How a “Legal” Ecosystem Arbitrage Was Executed
First, a Primer: What is Avalonia?
Avalonia is an open-source cross-platform UI framework based on .NET. Think of it as a C# version of Flutter—it can port Windows desktop applications to other systems like Linux and macOS. Amid the domestic IT infrastructure wave, a large number of legacy Windows desktop apps in China need low-cost migration to HarmonyOS PCs / domestic Linux systems. Avalonia’s HarmonyOS adaptation thus became a critical technical gap.
Developer B started working on Avalonia’s port for OpenHarmony (open-source HarmonyOS) as an individual from late 2024. He had a day job; this was purely a passion project in his spare time, with the port code released under the MIT license.
The Five-Step “Legal” Harvesting Chain
The entire incident can be broken down into five steps, each within the rules, but each making the developer’s situation more passive:
Step 1: The Passion Phase (Late 2024 – July 2025)
B independently completed the initial port of Avalonia for HarmonyOS. At that time, HarmonyOS PC had zero buzz overseas. He was the person most familiar with this work on the planet—this “uniqueness” would later become a bargaining chip exploited in the game.
Step 2: The Pseudo-Negotiation Phase (July 2025 – End of Year)
Avalonia (the Estonian company) began official cooperation talks with Chrysanthemum Yellow. Avalonia promised that if a deal was reached, they would hire B full-time or part-time for the HarmonyOS adaptation work. B was drawn to this promise—he loved Avalonia and aspired to Avalonia’s remote work culture and team atmosphere.
So from July 2025, B pushed subsequent port code to a closed-source repository, preparing for the upcoming collaboration. It was a reasonable decision—but one that stripped him of his “open-source umbrella.”
Step 3: The Information Arbitrage Phase (Early 2026)
The collaboration ultimately fell through. Neither Chrysanthemum Yellow nor Avalonia publicly disclosed the specific reason, but an unavoidable background factor is that Avalonia’s home country, Estonia, is one of the EU nations actively pushing sanctions against Chrysanthemum Yellow. An open-source framework adaptation deal ultimately hit the reef of geopolitics.
The key is what happened next: Chrysanthemum Yellow took the information provided by Avalonia during negotiations and turned to domestic bidding platforms to solicit tenders. Multiple outsourcing companies contacted B via blogs—the project details they had were exactly the same as those Avalonia had provided to Chrysanthemum Yellow.
No one broke the law in this game; everyone played by the rules—but the rules themselves are tailor-made for big companies.
Step 4: The Outsourcing Handover Phase (Early 2026 – May)
Outsourcing companies wanted B to help them win the bid, offering him any terms he wanted. B refused—he had a job, didn’t need the money, and only wanted one thing: to join Avalonia and do what he loved.
He was unwilling to work for a domestic outsourcing company or join Chrysanthemum Yellow. This choice was legally flawless, but in the game, it meant he gave up his only chance to stay at the table.
Step 5: The Developer Exit Phase (May 8–9, 2026)
B learned that a certain outsourcing company had successfully won the bid. He immediately announced the project’s suspension and archived all code.
His logic was clear and restrained: since an outsourcing company was getting paid to do this adaptation, his continued passion-driven work became meaningless—“I can’t let a third-party company get paid without doing the work, while protecting my own rights and, in a way, Chrysanthemum Yellow’s rights.”
But everyone knows the real outcome: a developer who built a project from scratch to a working state, because he didn’t belong to any “entity qualified to bid,” was ultimately locked out by the rules.
Analysis: Why Did This Mechanism Work?
The operation of this “legal harvesting” mechanism relies on three simultaneous structural conditions:
1. Geopolitical Barrier
Avalonia is registered in Estonia, an EU nation actively pushing sanctions against Chrysanthemum Yellow. This means Chrysanthemum Yellow can hardly establish normal commercial cooperation with Avalonia—not because they don’t want to, but because regulatory risks are too high. And porting an open-source UI framework isn’t worth the massive investment in funds and legal resources to bypass this barrier.
So Chrysanthemum Yellow’s choice was: bypass Avalonia and directly find domestic outsourcing. This is business rationality, not a moral choice. But for B caught in the middle, this wall is one he cannot tear down.
2. HC Freeze: Big Companies Don’t Hire, They Outsource
B’s condition wasn’t money, but an HC—becoming an Avalonia employee dedicated to this work. Avalonia’s negotiation plan with Chrysanthemum Yellow likely included this HC requirement.
But in the current big tech environment, HCs are scarcer than budgets. A full-time employee headcount means long-term fixed costs, while an outsourcing project is just a one-time phased expense. Chrysanthemum Yellow chose the latter—this is an inevitable outcome in an environment where HCs are locked.
B didn’t want to be a temp worker for an outsourcing company. So the deal was doomed the moment the HC was locked.
3. AI Narrative: You Are No Longer Irreplaceable
The final layer, and the most unsettling one:
Why did Chrysanthemum Yellow and the outsourcing company think they could manage without B? The answer is brutally simple—because AI is here.
AI is indeed relatively good at code porting and language translation. The outsourcing company could confidently claim: even without the original author, we can deliver by starting from scratch with AI. Under the MIT license, they could use B’s code; even if not, clean-room development with AI assistance could replicate it.
Open source used to be a contributor’s gateway—you publish code in exchange for reputation and industry standing. But when AI can read all the ideas in your code, your code itself is no longer scarce. Understanding and replicating your work becomes unprecedentedly easy. So what do you have left to bargain with?
The Audience and the Cost
The “leeks” in this mechanism are open-source contributors—those who spend their spare time adapting, documenting, and fixing bugs for the ecosystem. They believe the rewards of open source are reputation, recognition, and industry opportunities. But this mechanism tells them:
Your passion-driven work is just free feasibility research for big companies before they tender.
The costs are multiple:
- Individual level: B lost the project direction he loved; hundreds of followers lost a mature HarmonyOS adaptation solution.
- Ecosystem level: Open-source contributors will realize—your open-source achievements may not belong to you, or even the community, but to the outsourcing company that wins the bid.
- Trust level: When “open source” shifts from a prelude to collaboration to a tool for arbitrage, how many will still be willing to contribute passion to the HarmonyOS ecosystem next time?
How to Identify and Avoid: A Self-Checklist for Open Source Contributors
If you’re contributing to an open-source project for a platform or big company ecosystem, ask yourself these five questions before investing significant time:
1️⃣ Is my work locked by “pseudo-negotiations”?
If you close-source your code because of an “imminent” deal, you lose the “open-source community” umbrella. The moment the deal falls through, you have neither the reputation of open source nor the benefits of closed source.
2️⃣ What is my irreplaceability based on?
Is it based on technical leadership—“only I can do this”—or on investment—“only I’m willing to spend the time”? If the former, AI might catch up within six months; if the latter, any team with a budget can match you.
3️⃣ Is there a seat for me at the table?
If the big company ultimately bypasses the framework’s official team and turns to domestic bidding—as an independent developer, are you qualified to be a bidding entity? If not, you’ll always be the one who can be “bypassed.”
4️⃣ Does the other side want your code, or you?
Outsourcing companies ask you to help them win the bid, offering any terms—but they want your code and experience, not you. Once the bid is won, your relationship with the project ends. Are you willing to be just a stepping stone?
5️⃣ If AI could replicate your past year’s work tomorrow, what would you have left?
This isn’t a sci-fi question; it’s a 2026 reality. If your value anchor is “I wrote these codes,” you lose bargaining power in the AI era. If your value anchor is “I understand this scenario, I can make decisions, I have community trust”—that’s what AI can’t take away in the short term.
Conclusion
Developer passion is the fuel of open source. But when big companies use open source for free research, use geopolitics to avoid cooperation, use HC freezes to dodge long-term investment, and use AI narratives to dissolve contributors’ irreplaceability—this combination of moves means no one is breaking the law, but the one who started with passion is legally kicked out of the game.
This is the most important case study for every open-source contributor to read carefully in the 2026 ecosystem.