You are a senior executive at Adobe.

The CEO of Adobe summons you in his office.

You are in charge of creating a secret task force. The goal is to systematically undermine open source software such as Krita, Inkscape, Kdenlive or GIMP. You have a $50 million budget. Nobody in the company knows about this project except you and Adobe’s CEO.

What would you do?
Buy the platforms open source projects use and…Wait a minute, MS already did this.
With the advent of AI open source is no longer a threat. Now it is just training data.
I would start a bunch of supply chain attacks to erode the trust and drown them in ai generated “contributions” to make maintainers tired.
become a whisleblower, expose them?
Dropping all of that budget to art universities to have them teach Adobe software primarily. Inkscape, Kdenlive and GIMP do not have the funds to compete in this way, and once people learn a software to do their job, it becomes really hard to switch. Sure, enthausists can learn other open software, that’s not my target audience. My target audience is the one that uses such software to earn their money, and most of them will pursue higher education before doing so to learn their tools better, and Adobe will make that money back really easily with their subscription plans.
That’s why Apple used to give computers to schools (plus tax write-offs). Every school, and most classrooms, had Apple ][ computers in the 80’s.
Despite answering almost the inverse of the question, this is the correct answer
You can spend infinite money undermining infinite competitors but software companies live and die on industries and professionals being entrenched in their ecosystem
Spam poor quality llm commits from sockpuppet accounts to a bunch of popular projects. Sprinkle in some subtly-buggy contributions from more established accounts. The buggy contributions should not be obviously malicious (not, like, obfuscated credit stealers – they should just break things). Do this to as many projects as you can without making it super obvious. Prefer projects with few maintainers but a high merge rate. Then, go think about what you did, you bastard.
This is what I came to say. If you want to undermine open source software, you undermine the maintainers who hold it all together. Swamp them in pull requests, some that are genuine, some with subtle bugs, some that are nonsense. Also try to start flame wars and circulate unsavory rumours about them, claim they are sexist, ableist, racist, or that they are trying to capture the software fir big business, or anything else that might drive a wedge between them and their community. Ideally, drive them out of OSS entirely and encourage a large enough portion of their audience to switch to a fork you maintain through a sock puppet account. At that point you control the software, regardless of the OSS tag on it, and can go about degrading it slowly.
Pay a bunch of simps to make posts all over about how they tried switching to linux and/or GIMP but it was too hard and broke all the time, claiming that open source is “just a hobby.”
Nice try adobe.
I’d embezzle a bunch of the money, then spend the rest on good-faith contributions to the software in question, insisting that this was just stage 1 of the plan. There is no stage 2.
I can’t say you understood the assignment, but I can say you are good people. I mean… kinda. Embezzlement is a bit sketch.
Embezzlement is a bit sketch
Embezzlement from billion dollar corporations is a moral duty whenever the opportunity presents itself, so long as that embezzled money gets redistributed appropriately, Robin-Hood style.
I would submit code I wrote to it
I think the best strategy is to contribute lots of money and work to promoting and developing free software, improving it and using it everywhere so that it comes to be ubiquitous, used by everyone. That will make it even more of a target for malware authors and therefore lead to its sure demise. We should get started right away.
Fork it, carry on with being FOSS for now, develop a few killer features that everyone will love that would take a small FOSS team years to develop. When it becomes the industry standard, make it closed source. A year later start charging for it.
get open source fans on the internet to endlessly discuss and fight amongst each other.
I know, totally unrealistic. would actually never happen, that’s ridiculous.
Clone every repository, start inserting bugs and viruses, then take the open source code and encrypt/obfuscate it and make minor changes
Then release it as a closed source product and have a spin doctor like Steve Jobs tell people mine is better and there are no viruses or bugs so they should switch.
That’s the standard playbook, if it works it ain’t broke so don’t fix it.
Delete all of my internal databases. Necessity is the mother of invention, so starting at a disadvantage would be a catalyst to churn out even better software!
Delete your own databases, the AI method of software development?
I would take a movement whose mission is user freedom and whose arguments relate to morality and twist it so that the only thing that matters is software quality. Now, it’s palatable to corporations.







