Josh chats with Ruth Suehle, the president of the Apache Software Foundation and a board member at the OSI. This is a great discussion around what open source, what the ASF and OSI are doing these days. We cover some of the challenges modern open source faces and why this all still matters. Ruth rightly points out all software is open source now, and there’s plenty of work to do to keep open source healthy and working.
Episode Links
This episode is also available as a podcast, search for “Open Source Security” on your favorite podcast player.
Episode Transcript
Josh (00:00) Today, open source security is talking to Ruth Suehle the president of the Apache Software Foundation. Ruth and I have known each other like I think forever is the accurate term. Our paths crossed at Red Hat long, long ago.
And I know Ruth does a ton of other stuff. It’s not just the Apache Software Foundation work. So, Ruth, you know, welcome to the show. I’m so excited to have you here.
Ruth Suehle (00:19) Thanks. I’ve I’ve been listening to the show forever, so I’m I’m so
Josh (00:22) Awesome.
Ruth Suehle (00:22) honored that you let me be on.
Josh (00:25) Honored what? You’re like the you’re the president of the ASF. If I’m the one who’s honored here for sure.
Ruth Suehle (00:33) Mutual high five. High five through the screen.
Josh (00:36) I like it. That works. All right. So tell us tell us about yourself, Ruth.
Ruth Suehle (00:39) Yeah, so like you say, I’m I’m president of the Apache Software Foundation these days. I have been for I think it’s coming up on two years, I’d had been executive vice president for a long time from before that under David Nally. Uh but I’m also these days chair of the board of OSI, uh, which is partly related because my OSI seat is as an affiliate member. So the Apache Software Foundation is an affiliate member of OSI and the affiliate members elected to me to my seat. So um
And I also, because ASF is still an entirely volunteer organization, we pay a handful of people, but mostly volunteer run. Uh, I have been the vice president of open source strategy and ecosystems at Cloudera for about five months.
Josh (01:18) Holy crap, that is amazing. I I actually didn’t
Ruth Suehle (01:21) I’m busy.
Josh (01:22) I didn’t realize you were on the board of the OSI. So that is very exciting as well. So okay, there’s a lot to unpack here, and let’s just make for anyone who might not know who’s listening, let’s start tell us who the ASF is, then the OSI, and then you can tell us what Cloudera is, and then we’ll take it from there.
Ruth Suehle (01:39) my goodness, I feel like actually I should I I feel like I should go in more of a chronological order. Like we should start with OSI and like the whole I feel like this is where you have to stop me from launching into the entire history of open source. Uh so for for the people who really don’t know from scratch, so the term open source was coined at a meeting in Palo Alto on I’m gonna get February, it’s definitely February, I wanna say sixth, nineteen ninety eight. February nineteen ninety eight for sure.
And opensource.org, the website of the open source initiative, launched just a few weeks later. Uh, it’s a really cool page. You should look it up on archive.org. It says something like, uh, open source is here, but it also acknowledges this long tail of like 20 years of software that had led up to that moment. So the OSI is the organization that has stewarded the open source definition for all the years since then, going on 30 years, and is the one where if if you know what an open source license is, they’re the ones who say yes.
Stamp of approval. That’s an open source license. It meets the open source definition. And for the last about four years now, has been working on what the open source AI definition looks like. So we can talk a little bit more about that if you want to. And then so the Apache Software Foundation had been around in some form for quite a few years at that point, around the Apache HTTP server, which for a lot of folks I think of a certain age.
was probably their introduction to web servers. you know, back in the Lamp Stack days and uh when for me Linux was Red Hat. So, you know, you and I probably met at Red Hat, I think. Uh and for me, until I think 2002 when when they announced no more free Red Hat Linux before Enterprise was in the name, I thought Red Hat and Linux were the same thing. And I think a lot of people did. So yeah, that that Lamp Stack of Linux Apache, MySQL PHP. And then ah
Sometime about a year later, March of ninety nine, I wanna say, I should get all these dates nailed down in my head. The Apache Software Foundation was incorporated and these days is home to about three hundred and twenty projects, not just the one. Uh so one of the the oldest open source software foundations still kicking and still doing good work.
Josh (03:50) Yeah, yeah. And I mean, so for anyone who who maybe isn’t as will say experienced, I’m making air quotes as Ruth and myself, the
Ruth Suehle (04:00) Hold.
Josh (04:00) Apa the Apache Software Foundation, obviously the Apache web server was like the big thing, but now like the amount I I suspect the Java stuff is is what is kind of the claim to fame these days ‘cause an enormous number of like super valuable and useful Java things come from the ASF, which is super cool.
Ruth Suehle (04:17) Yeah, I don’t know that any one thing gets to be the claim to fame. I think it’s it’s uh when you’re talking about thirty years of software history, it’s really an an ever changing and it depends on what what you’re into, right? And what’s important to your piece of the open source ecosystem.
Josh (04:32) That’s fair. Yeah, I mean I I I won’t argue with that. So okay. So I’m not gonna lie, I reached out to you because of your ASF work because I saw you were elected. I think it was you said you’ve been president for two years.
Ruth Suehle (04:44) I w uh I think it was November
Josh (04:46) Ish.
Ruth Suehle (04:46) of twenty four. Ti you know what? Post pandemic time has no meaning. I d I don’t know how time works anymore.
Josh (04:48) R regardless. That’s fine. I agree with that.
But it’s basically from that point on, I’m like, I need to get Ruth on the show. So it only took
Ruth Suehle (04:59) Awesome.
Josh (04:59) me two years to make it happen.
Ruth Suehle (05:01) Some of that was my fault, to be fair.
Josh (05:03) No, I’ll I’ll you can have 25% of the blame.
Ruth Suehle (05:06) Okay.
Josh (05:08) But anyway, okay. So I wanted to start with the ASF because that’s actually what kind of the you it was when you announced your presidency, and I’m like, that’s exciting. I know the president now of the ASF.
And and I thought it is a marvelous kind of uh cross section, I think, because obviously my my goal is, you know, the open source security podcast, like obviously open source security related things. And I think the ASF has been doing obviously you’ve got a great security team. I know uh Mark Cox does a ton of work there, which you I worked for for Mark at Red Hat for a long time. And and I’m just like, let’s start with the ASF and just talk about like what is an open source foundation look like today? Because this is a topic near and dear to my heart.
Because not necessarily the direct security implications, but because the open source is struggling right now because of everything happening around it. And unhealthy open source is dangerous open source. And so I think there’s a very important security story here around keeping things like healthy and sane. And like you mentioned, the ASF is still volunteer-led, which is like you’re spending an enormous amount of your time working for free on this thing that I know has.
Nowhere near the amount of funding it needs.
Ruth Suehle (06:22) Yeah, well, and and not just me to be sure. A lot of people are. A lot of people are doing a lot of very hard work. And you know, it it’s also important to note when we talk about all of these people doing this free labor, the reality is that a lot of people are also paid by some company somewhere that allows them to to spend some amount of their time on on Apache work.
Josh (06:37) Yes.
Ruth Suehle (06:37) So it’s complicated. I feel like you can find numbers to support whichever side of the argument you want to make about whether the open source ecosystem is run on volunteer time or all paid. And I’ve I’ve seen both sets of numbers. Uh but yeah, so I
Clearly, what was important when the ASF was formed, uh back in the late 1900s, I like to say, and what’s important as a foundation now are very different things. And here in in the future, uh security is top of mind for everybody. And I think we probably could have have easily said that at any point in history, but now
When open source is the subject of so much regulatory action around the world, not just with the the CRA and PLD and all those things in Europe, but everywhere. And with all of the new work that AI is putting upon us, uh which is a lot, uh, security becomes even more important than it ever has been before. And so the way that we address that has, of course, continued to change. And so one of the biggest things that we’ve done in the last couple of years was establish
tooling office, which then started a project called Apache Trusted Releases, thanks to funding from Alpha Omega, our good friends over there, who uh have done so much for the security ecosystem, right? and so what the the ATR platform has done so far is uh create this web app that handles the full release process. There’s a client that lets a release manager do their work from where the artifacts were built.
We also have flexibility for projects to be able to do what they need to do in the way that they want to, but while meeting a number of security criteria. So I’m really proud of the stuff. Like you say, Mark is amazing. That whole team is amazing. everything that they’ve done for response, not just for the big things like Log4J that we all see, but but all of the little things, so many little things that that people never know happened. And if you go read uh I I always tell people to go read annual reports. I know that sounds super boring, and yet
Sometimes there are really interesting little nuggets in there. And if you go look at the Apache annual reports over the years and the number of things that the security has team has to deal with and that they do so so quietly and so well. Uh so when security is done so done well, nobody ever knows about it. And that’s amazing for all of us, but sometimes a bummer for the people who did all of that hard work.
Josh (09:04) I think that’s a really important point because I’ve recently had discussions with it was a sovereign tech agency and I want to say someone from the Rust Foundation, where it was literally that topic of funding people to do like janitorial work essentially, especially around security things. And like, you know, you’re talking about you have a build system, which I didn’t know because I dug through a bunch of your blog posts and I I I whenever wherever that was talked about, I didn’t make it to that point in time, which you should talk about it more because that’s really
cool. But like there’s so much work that happens, especially in these foundations, that is totally thankless, like totally hidden. It’s like very much the Morlocks, you know, they’re underground doing this work. And without them, like none of this would exist.
Ruth Suehle (09:47) I love that.
Morlocks underground. That’s hilarious. Um yeah, so I you know, a really good example that I think what what did you call us besides old? Experienced, that the experienced of us. sorry, air quotes. The experienced
Josh (09:58) Yeah, we’ll put experience. You gotta put through the air quotes when you say it.
Ruth Suehle (10:03) of us remember uh people who were maybe not quite in the industry but are old enough to remember Y2K. Like it wasn’t directly a security problem or or could have been. But a lot of people think, you know, there was all that drama and nothing happened. Well, nothing happened because a lot of people worked really hard.
And every day, every single day, nothing happens because a lot of people work really hard.
Josh (10:24) I mean, this is one of the challenges the security industry has. And I know like I’ve talked about this many, many times, is when it’s time to go get budget, you know, at the beginning of every, you know, fiscal year, they’re like, Security team, why do you need more money? It’s like, well, to make sure you don’t hear about what what you know what didn’t happen, that’s why we need the budget. And it’s really hard though. It’s hard to say, like, if you pay us money, nothing will happen, right? Like people are like
Ruth Suehle (10:50) That sounds like
extortion.
Josh (10:51) Well it does, right? Like it’d be a shame if something happened to this application you got here. Yeah, yeah, it’s it’s super it’s super tricky and super hard to do.
Okay, Ruth. So we talked a little bit about kind of you know the ASF and some of the logistics there and you know the context of you know funding and Morlocks and and whatever. But but before we move on to maybe some of the other things you’re up to, I want like tell us what like from your position, you know, being in a leadership role at the ASF, like what are the things
you you think you need like I I I always I hate focusing just on the negative, but like obviously there’s things you’re doing well and you covered some of that. But there’s also like what are some of the needs you see in foundations? Like what are the what are you concerned about that and this isn’t obviously just an ASF. Like every open source foundation has lots of problems like this, but I’m curious because we hear about like funding and there’s, you know, AI scrapers are crushing package repositories. There’s like all these things going on right now. And so I’m curious from your perspective, like
What are the things that that I hate to say keep you up at night, but you know, essentially that you’re concerned about in, you know, specifically from the ASF perspective?
Ruth Suehle (11:59) Yeah, well, so what I’m concerned about from an ASF perspective is what I’m concerned about for the entire open source ecosystem. And that is sustainability, which is a word I hate to use because when you say it, people hear money, and it’s so much more than that. and it is a security problem too, and it is a money problem too. It’s lots of problems. So at this point here in the future, I I I feel like we live in the future. We live in the future now. And then tomorrow is a new future. So
Josh (12:24) We Yes.
Ruth Suehle (12:26) at this point in time.
There is effectively no proprietary software anymore. Absolutely everything is
Josh (12:32) Yes.
Ruth Suehle (12:32) built with open source components. We know that. and anybody who thinks that isn’t true and that their company has fully proprietary software should go build their SBOM and take a look and then get back to me because I think they’re gonna learn some new things. And if they do have fully proprietary software, I want to know about it. It’ll be the first one. Nobody has taken me up on this yet, and I’ve said it a lot.
So we know that. We know that we have all of these economic studies from the EU and the Harvard Business School study about the value of open source software. We know what it would cost to replace. We know all of that. And yet still, a lot of companies are treating open source like this endless free supply chain, this endless well of raw materials that they can go dive into and take from. And they don’t understand that a supply chain is a linear transaction where you just pick this need and you procure the thing you need and the transaction is over.
But this whole open source thing that we didn’t ask to become the substrate of global commerce, but it did. It’s an ecosystem. It’s not a linear transaction. And the ecosystem only works like it did the way they explained it when you were in sixth grade. And every part of the ecosystem has to be succeeding or the whole thing collapses. Bad things happen when one part’s not working. Likewise, open source has to work that way. And if we’re not putting back out what we take in, that well of free software, more scare quotes, dries up.
and I I like to say when you treat open source like a supply chain, you get code. That’s great. When you treat it like an ecosystem, like the community that it is, that’s how you get the innovation that you expected from it and the security that you want from it and the resilience that you need from it. So
Josh (14:02) Yes.
Ruth Suehle (14:03) that’s what I’m concerned about is is figuring out what that looks like in the long term as everyone has discovered that open source is the way that we build software now, but that it’s not the magical freelance that they thought it was.
Josh (14:18) Yes, I love this topic so much. There was what the Atlantic Council had a paper they put out a couple of years ago where they compare open source to I think they compared it to like roads and bridges as well as uh the water system, right? Like ecological water systems where obviously if you pollute the river, no one can use the river. And yeah, I I agree.
Ruth Suehle (14:38) I didn’t see that but I would
love you to send it to me because that’s what I’ve been saying for several years now.
Josh (14:43) Yeah, yeah, yeah. I don’t I don’t remember if I talked to the author about that one or not. I mean it has been a while. It’s it’s it makes me sad that they wrote this. I think it’s been like it might have been pre COVID and like it’s still here and it’s still the same story. But yeah.
Ruth Suehle (15:00) I actually
I I came up with a a more microcosm level metaphor. I was walking around Berlin before a couple of conferences back in June, and a good number of parts of the city have these same paving stones all over them, and every so often I would find one that was missing. And I was thinking about it, and I was like, imagine that’s where you live, is on one of these streets, and you notice one of these loose paving stones, and you don’t want to trip on it every day, and you don’t want somebody else to trip on it if they’re walking by. So you fix this paving stone. Cool.
But then the town noticed, so they’re not gonna do maintenance on your street anymore, because somebody’s fixing it, so it’s fine. And
Josh (15:35) Yes.
Ruth Suehle (15:35) then the neighbors on the next street over start leaving notes asking if you’ll fix theirs. And then there’s an apartment building like a whole block away that says that their contractors really need the whole pavement relayed by Q three and they have accessibility requirements you have to meet. And that’s basically the life of an open source maintainer now.
So they’ve got companies filing these issues that are really like support requests, but you don’t have an SLA and their roadmap demands that you do some features and then they’re mad when you haven’t done it all by the end of next week for free. Like that is open source.
Josh (16:04) I yes, I this is that is an excellent analogy and I’m totally stealing it because yes, there’s nothing
Ruth Suehle (16:09) Absolutely.
Josh (16:10) there’s nothing more, I guess, upsetting to me, but also like I just can’t help but laugh when I’m reading an issue, especially for security things, right? ‘Cause something gets a CVE and someone’s like, I need this fixed now to pass my audit. And it’s like, What? Like
Ruth Suehle (16:24) Right.
Josh (16:24) why and I keep telling people I know in these projects, I’m like, you need to open up a Patreon and you need an I’ll fix your bug tier that people can like use ‘cause like
Come on, it’s it’s free, but
Ruth Suehle (16:38) I won’t name and shame companies ‘cause a lot of them have done it, but I have a vivid memory of two guys telling me, um, well asking, how do we make the community do this thing because our bonuses are tied to it? And I’m like, I I don’t think you understand what we do here.
Josh (16:54) I am not even a little surprised that you say that. my goodness.
Ruth Suehle (16:58) But yeah, you’re
you are free to use, study, modify, and share my metaphor as you like.
Josh (17:03) Excellent. That’s that’s a good one. I and you’re right though, because if you started fixing the road outside your house, the city is not going to come and do it ever again.
Ruth Suehle (17:11) Right?
Josh (17:14) I bet the city would love it if we all fixed the roads outside our houses, but
Ruth Suehle (17:18) Either that or they would like send you a cease and assist and demand that you provide your approval letter from them or something.
Josh (17:24) Oh. That’s
true. That could be as well. I mean I nothing would surprise me with with local governments. It’s
Ruth Suehle (17:30) And where I
live the H O would the H O A would get mad that you used the wrong color pavement or something if
Josh (17:36) I luckily don’t have an HOA where I live, but okay, I want to talk about the OSI a little bit because this is like a delightful surprise as we started talking. So like, what are you doing at the OSI and kind of what’s going on at the OSI these days? Now, I want to start out though. I want to start out by telling you the thing I always tell people in in conference talks I give, because I go and talk to a lot of people about open source that like don’t know anything about open source. And they’ll say, like, what is open source? And I’ll put up the OSI logo and I’ll say, Oh, open source is whatever these people tell you it is.
And then we all laugh and ha ha and I’m like, It’s actually kinda true. And then we move on.
Ruth Suehle (18:11) Well, so he at this point in time, the open source definition is pretty well agreed upon by the community, but it’s not something that the OSI declared. In fact, the the open source definition was originally the Debian free software guidelines. That’s where it came from. And it took about another ten years to really refine it into the state that it is. So it wasn’t something that OSI dropped on the world. It was it was community work. Although I totally
Josh (18:32) No, I know. I know, I know.
Ruth Suehle (18:34) understand the perspective that open source is what those guys say it is. I understand why people come to that conclusion.
Josh (18:40) Yeah, yeah.
Ruth Suehle (18:41) So I think it is actually a super exciting time for OSI. So one of the f I’ve only been on the board since uh March. And one of the first things I did March a year ago, again, time became meaningless at some point, and I don’t know how it works anymore. At any rate, uh one of the first things I did this year was help lead the search for a new executive director.
Whom we put into place in March, I believe. So Dwayne O’Brien, whom lots of folks in the open source world have known for assorted work all over the place, particularly around sustainability and funding, uh, has been the ED since the spring and has done just a killer job. Very proud of him. Uh, love all the work he’s doing. So, uh, one of the things that I have done more recently is lead a governance working group to talk about how OSI will.
continue to seat board members. Cause the last couple of elections uh ended
Josh (19:35) Yeah.
Ruth Suehle (19:35) in differently hairy ways, shall we say. And
Josh (19:39) Yes, I I
so I I only have kind of a very one-sided view of this, but I was reading a very play-by-play from it was Richard Fontana and Bradley Kuhn, and it was like I don’t know what’s happening here, and I know obviously this is a very porthole view of a process from a very opinionated two people, but like, holy cow, this sounds wild.
Ruth Suehle (20:01) Well, and I I think to some extent, uh a lot that happened was for some people a misunderstanding of what election meant in the OSI context, because the OSI bylaws, it’s not a membership organization. It’s not an election situation. Those are advisory. So technically, the board could seat whomever they want, regardless of of the quote unquote election. but historically
Josh (20:26) Uh
Ruth Suehle (20:27) did generally seat the people that the election chose.
There was a lot more going on, but that was part of it. Nevertheless, uh, we never like for a community to feel surprised nor disengaged. And so we wanted to talk about how we could make sure that everybody was on the same page, everybody felt heard, and that the board could be as diversely represented as possible in in every dimension. So uh different types of foundations, different types of companies, academia, government, different parts of the world.
It’s hard to represent every possible direction in a a small board, but to the extent that we can. So we’re just now starting to get to the point where we’re talking about those those governance finding publicly. I think there was a blog post back around All Things Open, the end of October. Um and so there’ll be more coming out of that in advance of the next round of elections next spring. So that’s been very interesting uh from a a uh
Deep and dirty governance perspective, but probably the coolest thing going on from a broader open source ecosystem perspective and less about the nitty-gritty governance of foundations, which bores a lot of people to tears, is the open source AI definition, which also was not without controversy. So for for folks who are less familiar, about four years ago, uh before I well before I was on the board.
OSI recognized that the term open source AI was getting thrown around a lot in the news, in uh even in regulatory places, in policy, and that there was not a universally agreed upon definition of open source AI. And beyond that, the ways that it was being used were ways that most of us would not recognize as actually being open source as applied to AI. So in at the all things open.
In 2023, 2022. ah you know what? Before you talk to me in the future, you should tell me to get my calendar date straight. So,
Josh (22:29) That’s fine, no one cares.
Ruth Suehle (22:31) yeah, at all things open a few years ago, we had the first of a series. I say we, I again was not technically part of OSI at the time, but I did go help lead this workshop on what an open source AI definition would look like. And it’s really interesting how far it’s come from that first meeting. So that first workshop.
I’m gonna say about two-thirds of the room said, We we have an open source definition and AI is code. Why do we need another definition? Which at the time I and what open what AI looks like has changed so much since then. Uh, even in the last six months or a year, what we call AI has changed so dramatically. And so those conversations started to evolve into, well, what do we mean when we say an open source AI? What is what does that mean? And we started to look separately at the models and the weights and the data and all of the components.
And so then uh two years ago at All Things Open Again, uh, because OSI always has uh a little state of the source track there. That’s why it keeps coming around to All Things Open. Uh, they released the first version of the open source AI definition. And it is it is interesting in many ways. Uh it is it has shortcomings in other ways, particularly two years later. And the part that was uh the least agreed upon.
Is the part about the data because what it says is not simply the data must be open. It says that if you can provide the data, you must, and then there are various conditions upon which if you cannot provide the data, you must do X, Y, and Z. Down to the point of if it is technologically or legally impossible to provide the data, you have to provide as much information as possible such that one could recreate the data reasonably. So
All that said, uh a about a month ago, the OSI held the first of a new series of open source AI salons, hoping to bring together leaders and and folks working with AI from every corner, not just open source, but the the academics and the researchers and the folks in government, particularly looking for people who may have been left out of the conversation the first time around, to discuss
what ways we got it right and what ways we could improve it so that we can keep iterating. Because again, the original open source definition took about 10 years to solidify. And so we we need to move a little faster, I think, when it comes to AI because of the speed of the technological change. But on the other hand, it did take us a while the first time. So it might take a minute the second time too. So I I went to that uh sorry, I’ve just been rambling. Go ahead.
Josh (25:06) No, this is amazing. This is really
good. I mean, ‘cause you’re right. Like from from my perspective, you know, I at least I feel like I hear the word open weight used more than open source. But yeah, like a couple of years ago, everyone kept calling everything open source and it’s like that’s not open source at all. You know, and and it sounds like there’s a an attempt at a definition. And you’re right, it’s gonna take time and you’re gonna screw it up and a bunch of people are gonna hate it and a bunch of people are gonna love it and whatever.
I that’s just how this stuff works, right?
Ruth Suehle (25:38) I think absolutely the most interesting thing that somebody said at that salon a few weeks ago, uh, and it’s crazy that I’ve been thinking about this for four years and there was still so much said that day that I just had not yet thought of at all. But one of the most interesting non-technological detail points, someone said when we’re talking about creating this definition, is it more important to be right or to be relevant?
And I just stopped for
Josh (26:06) I mean
Ruth Suehle (26:06) a second. So I thought, well, the obvious, the, the, the gut response from I think everybody in the open source ecosystem is it’s important to be right. So much of so many of the people that we work with in open source have done it for so long as a philosophy, uh, because it was the right way to do things. And so I think for them, it’s about being right. But if we think about history, if we think about why the term open source was coined to begin with.
It was an attempt to make what was being done relevant from a commercial perspective. That was a part of that conversation. And so I don’t think it’s impossible to be both right and relevant, but I think it is a super interesting question in the context of figuring out this definition.
Josh (26:53) I mean, so this is related to a question I was gonna ask you kind of later on, but so I have many gripes with the OSI because I think but but what you just said I think clarifies a lot of this, where I think the OSI is right in terms of like open source licenses, but I also think a lot of open source licenses are not meeting the current like challenges and
And just environment open source has right. And that’s where you get into that, would you rather be relevant relevant angle? So that is wow, that’s like a super deep thought right there. Because you’re you’re right, like we wanna be right, but sometimes you can be right and it doesn’t matter. my goodness.
Ruth Suehle (27:39) Yeah.
Well, so what is what have you done for the world if you create a definition that is quote unquote right to whatever your definition of right is, but it’s not something anyone can use. Have you done anything at all?
Josh (27:54) Right. Right. I we just said the word right a lot, but I mean, no, this
Ruth Suehle (27:57) Right. Left. Wait.
Josh (28:01) is this is spot on because like I know a bunch of people that are pretty young and they’re they’re very much in we’ll say open source and and it’s not open source like we think of open source, like you and I, right? Because we come from a a certain era when like my my personal goal was like I wanna see Microsoft go.
Like I I loved it when Matthew Zulik was at Red Hat and he was like, The road to Redmond leads through Mountain View, which meant first we kill Sun, then we kill Microsoft. Like we got one of them, but we didn’t get both. You know, ‘cause that was like that’s what we were there for. You know, in a lot of younger people, they’re like, I just want to put a thing on GitHub and and it solves my problem or it, you know, it’s part of my game or whatever. Like they don’t care about like freedom, like we think about freedom.
And that’s I think that whole right versus relevant because from their perspective they stick the Apache two license on ‘cause they’re like, whatever, this is easy, I don’t care. But you know, they from their perspective, like no license it would be just fine. They don’t they literally don’t care.
Ruth Suehle (29:03) Yeah. And I think that’s something that I’m seeing definitely things that are coming from OSI, things that the ASF are doing, things that I’m seeing other foundations do as well, is trying to reach that next generation for whom GitHub has always existed. And so they don’t
Josh (29:18) Right, right.
Ruth Suehle (29:19) actually know what open source means. They’ve heard those words, but to them, like you say, it’s throw some code on GitHub and uh their biggest decision is it Apache or MIT and they don’t know why. And so they end up just clicking one. I and that’s really what it is.
Josh (29:30) Yeah, yeah, right, right.
Ruth Suehle (29:33) I so
Josh (29:33) That’s right.
Ruth Suehle (29:34) can I can I ask you, can I go on a tangent about Microsoft?
Josh (29:37) Please, please.
Ruth Suehle (29:39) So w I have a similar path, except that for me it’s I I was never like gung-ho about I have to kill Microsoft. That was not a personal mission, but when I got my job at Red Hat and I tried to explain to my mom what Linux was and what Red Hat was, and I tried to explain it and finally she goes, So you’re like not Microsoft? And I said
Sure, let’s go with that. And she’s like, You go get Microsoft. So that was the beginning
Josh (30:05) Excellent.
Ruth Suehle (30:05) of it. And then fast forward some number of years and ah after opensource.com launched in 2010, so this was probably late 2010, early 2012, I was at a conference and this guy from Microsoft came and talked about what he was doing to sort of seed open source around the company. And I went to talk
Josh (30:24) Nice.
Ruth Suehle (30:24) to him after and I was like, I’m so excited to write about this on open source.com, blah blah blah. And he goes, my god, you can’t tell anybody I was here at all.
I was like, but dude,
Josh (30:30) Uh-huh.
Ruth Suehle (30:31) you just gave a talk in public, but okay, cool. And then not, I think it was 2015, a few years later, probably my favorite conference booth backdrop ever. And I just found the picture of this a couple months ago. I didn’t think I still had it. Microsoft’s booth at LinuxCon, I think it was still called LinuxCon, was just this blue background, a white silhouette of a pig with wings, and it said Microsoft’s open source program and other things you never thought you’d see.
Josh (30:59) Epic.
Ruth Suehle (31:00) Still my favorite booth ever.
Josh (31:03) I mean in in fact I remember going to LinuxCon just to fight with the Microsoft people because they
Ruth Suehle (31:07) Ha.
Josh (31:08) they started going and it was yeah, I was I mean I was young, total jackass, but whatever. Okay.
Ruth Suehle (31:14) Okay, my second
favorite conference booth though is Oracle with a guy in a Darth Vader suit, and like, huh.
Josh (31:22) There’s a lot to unpack in that one that we’re not gonna do today.
Ruth Suehle (31:25) To be
fair, that was so it was during the Linux con that was in Chicago at the same time as Wizard World and so everybody was in costume. Just thought that was an interesting
Josh (31:31) Uh
Ruth Suehle (31:32) choice.
Josh (31:33) okay, okay. I mean, still All right, Ruth. Why don’t let’s start to land this plane. So we’ve covered a lot of ground, and that’s part of the fun of talking to an old friend as we obviously get to go on these crazy tangents and things like that. But what I’m really interested in is like what what are you working on and what do you think is going to be the the topics from either, you know, ASF hat or OSI hat or both hats or however you wanna wanna cover this. But like
What are the things you think we should be paying attention to? And what are the things you you think that would be beneficial for people to maybe lend a hand with if this is something they care about?
Ruth Suehle (32:10) So what’s most important to me right now is that stuff we were talking about about the sustainability problem. And that it’s really not just fun. Everybody needs more money. Everybody will always tell you that they need more money. Uh and I always encourage people to go figure out what that foundation needs the money for, how they’re spending it. Uh but the deeper problems are not money. They’re architectural and they’re governance and they’re cultural, because you can have all the money in the world with a single maintainer and no succession plan, and that is one bad day from collapse.
And you can have all the money in the world and a terrible community, a toxic community, and you burn through all your contributors and the project ends. So figuring out the resilience, figur figuring out the sustainability is important. That education, bringing in the next generation is important. Uh so from the ASF perspective, a few years ago we changed the name of the conference from Apache Conda Community Over Code.
And a lot of people still have an affinity for that ApacheCon name. I know I do, and occasionally I still call it Apache Con because it’s it was ApacheCon for a long time. But that community over code is really the ethos that I think is important to sustaining the entire ecosystem for the long run. Uh and I think it’s really what sets Apache apart for a lot of people is that community aspect. So building that there, one of the things that is coming out of that OSI governance work that I was talking about is.
I don’t think it’s easy for people to see how they can contribute to OSI work, what what they can do, how they can volunteer there uh without being on the board, basically. And so I want to create something that looks like the analogous to the contributor sort of process in a project, but not code. So ways that you can be analogously a contributor, a committer, a maintainer of an OSI project of some sort, what that might look like.
another thing I did this year was so there’s this thing called open source congress that started four years ago to bring the foundation leadership together to talk about matters of common interest instead of all of us reinventing the wheel. Stop me if you’ve heard this before. We collaborate on things that we all do to make it easier. So the first Congress was hosted by the Linux Foundation, the second Congress was hosted by Open Atom, the third was hosted by Eclipse, and then we hosted it this year.
And I think the biggest thing that came out of that is working groups. So that this is a a year-long ongoing thing where people talk to each other about the things that are important to them. So we have groups talking about governance, groups talking about security, groups talking about AI, whatever it is that that is most concerning to them and the things that they need help on, so that we’re not all redoing things. So that’s what’s important to me from from all the hats is
Figuring out how to make sure that open source continues to be as successful for the foreseeable future as it has been for the last thirty years.
Josh (34:59) Love that. I mean that feels
When you say this, it feels like the answer is well duh. But like that happens so often, I think, especially in the world of tech, where we like how many all of our problems are communication problems, right? Like it feels like every time and
Ruth Suehle (35:18) People are hard.
Josh (35:21) I know, right? Yeah, yeah. I mean, it it seems so obvious, but I get it too, just because you know, I’ve been part of lots of open source projects. I’ve I’ve helped with many open source foundations.
And it is uncommon for there to be a lot of cross like foundational, even cross project efforts. I mean, how many open source projects have the exact same problem the exact same way and no one ever right, no one’s talking to each other? And granted, it’s hard to even know where to go to talk or what to do. I mean, this is where like the ASF had places help, but it’s tough. I get it. Yeah.
Ruth Suehle (35:56) Yeah, hopefully fewer and fewer. So I’m I’m hoping open source Congress will solve that for some problems. That’s what Alpha Omega has tried to do is make sure that everybody isn’t reinventing the same security wheels over and over again. So hopefully we’re doing a better job of that. You know, we’ve had the UN Open Source Week for the last four years or so where people are coming together. We’ve got the open policy alliance at OSI for people to come together. If you don’t have a policy person, let OSI be your policy person. Let everybody else in the room be your policy person. Do it together.
So I’m seeing more and more of that collaboration across foundations that I don’t think we’ve ever had before. And it’s amazing. I so I also think about a lot the fact that community and collaboration, all of that, that’s not actually part of the open source definition. At no point in those
Josh (36:39) Yes.
Ruth Suehle (36:39) 10 points does it require any of that. But that is what makes it work.
Josh (36:45) I yes, I agree. I agree a hundred percent. And I think we should just call it there ‘cause that is a marvelous ending for this discussion because yes, community is what
Ruth Suehle (36:54) Awesome.
Josh (36:55) it’s all about, even though it’s not technically the definition.
Ruth Suehle (36:58) Put a stake in it.
Josh (36:59) Awesome. Ruth, this has been a ton of fun. I wanna thank you so much. I can’t wait to have you back at some point.
Ruth Suehle (37:04) Thanks for having me.