Pod Insights a16z Podcast a16z Podcast | The Changing Culture of Open Source About this episode The culture of open source has changed across generations, from previous ones that had to fight for the brave new way -- to the current "GitHub generation" that not only accepts open source, but expects it as the default. Which makes sense given that open source powers so much of the software world today... and by the way, that's not just tech companies but hospitals and banks; it touches everyone.
Open source culture has also moved away from cults of personality and top-down models to drive the vision for open source projects, to decentralized individual contributor identities and more micro-sized projects within projects. So what does that mean for the governance of open source, whether it's by institution or foundation, or a "healthy" or "popular" project? Should we invert, always invert to make sure open source code "lands" and is committed by default -- as opposed to going through a cabal of gatekeepers first?
This episode of the a16z Podcast -- featuring Nadia Eghbal (who formerly researched the sustainability of open source projects for Ford Foundation, and is now in community programs at GitHub) and Mikeal Rogers (community manager and more at Node.js Foundation) in conversation with Sonal Chokshi -- covers all this and more. Is open source simply too loaded a term? Is there no sense of ownership? How best to manage a project or resolve conflicts? After all, at the end of the day, it's about people, not just code...
Transcript Speaker names marked ? are inferred from speaking time and the show’s known hosts — they are not voice-verified.
0:00 Speaker 00 The content here is for informational purposes only, should not be taken as legal, business, tax, or investment advice, or be used to evaluate any investment or security, and is not directed at any investors or potential investors in any A16Z fund. For more details, please see A16Z.com/disclosures.
0:19 Sonal? Hi, everyone. Welcome to the A16Z Podcast. I'm Sonal. Today, we're continuing our series on the theme of open versus closed by focusing on the topic of open source communities, and more specifically, the changing culture of open source across generations and governance models to access and identity and identity politics. Should there be a sense of ownership in open source? What's healthy? What's not? Do we need to get religion or have a culture of personality in order to drive vision? What happens to projects that evolved out of big companies and universities? Joining us to have this discussion, we have Nadia Ikbal, who did research for the Ford Foundation on the sustainability of open source projects before going to GitHub to focus on community programs there. And then we have Michael Rogers, who's been a contributor to various open source projects
1:02 Sonal? for over a decade and currently manages community and much more for the Node.js Foundation. And just for quick context, Node.js is a platform built on Chrome's JavaScript runtime for building fast and scalable network applications. And its package manager, NPM, is the largest ecosystem of open source libraries in the world. So we talk about open source a lot on this podcast in so many different ways, in the context of infrastructure, pricing, trends. I just kind of want to break it down, starting from the basics, for the culture of open source. And maybe we can start with, you know, why you got into open source in the first place?
1:34 Speaker 02 Wow. So I think I got involved because when I was really young, how I got involved in computers was through the hacker scene. And one of the things that really kept me there was that there were like people to talk to, and there was a community angle to it. And so when I started to work in like the actual industry, I was kind of searching for that continued community, and that ended up being the open source community.
1:53 Sonal? Why is the community aspect so important to you? It sounds like so obvious, but why?
1:57 Speaker 02 We're in an industry where people are in a job for like a year to three years. The relationships, the personal relationships they have tend to stretch decades. And so, community is kind of important to everybody. But in the open source world, it's just a lot more defined. The community is like literally the only thing holding these people together, even at the time that they're doing the work. They don't all work for the same company.
2:14 Sonal? Right, so there's a certain portability in that because regardless of what job you take, you sort of take it along with you. Nadia, what brought you to the open source world?
2:22 Speaker 03 So, I mean, the way I first discovered what open source even was was someone learning to code, maybe like four, four years ago. And I remember having this moment at a Rails bridge workshop where you get your Rails app up and running for the first time and typing in like, you know, three words. And all of a sudden, like, all these magical things happened behind the scene that I didn't know about. And I was like, where did all this come from? How did I create this app by not really typing that much? It was pure magic to me and that was the part where I was like, huh, I wonder who is actually building all this stuff in the backend to like, allow me to have that experience?
2:52 Sonal? It's actually very democratizing that when you have all these people building that it allows you to literally write a few lines of code and then have this app up and running.
2:59 Speaker 03 Yeah, and the part that I think I've always been excited by is the human part behind it of like, who made all this stuff and where does it come from? And why are they providing it to me for free?
3:08 Sonal? I'm glad you brought up that you, the human part of it because I have, I feel like there's a tendency when we talk about open source and code to sort of mechanize it. And to me, like, the arc of this podcast is about the human aspect of open source. Because essentially, you're working on code and then you have human beings, personalities, clashing and coming together while working on this through these various open source communities. So, go back to just even the nature of the fork you led. And by the way, you just told me today that you merged it back in now. Like, what was the story behind that?
3:37 Speaker 02 This was the I O J S fork of Node. The main difference was that there wasn't a technical disagreement. A lot of these other forks, like Ethereum and whatnot, there's a technical disagreement that essentially is not really reconcilable a lot of the time. For us, we were actually kind of hitting a lot of the problems that actually Nadia's research calls out, where the sustainability of the project was in question. We had tons of users. I mean, the users of Node J S are still doubling every year, but the number of people working on it had gone down. And
4:04 Sonal? So sorry, so the users are the ones who are just using the product that people are actually maintaining
4:09 Speaker 02 Just consuming it, yeah.
4:09 Sonal? And creating new code. Okay.
4:11 Speaker 02 But contributors had dropped down to, depending on how you're counting, maybe three people were actually like working on it from a high of, you know, something like seven. So it was never really that high. And the, the community around JS, the people that had built modules on top of it, we'd actually done a lot of experiments in how do you grow sustainable contributors over time in, in this new GitHub kind of ecosystem. So we had some, some really good reference material and some, some strong opinions about how to do this. Also, some of the people that had been contributing to Node for a long time were unhappy with the way the joint was running it at that time, had some disagreements. And so we, we took those disagreements and said, okay, we're going to fork the project under a different kind of contribution model where we get people more involved. Because it wasn't a technical disagreement,
4:52 Speaker 02 later, Joint put Node into a foundation. They needed kind of an open governance plan. We were able to merge the project back together.
4:58 Sonal? So you put it into the Linux Foundation?
4:59 Speaker 02 The Node Foundation is an independent foundation. The, the Linux Foundation is essentially hired to run it, to, to, to administrate it. And so it is a Linux Foundation collaborative project. But Joint had brought Node in and created this foundation around it. We brought kind of a governance model and a lot of the contributors and we were able to merge all that together. And so, I mean, at the point that we, you know, that we had this disagreement, we were down to, you know, maybe a high of seven committers. Today, about a year and a half later, we have 90 committers.
5:28 Sonal? Wow, that's amazing. So the reason for that, you believe, is because you changed the governance model of it?
5:34 Speaker 02 We started thinking about contributing to the project differently. I mean, so for instance, that 90, that's just a core itself. If you, if you look at the website and localizations and everything else, we actually have like over 400 people that have commit rights.
5:46 Sonal? That's amazing. So this ties so much into your research and thinking about sustaining open source communities. First of all, why does it even matter? Because honestly, as a consumer, as a user, I don't care as long as I have a product. So why do I care if there's three people working on it or 400?
5:58 Speaker 03 Everything is great while it works, and when it doesn't, then suddenly it doesn't. And there are a lot of people who use open source products who then are trying to ask, hey, like, can we get this type of feature in? Or like, this isn't really working. And if you don't hear feedback because nobody's maintaining it, then you have a problem. It would be as though there was like, A bunch of volunteers working on Facebook or something. And it's like, well, I really hope Facebook works because.
6:20 Sonal? There's only like 10 volunteers working on it. That's a good analogy.
6:23 Speaker 02 I think that there is like a somewhat laissez faire reaction. It's like, well, if people don't work on it, then people don't care about it. And then it'll just go away. And, and what Nadia has found and actually like demonstrated with real data is that there, there really is no connection between the number of users and the number of people actually maintaining a project.
6:40 Sonal? Let's pause on that for a moment. There's no connection between the number of users and the number of people maintaining a project. Why, what's the significance of that?
6:47 Speaker 02 So if a project goes into a state of disrepair, that doesn't mean that people stop using it. And in fact, I mean, like Heartbleed is like the best example of this, where you have, I mean, basically nobody working on open SSL, or maybe like a couple of people that aren't even paid full time to work on it. And, you know, the majority of the internet depending on it.
7:04 Speaker 03 Yeah, and not just software, but like hospitals and banks and stuff that are using it. And like you have two people that are working on it, it doesn't make any sense.
7:10 Sonal? Right. So what are some of the other interesting things your research in sustainability of open sources has, has found?
7:15 Speaker 03 Some of it has just been around, like trying to put vocabulary to what is going on. So about, you know, how you can have someone, people using this project, tons of people using the project, and not that many people maintaining it. We need vocabulary to actually explain those two different things, right? Because right now, I think a lot of people talk about projects as big or small, and big doesn't really explain what it means for a project to be big. So I've tried using terms like popular versus healthy.
7:39 Sonal? Tell me about popular versus healthy. Why does that distinction matter so much?
7:42 Speaker 03 So popular can refer to like lots of people are using the project. And healthy might mean is the community behind it, or the governance, or like how many people are maintaining it? I guess the, the backend part of the project is that in a good state. So you can have projects like open SSL might be a project that was really, really popular. Lots of people use it, but not actually healthy. Until we separate those things out, then you have the problem of people saying, well, if it's, you know, if no one's maintaining it, then it's clearly not a, not a great project. It's like, no, that's just two different metrics, right? And we have to look at one and the other separately.
8:12 Sonal? I mean, it strikes me that you can use the analogy of an organism to describe the community, like a human body or any other organism, and that you can have like this ecosystem of all these different parts and players. And then if you're healthy, you're functioning well. And if you're popular, you're like working really hard. But it doesn't necessarily mean that you're in good shape. And that has all kinds of implications.
8:30 Speaker 03 Right.
8:31 Sonal? That's super interesting.
8:32 Speaker 02 One thing that I found interesting is because the, the dialogue tends to be set by. Popular projects.
8:38 Sonal? Uh huh.
8:39 Speaker 02 And those developers and their problems tend to dominate the story about this. You have these words and vocabulary like drive-by contributions, right?
8:46 Sonal? Oh, right. Like these drive-by contributors.
8:49 Speaker 02 Like these assholes just keep showing up and giving us code. Like, don't they understand that I'm too busy to look at their code? This is crazy, right? But that is like a lot of the dialogue around it. Whereas like, you know, thinking of them as casual contributors and people that like show up and have value to add. And like, really what you need to figure out is how do you capture that value? How do you encourage it? How do you level people up? How do you, you know, retain people?
9:10 Sonal? So it's not a drive-by, but it's actually ephemeral and not so...
9:13 Speaker 02 It's an opportunity and it does have value. And the real problem is that like, you don't have enough people that are maintaining it. And one of the reasons they don't have enough people maintaining it is because you're not leveling up any of these people that come by.
9:24 Sonal? That actually reminds me of some of the intergenerational problems in getting through the open source communities. I mean, when I think about the early days of like how, I mean, Jim Zemlin has described to me like, you know, the existence of the foundation, the evolution of the foundation. It kind of blew my mind that you have Linus Turwolds and then you have like this entire foundation of people. So it's not just a cult of personality. And then you have this sort of old world of open source and new world of open source, which is probably not a good way of describing it. But Michael, you're actually the person who brought that to my awareness when we did an op-ed years ago on how GitHub makes everyone essentially an open source.
9:58 Speaker 02 Yeah. One of the, one of the things that's been like really undervalued is the degree to which in older open source, part of the barrier to entry that people went through before they were ever identifiable to any contributor was an acclamation to the culture and an acclamation to the tool chain and all of this stuff. And one of the things that GitHub has done is completely removed all of that cultural acclamation. Like, there is one tool chain that you use to contribute to any project. And then when you show up, you don't have all of this cultural knowledge. You haven't like bought into any of these ideals about open source necessarily. You're just there to contribute and it's, and we actually need to, you know, work with that.
10:35 Speaker 03 And there's just more like natural cross pollination, I think, that happens between GitHub projects than there was before, because you can just be on this one platform and very easily move between different projects and kind of glance around. I just think in general, the more you can take inspiration from other places and easily link to them and point to them and have exposure to them, the more likely you're going to learn and iterate on your own.
10:53 Speaker 02 With all of these, there's like a positive way and a negative way to look at it. So like, the negative thing that I always hear is that like GitHub is just a bunch of people dicking around with their own thing and they don't care about contributing to projects that are established, right? Which is like, actually not true. Like, there's, there's a lot that a person gets out of contributing to a project that's, that's popular. And there's a lot of draw for that. The, the issue is that the competition for people's attention is really high. And so unless you're a nice place to come and contribute, people don't care. A lot of established contributors that are used to just people showing up because they're a popular project, they're not getting any people, because they're actually not a very nice place to contribute.
11:26 Sonal? Well, so I have to ask a question, which is, does healthy necessarily mean nice?
11:30 Speaker 02 Now it does.
11:31 Speaker 03 You mean contributors helping, or?
11:33 Sonal? In the community? Because I mean, is niceness a quality of a healthy community? Because don't you want sort of a creative friction and collaboration? How do you sort of navigate that?
11:41 Speaker 02 I would say that in, in modern open source, in like the, the whole GitHub generation, they are the same thing. If you're going to continue to sustain your project, you're going to be needing to get people out of this giant pool of contributors. And many of them need to be, feel invited. And you're competing with a lot of other projects that are nice and inviting.
12:00 Speaker 03 And there's a balance between, like, I mean, there are projects that maybe almost over invest into building really, really healthy contributor communities, but then someone's also got to use them, or else it just kind of becomes this really nice experiment in like, what it looks like to have a healthy community.
12:13 Sonal? What are the qualities of a healthy open source community? I mean, this is very tied to your notion of sustaining, sustaining them.
12:18 Speaker 03 Yeah. I think just making it clear, like, really, really easy for people to join, like, first off, not scaring them away, is really important. A lot of that is in like documentation. So it's not just, here's how you do it, like, steps one, two, and three, but even just human language around, hey, like, so glad you're on this page, really excited for you to contribute. Like, if somebody is not sure if they want to contribute and they read that, then they'll immediately feel more welcome. And then when someone shows a little bit of interest, trying to like encourage and nudge them along. I think is really important. So it really is more of like an active investment into what people are doing.
12:48 Sonal? I mean, is it also like a more formal onboarding? Is there even an onboarding right now?
12:51 Speaker 02 The reality is that some projects are complicated enough that you have to, but hopefully you can get around it or find inventive ways. I mean, one of the things that we've noticed in the Node project is like we've broken up things that you can get involved in. So if you just have the skills to work on a website, you can actually work on the Node.js website. And we see people transition from that into Core because there was kind of a cultural barrier to entry that they're now past, that they're like comfortable to contribute to the project. So, you know, there is no formal onboarding process for the website. It's easy enough to contribute to, but then when they get over to Node Core, like yes, there is, because it's just a little bit more difficult.
13:24 Sonal? It's more critical. So you have to have a slightly higher bar.
13:27 Speaker 02 Well, and not, I mean, not everybody makes that transition. That's not why we have a website project is just to get people into Core. It's more about, you know, healthy open source projects value all of the skillsets that they're trying to encourage. So if we want a nice website, if we want nice documentation, if we want good tests, we actually have to have the same kind of path for those sorts of contributors, right? Like they need to eventually own that work, become committers to it. You know, we have people in the, you know, formal governance body around Core that mostly have worked on tests and they know the test system very well. And the same with documentation, right? Like these are core values, so they need to have the same basically growth path as anybody else does, even if they're on, you know, deeply technical stuff.
14:07 Speaker 03 Code by itself does not make an open source project. You have to have all these other types of skillsets. And that's like one of the biggest issues that I've seen where people don't really understand the value of a healthy community.
14:19 Sonal? That's great. What are some of the other qualities of a healthy open source community? We started off with like the welcoming and the moment they join the community.
14:25 Speaker 03 Then even just beyond like, how do you get like new contributors in or how do you up level contributions or keep people around? It's also like, how do you deal with issues as they arise? How do you talk to each other?
14:35 Sonal? Yeah. How do you actually resolve conflict? I actually really want to get to the bottom of this one. What are the, some of the negotiations that happen, both in the actual commit and in the actual verbalization?
14:44 Speaker 02 So one of the things that I've been a big fan of is inverting this, this whole notion. Usually you'll have like a small group of people, whether the committers or a smaller body of the committed. That are making a lot of decisions, right? And usually you you put this in terms of like their gatekeepers. They have to make sure that every commit lands, right? They have to get agreement about that. That just doesn't scale like there are too many contributions that need to land for that to be the case. So what we do in node and what we've actually encouraged other projects to do is invert that. So that the default mode is for something to land and and you may make corrections to it. You may need to get them to change things, but everything is going to land. And things only escalate into these like people to make a formal decision if there is a conflict around.
15:26 Sonal? Oh, that's interesting. So it's almost like the default is it's gonna work.
15:29 Speaker 02 Well, and and 95% of the commits that we get into core do just land without ever having to go to the CTC, which is the governance body.
15:36 Sonal? Do you think that your model of inverting that is what makes people hold to a higher bar? So they're not sloppy like do you think people are more sloppy when they know they have to go through a gatekeeper?
15:44 Speaker 02 No, I no, I think that like the the reason why it's not very sloppy is because we dramatically increased the number of committers. So like there are, you know, 90 people that can review this. Nothing is gonna make it in unless it's pretty nice. And but the reality is like, you know, a fix to a test, a a small adjustment here, a bug fix there. These are not issues that need to get, you know, decided upon by formal body like they're clearly valuable as nobody's going to object to them. Let's just let them get in. And then, you know, when things are controversial, when people can't agree, that's when we escalated and we have a we have a consensus seeking process. So it's actually a majority vote, but we try to reach a consensus if we can.
16:21 Speaker 03 To me, actually mirrors how we think about like workplaces or interactions with people in general. Humans are just humans, no matter what they're doing. But yeah, I mean, if you think about like evolving manager strategies now in workplaces where it's like wanting to default to trust of the people that you manage and not say, I need to micromanage every single little thing you do, but I want to trust that you are on your own skill to handle this. And if anything is wrong, then I can like stop it. But otherwise, I want to just empower you to do what you're doing. I think it's actually like very in line with like broader evolution of like how we think about human behavior and and how we manage.
16:57 Sonal? I I love that because I think that also reinforces this idea of these communities as sort of new organisms, the new nature of companies, because I'm I'm really fascinated by. Decentralized companies and decentralized organizations and open service is one of the vectors to get there. But it's also interesting because going back to the human side, I remember Jim telling me a story about Linux Foundation where in the early days, one of the biggest lessons they learned was sometimes you just had to pick up the phone and talk to a person directly, just human to human.
17:22 Speaker 03 Yeah.
17:23 Sonal? Like, forget even kind of battling it out, like, you know, in code.
17:27 Speaker 02 Yeah, the CTC, the governance body around node, like, we actually like to discuss things, but I like that. So in startup land, everybody likes to talk about ask for forgiveness rather than permission. But the standard in all open source is you're constantly asking for permission and we guard this commitment like so strongly. And a lot of that comes down to like the history of the tool chain, right? Like with CBS and with Subversion, like, you could make pretty bad mistakes that were very hard to recover from, that really took like an expert in the tool. But Git isn't like that. Git is very forgiving. You really can't mess it up too much.
18:00 Sonal? Right.
18:01 Speaker 02 And so what we've been pushing on is sort of liberalizing that commit access. Like, once you get one thing in that is valuable, like, we will onboard you as a committer very quickly.
18:09 Sonal? Well, and that move from Subversion to Git was also interesting because of how it decentralized or actually now create a new identity for the developers, for the people contributing that code.
18:20 Speaker 02 GitHub is a general kind of collaborative platform and they are essentially the the identity manager for collaboration online, particularly code collaboration. They've won that battle. There might be another battle for other spaces. We'll see.
18:31 Speaker 03 Yeah, I mean, it's cool. I mean, like, if you think about Git's only been around for 10 years-ish, it's not unusual to think that when you have new tools in the system, then the culture of how you work is going to change. We believe that for everything else. Why would we not believe that for open source? And I still, I think that we're just in this sort of like transition period from open source practices that worked in like the 90s or early 2000s or whatever, pre-Git life and have to like recognize that some things are just not the same anymore.
18:58 Sonal? Well, I have to ask you a question. Following up on this idea of that shift, you once argued that there should be no my in open source. And if you could share with us what that argument was and why you made it?
19:09 Speaker 03 There is no my in open source. It refers to the legal position of what open source is and just kind of speaks to the tension that we're feeling today from a new generation of people. So historically, you think about open source as being like, the code is the institution that we must protect and protect its freedom at all costs. I do not own the code because the code legally is out there in public domain. It's like out there for anybody to use, to copy, to modify. That's the definition of open source. And so instead of having a possessive my where you say like, this is my bike, you have an associative my, which is this is my friend.
19:41 Sonal? Oh, that's so interesting. Possessive versus associative. I hadn't thought about that as a shift in the my.
19:47 Speaker 03 I have to credit Carl Fogel, who was one of the original authors of Subversion, for coming up with that and helping me think through that. But right now, like as more and more people are creating and contributing to open source and don't have the same attachment to, let's say, the legal battles of the 90s or the early 2000s, because everyone releases their stuff as open source, whatever, it's not a big deal. And they don't think about the fact that like, it's still, it's not your project. Once you make it open source, it is actually like out there in the public for anybody to copy and use.
20:15 Speaker 02 Yeah, we had Carl on the podcast and he, he just had this like, this idea of open source from the initial morals, not from, you know, what the law actually says. Because all the legal stuff is just a hack in the law so that we can get to this place where we're all working on this thing together.
20:30 Sonal? Oh, and by that podcast, you mean requests for commits, your guys' podcast where you talk about all things open source. That's so interesting. It's literally a way to get around it.
20:37 Speaker 02 Yeah, yeah. And because they don't have this long onboarding process where they have to acclimate to the culture and this giant tool chain, they don't think about these kinds of ideals the way that everybody who was involved in open source in the 90s did, right? It was just one of the, the things that you went through in, in the onboarding process. Sort of informally, you acclimated to the culture.
20:54 Speaker 03 Where that becomes awkward today is that so many different pieces of software now depend on other open source projects, which wasn't actually true, like, you know, 10 or 20 years ago, but now it's really prevalent.
21:04 Sonal? Entire businesses depend on open source projects.
21:07 Speaker 02 Virtually every business.
21:08 Speaker 03 And all of society. Like, again, we, we tend to think about like software companies depending, but it's also like banks and hospitals and whatever.
21:15 Sonal? Right. I mean, it scares me when you mention the heart bleed in the SSL. That really drives it home.
21:18 Speaker 03 There was like a very critical bug that was found in open SSL. And the question was, well, why did nobody find this before? And the answer was because they're like, To there's one paid person and there's like 10 volunteers that are working on this. Like, of course, they missed a bug. Sorry. And that led to this bigger thing from Linux Foundation and and other organizations that were saying, like, how do we actually support these types of projects that they have the resources they need to protect all of the world's information? Right now, today, with so many different dependencies, the question of whether you have this possessive my or associative my is important, because if you want to take down your piece of code, you can't you can take down your version that you put up, but you can't actually take it down from the public domain. Once it's out and it's been licensed a certain
22:02 Speaker 03 way, it's out there. Like, anyone else can take it and modify it and make it their own. And that's like terrifying to some people, because it's like, wait, that's my project. You can't have my project. And it's like, well, because it's not your project, because it's open source. And that's where the tension lies today.
22:15 Speaker 02 The funny thing is, I remember when we were talking to Carl, he he has this view of as long as it has an open source license, it doesn't matter how dysfunctional the project is, because we, as a community, always have this ability to fork it, right? And didn't agree with him on this, because just the practical reality of working a project is such a huge overhaul. And you don't necessarily have the right people to do it at any particular time. And and what you actually want are the healthy communities that have healthy practices. You want to be able to reform them and to keep them going.
22:43 Speaker 03 I think of it as like, we can technically impeach our president if we have to, but we probably want a healthy democracy.
22:48 Sonal? Right.
22:51 Sonal? So what are the incentives for people to contribute to open source?
22:55 Speaker 02 Well, this, I think, is the biggest change that we really need to change in people's conception, because people still go back to the cathedral and the bizarre.
23:01 Sonal? Yes. And you describe that, by the way, because that's a really popular concept.
23:04 Speaker 02 Yeah. So the cathedral and the bizarre is a very, very old Ericus Raymond essay on like, basically describing open source, especially early open source. And at one point, he does get into like, the incentives that people have. And the incentives he describes in in that text are just no longer true. Like, that's not why people get involved in open source.
23:25 Sonal? And what are the what were those incentives? And admitting that we're stereotyping a little here, but just in broad strokes, like, how would you sort of paint the picture of what was the picture then and now?
23:33 Speaker 02 The people that he was describing were technically oriented people, whether they were pro- Or not, who, you know, in their own time, wanted to go and mess around with something and, you know, because they wanted to, you know, get recognition, because they wanted whatever, like that, that was their motivation. And that was kind of where they were coming from. Whereas today, open source runs every business, every technology, everybody is in involved in it in some capacity. If they're developing software, they contribute to and move around the open source software community as a contributor, as part of their work, as part of their social lives, as part of like any kind of side project they do. And it's really usually not about recognition and about ego. I mean, all the people that are highly recognizable in
24:16 Speaker 02 modern open source communities would would trade it for three more people to help them merge patches. Like, I think some of this is really inverted.
24:24 Speaker 03 And something that just dovetails with like, software itself and the process of making it is so much more accessible in the last five years than ever has been before. Now, you can see this happening even in like startups where we used to have this archetypal, like, I don't know, college hacker or whatever who became the founder. And now we are groaning about having these like more MBA types or whatever that are coming in. Part of it is just because it's becoming a lot easier to start a company. And part of why it's easier to start a company is because we have open source software.
24:53 Sonal? Democratize entrepreneurship.
24:55 Speaker 03 Yeah, you don't have to actually write as much code yourself to get something up and running. You can just use other people's tools and those tools are the open source tools.
25:03 Sonal? But where does the vision come from? I'm not saying there has to be a cult of personality necessarily, but it's kind of amazing when there's sort of a driving person, a driving force that sort of motivates people into a new worldview, like whether it's Vitalik for Ethereum, or, you know, Mike Kern in the early days of Bitcoin, Gavin at Bitcoin, whoever it is, Linus Torvalds for Linux, you know, like, we can just keep going.
25:25 Speaker 02 So I think that one of the things that GitHub solved was they made it very low cost to have a lot of smaller projects. And so what you're seeing is that basically large projects, large applications are assembled out of a many, many tiny components. When you have these tiny components, they're they're scoped very well, right? Like they do this one or two things. They're not going to grow exponentially out of control. Whereas in older open source, We were building a database when we were building an operating system. There are a million potential directions that you can go in. There's a million ideas of what the scope of this should be by everybody else. And because it's so hard to set up the infrastructure for an open source project and get it going, there was a lot of incentive to try and get every feature ever into these projects. And but but that goes away and it actually becomes a lot easier to to manage projects when they're much smaller scope.
26:10 Speaker 03 Sort of like the decentralization of anything, anything creator related these days, right? Like, we used to have like 10 internet memes that were really funny. And now, like, there could be a meme that got like 3 million views or whatever. And like, no one even knows it exists. Smaller projects might be really wildly popular, but it just solve like one small piece or have their own size audience that's big enough for them, but doesn't have to be like this, the same sort of cultural personality we used to have.
26:37 Sonal? Does this then leave the domain of like the really big visionary projects that come out of academia? Like, the way Spark came out of Amplab, Apache Spark, where you have an entire new set of companies being built. I mean, they like now have had like multiple conferences like since like, you know, that keep growing and growing and.
26:52 Speaker 03 For me, this is like one of the big questions around sustainability is not just how do we support the projects that already exist, but where are all the new things going to come from that are really, really big? When you don't have any sort of, honestly, like any sort of incentive for it, which I think government and academic institutions have traditionally done for software and they aren't necessarily participating in right now.
27:10 Sonal? So do you have an answer to that question?
27:12 Speaker 03 No, that's what we're gonna do.
27:14 Speaker 02 I I tend to take the long view, like when I see larger projects like that, or in general, what you would call like a framework, where you're usually, what it usually is, is there's a new use case. And in order to really fulfill that use case, somebody wants to take responsibility for the entire problem, not a piece of it. So they build a very large stack, a very large project to go after that. Once, after like a few years, though, you start to recognize what are the good ideas in that stack and what are the bad ones? And.
27:41 Sonal? How do you recognize that?
27:42 Speaker 02 I think it varies, but like you can take a few examples like, so React is like a very big JavaScript framework right now from Facebook. It's actually assembled out of many tiny components, but it's really easy to, for me at least, to poke in there and say like, okay, what are the? Ideas in here that are going to last way beyond when anybody's using this framework. Like they have this notion of DOM diffing and applying the differences to the DOM instead of just applying all the updates or replacing entire sections of the DOM. And like, that's really powerful and there's already a dozen libraries to do that in different contexts. But once we move on to a new use case after that one use case, it's very hard for these frameworks to add things that help them into that use case. So what we end up doing is we break apart all of the good ideas into smaller components that are more reusable.
28:23 Sonal? So you're saying that's almost the inevitable evolution of every successful project.
28:27 Speaker 02 I'm a little bit biased, but also like when I look at newer frameworks for a lot of this stuff, especially like React, they're actually assembled out of many tiny components now. So even our bigger projects are broken into tiny components, just because they're easier to manage, to be honest.
28:42 Sonal? I mean, honestly, it does feel like the natural evolution of things. Everything breaks down into these micro components, whether it's micro services, micro work, micro hours, micro everything.
28:51 Speaker 03 Yeah. I mean, I think about this having like all these like easily accessible little Legos and you could just kind of turn them into one building and you break them apart and you build something else with it or whatever. If the world can function that smoothly, then that would be great. That's an ideal to aspire to. You still need people to think about like, why are we building it this way? Or what does the actual system look like? And that role is actually kind of being filled lately by companies like Google or Facebook that have the resources to make big strides the way that academic institutions used to. That can also lead to like a bleak future if we take it to its fullest extent.
29:21 Sonal? So far, they've been contributing a ton of things. They've been open sourcing their thing because I think they recognize selfishly and unselfishly that for a lot of the most successful things, you need to create ecosystems around them. And that's a really important piece. I mean, even open sourcing TensorFlow.
29:34 Speaker 03 Totally, yeah.
29:35 Speaker 02 But I'm a little bit more critical of those projects in that they are open source technology. And well, that's enough for Carl Fogel. It's not quite enough for me. Like, I would like to see them under either open governance or just like having contributors that don't work for that one company, right? Or having like, I would like to know that the sustainability of this project is not dependent on how much money that they want to put into it. Because I've seen it just happen too many times where, you know, this ends up being more useful than that company has used for it. And it becomes harder and harder for them to justify the continued investment that it takes. For this growing community and growing number of use cases. I mean, like, you know, there are projects like Go at Google where they can continue to flow money into it because they're using it so much internally.
30:17 Speaker 02 But at some point, if they continue to be popular in the community, it is going to, you know, be bigger than just Google.
30:23 Sonal? Right. And but isn't there also been a historic precedent where then a lot of those companies actually kind of gift it to a foundation or a community?
30:30 Speaker 03 Sometimes I think gifting kind of means it's like sending your dog away to the farm upstate. Like, I don't know.
30:36 Speaker 02 Tell me, tell me more ways.
30:38 Speaker 03 Like, sometimes people go, we're really excited to announce that this is now open source, meaning we don't want to take care of it anymore. So go live over there. We'll give it to the community, except they haven't actually identified anyone in the community who wants to take care of it.
30:49 Speaker 02 Yeah, there's some dumping going on, right?
30:51 Speaker 03 It's basically dumping.
30:52 Speaker 02 And sometimes they'll even try to retain some level of control even without investment, which is really bad. But but there are there are counterexamples. I mean, Google just gave Kubernetes over to the Cloud Native Computing Foundation. And that's like, you know, an up and coming project that's getting lots of contributors and lots of new adoption. And that was just because like, for it to be a de facto standard, it needs to be a neutral body, right? So there's there's some recognition.
31:14 Sonal? That is the evolution of computing until now.
31:16 Speaker 02 Yeah.
31:17 Sonal? So clearly you guys are lovers of open source and passionate about everything it represents, the potential, the possibility. So why, Nadia, have you actually said in the past that you hate the term open source?
31:27 Speaker 03 Oh, I said I hate the term open source, which admittedly was a little bit inflammatory to say that. I felt very, I felt this tension coming in as an outsider and talking to some people who strongly believe this one thing is definitely a core value of open source. Then you turn and talk to other people and they're like, no, this exact opposite thing is also a core term of source. And it started to feel like the term open source is just sort of meaningless.
31:47 Sonal? Or just creates all these religious debates.
31:49 Speaker 03 Totally, yeah. And like, and, you know, there are also people who don't use the term open source because they want to use the term free software. And I think I just felt sort of frustrated.
31:56 Sonal? I used to edit Richard Stallman, I know.
31:58 Speaker 03 Oh, my gosh, wow.
31:59 Sonal? And by the way, he doesn't even like the word free. It has to be Libra. He's very specific about this.
32:03 Speaker 03 And it's just, there's so much focus on like, what are all these different terms and what do they mean? And what is my affiliation? And I just sort of was like.
32:10 Speaker 02 There's a lot of identity politics.
32:11 Sonal? It's like religion. It really is like religion.
32:13 Speaker 03 It really is.
32:13 Speaker 02 A lot of it is historical. The open source branding branding kind of helped open source. And then when open source won, I think that a lot of the free software people went, well, that's not necessarily our values. We're going to glob onto this other identity. But then now the people that kind of stayed on the open source side of that also had a bunch of identity and a bunch of values associated with it. And their assumption is that everyone who comes to work on open source needs to acclimate to these values. And with this whole GitHub generation, these people are not grabbing those values before they contribute. They're contributing for a whole host of other reasons, and we shouldn't expect them to share all of these exact values.
32:47 Sonal? The GitHub generation, as you dub it, open source is the default. There's nothing to push against. So it really is just about being a regular person going about your day than about being in open source.
32:57 Speaker 03 And to be fair, in a nod to the older generations, it's part, they don't see all that partially because there were previous generations that were fighting for all this stuff to say like, oh, now you can just like copy paste this license and you're good. But there was a lot of work that had to be done to even develop this license.
33:11 Sonal? We are standing on the shoulders of giants.
33:13 Speaker 02 But even that, like, I feel like, you know, people are taking the MIT license. It's a way to say I'm opting out of these identity politics.
33:18 Speaker 03 Yeah, it's saying, I don't care.
33:19 Sonal? What's a license that we're talking about?
33:20 Speaker 02 The MIT license. So the MIT is a liberal license, similar to like the BSD license. It's now, I think, the most popular license.
33:27 Sonal? It's the most popular.
33:28 Speaker 02 Because it's a better license. And the Apache two license is a better license. But there's a lot of stuff going on with Apache as an identity and a lot of like identity politics around open source. And so I think really, really like why people have been taking MIT is it's a way to say, I just don't want to have that argument.
33:43 Speaker 03 And that's what the, I think the GitHub generation is much more interested in, like workflow, collaboration, process side of open source and the legal side of it. It's just like almost less relevant.
33:53 Speaker 02 Also, the legal stuff still does exist and patent protection is a big deal.
33:56 Speaker 03 There's a lot that's still happening and evolving. And also like companies that are now using open source and like.
34:00 Sonal? Oh, yeah. We haven't even talked about Oracle and, and Google. Like, what the fuck?
34:05 Speaker 02 That's, that's been great for Node JS, though. It's just another reason not to use Java, I guess.
34:10 Sonal? I don't have Sarah on this podcast and she literally live tweeted the entire thing from the courtroom.
34:14 Speaker 02 Oh, that was brilliant. Yeah, I was watching that. That was so good. So Oracle acquired Sun. Sun owns basically all the intellectual property associated with Java. They, they, they then claimed that the API. Which not the implementation, but the actual API service.
34:31 Sonal? Yeah, I remember doing an app bet on whether you can patent an API.
34:34 Speaker 02 Yeah, you can't. If you can, then virtually everything that we've built open source on like kind of doesn't work. And a lot of like our entire industry falls over. So, so no, like you have to pretend that that legal precedent wasn't set, even though it kind of was. And then, yeah, so they, they sued Google for infringing upon that API. And then they actually won a case that said, yes, you can patent an API, even though that's crazy. And then, but they lost an appeal that was very awkward, but eventually won. Google, Google did not have to pay them in the end, but in the meantime, you know, Java's predominantly used by enterprise customers. They're, they're not happy that the underlying IP they've been building on is suspect.
35:16 Sonal? Yeah. I mean, this actually goes to your idea, Nadia, about there's no my in open source. It plays out very differently when the my is an enterprise. Totally, yeah. And it goes back to you guys' ideas about what happens about the good motives of the Google, Facebooks, Twitters, who then open source their internal tools.
35:28 Speaker 02 Yeah, yeah. I mean, it just, it made me think like, I'm not going to invest in a platform that is not like in a neutral body, right?
35:35 Sonal? But isn't that also a little idealistic for you to say, a lot of people have to invest in platforms that are not that neutral?
35:41 Speaker 02 Well, as a programming platform, those are choices that you can make. But yes, like sometimes you have to deal with the App Store or whatever.
35:46 Speaker 03 Yeah. I think it's actually going to be one of the most interesting battles in open source moving forward. What is the role of companies going to be in open source moving forward? Because like briefly summarize the history of open source, there was a time where companies were like, oh, we don't really want to use it because we don't think it's reliable. Then tons of startups got built using open source because, you know, big established companies didn't want to use it. They were like, and startups said, we'll use it. You know, made tons of money. Now those startups are huge companies themselves.
36:10 Sonal? So just to wrap up then, what are some of the other things for what you guys think are ahead? Whether they're battles or things to pay attention to on the horizon? What else is up ahead?
36:19 Speaker 02 Working for a foundation now, I've come to respect some of the institutional infrastructure that you can get behind things. And I think that as we start to think of open source projects as infrastructure, you need some kind of institutional support for that. But it runs a little bit counter to this trend of everything getting smaller and more broken up and more distributed.
36:36 Sonal? Well, maybe the institutions themselves can be that way.
36:38 Speaker 03 You need just a little bit of institutional oversight to then let people do what they want to do. That was when you talked about.
36:43 Speaker 02 Yeah, that is all very true, but it is, it is very, very complicated to implement, especially as we get better at managing open source projects without institutional infrastructure. People become more resistant to it because like it always adds something, right? It's always another thing to think about or to deal with. And I think that people really like to live in a world where they don't have to worry about a lot of those concerns.
37:04 Sonal? Well, it just reminds me what happened with even like holocracy in the organizational sense, right? But it's, I don't think it's saying that you need institution in the traditional way. It just means that you can't just completely dismiss it.
37:13 Speaker 03 Yeah, there's a balance, right? You don't want to micromanage people and you also can't have a completely decentralized system. You have just enough management somewhere in there.
37:20 Sonal? Okay. Anything else you guys want to add on the what's next trends, things that are top of mind?
37:23 Speaker 02 Just personally, I've been mainly interested in the distributed web and a lot of the new stuff going on and like kind of peer to peer distributed web. And it's everything from IPFS to just to Tor to like blockchain is kind of in there. IPFS is a interplanetary file system. It's basically a way to in a distributed fashion, store files and serve them out and eventually potentially even kind of replace HTTP as a transport for web like applications. And then peer to peer in general is just, you know, everything from BitTorrent to, yeah. But there are some new web standards that really helped bring a lot of this along, like WebRTC. And I really like the intersection of this along with
38:04 Speaker 02 sort of like repressive governments and regimes and people who have poor access to information. Like there's actually a lot of benefits to sometimes online, sometimes offline distributed systems that can really do a lot for people. So.
38:17 Speaker 03 I find, coming back to sort of like the holistic look at open source, like I'm really interested in seeing how org structures for open source projects themselves is going to evolve where it has been so lopsided to developers. And code, but the only really way to, I think, like have sustainable projects and sustainable organizations is to bring in other types of skills to support all the things.
38:36 Sonal? And by other types of skills, you mean?
38:38 Speaker 03 People that can, you know, write good documentation, people who can do project management, a lot of.
38:43 Sonal? I would even add design, by the way, to the list because this is my number one complaint about open source projects. It's how fucking good the interfaces always are.
38:49 Speaker 02 I was blown away when we talked to Jan Lernhard from the Hoodie Project and he said.
38:54 Sonal? What's the Hoodie Project?
38:55 Speaker 02 It's a JavaScript library that has probably about as many contributors as users. They've done a very good job of building a great community that way. But it's sort of for building like online offline applications on top of like CouchDB and things like that. Great community. But he was saying that in their community, they actually have a team of people that work on the marketing and actually talk to analysts on behalf of the project.
39:18 Sonal? So the project itself is essentially has a marketing department.
39:21 Speaker 02 Yes, but they're all volunteers. They're all part of the community.
39:23 Sonal? Interesting. So even adding marketing as a capability, that's actually great.
39:27 Speaker 03 They have a editorial team. I mean, they have like.
39:29 Sonal? That's actually pretty great. I mean, that's a natural evolution. If you're saying that this is a wave of the future and it even is here, then why shouldn't it then take on the forms and functions of every other previous successful organization and company before it? And ditch the ones that didn't work. Exactly. Okay, you guys. Well, thank you for joining the A6 and Z podcast. That was a lot of fun. Thank you.
Previous Company Building in Crypto: A Conversation between Brian Armstrong and Chris Dixon Next What's Next for Education Startups Page updated October 9, 2026 · transcript and summary are machine-generated