Open Source Politics

Hi everyone, this is Charles Hoskinson broadcasting live from warm, sunny Colorado. Always warm, always sunny—sometimes Colorado. Today, we learned something: open source is hard. Why? Because while we like to believe it’s just a GitHub repo and code, it turns out there are human beings behind the keyboard.

I opened up my Twitter this morning and immediately saw this big storm where Matias Ben Court said he’s been banished from Ain. Then Lucas comes in and says they call us fascists and they hate everything, and there’s this war here. I didn’t know anything about it, and I thought, “Oh God, why are we doing this?” In a broader sense, one of the core utilities of a member-based organization—whether it be the Linux Foundation, the Apache Foundation, or the Open Core Foundation—is managing the social physics. The technology is easy; at the end of the day, it’s GitHub, it’s Git projects.

You have a little Git project, and people say, “This sounds a real good idea; let’s go do that.” But then people get involved, and they have political views. Let me show you something to illustrate how surprisingly common this can be. I asked Perplexity to make a list of open source contributors kicked out because of their politics. The Russian Linux kernel maintainers were removed by the Linux Foundation to comply with U.

S. sanctions following geopolitical tensions. That’s unfortunate because many of those were OGs of OGs, and Linux is Linux, right? Then there were GitHub suspensions. The big one was Eric Raymond, who is a hero of mine.

He wrote the lovely book "The Cathedral and the Bazaar," one of the first books I ever read on open source. He was kicked out for troublesome behavior that undermined the organization’s goals because he opposed the OSI diversity initiative. There was also Seth Vargo and Chef for its contracts with OpenAI, and Dean Dobot, a developer. If you dig a little deeper, you’ll find that there are probably hundreds of cases, and not all of them are well politicized. The reality is that people have very different politics at times.

Some people are hardcore alt-right extremists, while others are hardcore communists. Some people really believe in one thing. In fact, when I was growing up in the Bitcoin days, there was a guy named Luke Dash Jr. who made Bitcoin blocks and created a bit of controversy because he always embedded Bible verses inside those blocks. He has a very unique worldview, and we all loved him.

I never have a problem with people’s politics, and I enjoy working with people who are quite diverse. People who have worked with me throughout the ages will know that’s always been the case. We didn’t start Ain; it was an open-source project, and people came together to work on it. Like all social interactions, people come from different backgrounds, and if they don’t have the right structure in place, the things that divide them can become wedge issues, and they can split apart. It looks a wedge issue occurred here because the macro became the micro.

It can seem pretty horizontal: it’s just this project, and people work on it. One of the core maintainers likes me, and another one doesn’t. They say, “Oh, well, because Charles is doing stuff with Trump, or is perceived to be doing that, he’s a fascist and an evil person.” The other person says, “I like that stuff,” and they split. The solution is for them to talk to each other.

My understanding is that Lucas and Matias are going to talk it out. Hopefully, they can come back together and figure it out. The broader, longer-term solution is to recognize that you need to have member-based organizations because they have the structure in place to ensure that everybody has the right to be heard. Recently, I saw some budget proposals where they said we don’t need any bureaucracy, don’t give any money to Intersect, don’t give any money to any of these NBOs; it’s a waste of money. The whole reason they exist is to prevent these types of things from happening.

You have two tremendously talented people who are geniuses; they do amazing work and are incredibly passionate. They’ve proven their passion about Cardano, but they have opposing worldviews and opinions about people. The whole point of an NBO is to create the infrastructure so these types of people can work together productively and effectively. Those opposing views don’t do that in the absence of it. When you have these small horizontal structures, over time, they become like sandpaper and create friction.

We’ve seen this throughout the years. In fact, the history of Haskell, the programming language, dates back to 1985. It came out because the original language that everybody wanted to use was called Miranda, and the person who created it didn’t want to release the intellectual property. They wanted to try to make money on it, but people were like rebels and said, “Screw you, man, we’re going to create our own language.” They formed the Haskell working group, and that’s where Haskell came from.

When Oracle bought Sun, it led to the creation of PostgreSQL. You notice we have a lot of forked projects floating out there. Sometimes these are commercial; sometimes they’re due to geopolitical sanctions. For example, in Brazil, this led to the creation of the Lua programming language. The same thing happened in certain respects in South Africa during apartheid.

Geopolitics, political views, and personal opinions—that’s what makes open source hard. We have just seen a case study on why open source organizations exist. For my part, I always err on the side of collaboration, and I think that these two will find a way to work it out and come back together. This is a teachable moment for everybody because it allows us to reset and reevaluate that collaboration is hard. This is another reason why Cardano is one of the most valuable cryptocurrency projects in the world.

We focused on the governance and collaboration side first and created one of the most complex and useful governance layers of any cryptocurrency, with lots of checks and balances. If you solve governance, tech is easy, and you can make forward progress and get things done. That’s why we invested so much time, effort, and money as an ecosystem, and that’s why we have decentralized governance now and why we have constitutional committee members. Every now and then, people come and say, “Hey, kids, cut it out.” I understand you’re passionate; let it go and come back together because you both care.

I’d like to believe that they do, and I think this will probably get resolved today, one way or the other, and people will move on. Moving forward, let this be a teachable moment that governance matters. This happens all the time in open source. It’s unfortunate, but that’s what makes life fun. You can’t say you like diversity; you can’t say you like different cultures and viewpoints without admitting that by embracing that, you are also embracing the occasional conflict and debate.

The key is to disagree without being disagreeable. The key is to come back together when you realize you’re too far apart. At the end of the day, the things that connect us are a lot closer than the things that divide us. That’s all I’ll say on this, and welcome to decentralization. It’s a fun thing.

Thanks, everyone.