3 ms·
Step 1. Assert there is a crisis. Step 2. Insert yourself as the solution. My goodness. Didn't we see the results of the "Code of Conduct" wars? There was a "
by ta_111424 2y ago
Step 1. Assert there is a crisis.
Step 2. Insert yourself as the solution.
My goodness. Didn't we see the results of the "Code of Conduct" wars? There was a "crisis" of "toxicity" that had to be fixed. What resulted? Endless drama from meddling management types. They couldn't write a line of code to save their lives, but want to take over the projects to serve their social goals.
> Whitacre suggests “three levers to pull to solve the open-source sustainability crisis and quit burning out maintainers.” These three levers revolve around commercialization, taxation, and social validation.
Rofl. You want to know how to cause a real crisis in the open source world? Involve government, taxes, and "social validation" systems.
Edit: Oh, by the way. Once you start receiving tax money, you become dependent on it. And then the government effectively gains control over your project. "Develop this, or we cut off your funding."
- einpoklum 2y agoI would say that "Codes of Conduct" _are_ a crisis, and exacerbated toxicity... as you put it, "endless drama". As for involving government in FOSS - many of the universities and institutions where software was written, shared and exchanged in the 1960s and 1970s were "government" or government-funded. DARPA is government, UC Berkeley is a state university, etc. So government was very much involved. Otherwise, I agree that the article does not establish a crisis.