UDSKRIFT 🔗
speaker-0: Hi, this is Rachel Rameliotis from Punch Tape, and we are here with an episode of Contribute Beyond the Code. We have a great interview with Patrick Masson of the Perio Foundation, but before we get to that, I want to touch upon a couple of big open source headlines. The first of which is that GitHub is talking about open source and AI and the impact that it is having beyond the code. And so what I wanted to highlight was something that they mentioned, this was in their blog piece about their update for 2016. It says, expect the open source projects that continue to expand and grow over the next year to be those that incorporate AI as part of the community infrastructure in order to deal with this quantity of information. they mean from AI. AI cannot just be a coding assistant, but needs to find ways to ease the pressure of being a maintainer and finding a way to make that work more scalable. So that is a definite pain point and I think something that people have been discussing both pros and cons about. And so we'll definitely continue to talk about that aspect of AI. usage in open source. It's very interesting and I do think that we will see more and more of that as the year moves on. The other item I wanted to talk about, and this sort of starts to branch into our interview today with Patrick a little bit, is sustainable funding for open source. And so there's a new group, Open Source Endowment, at endowment.dev. And this is a group of people that have launched this nonprofit to help solve the issue of funding. ⁓ and this includes a bunch of folks, including Thomas Adonka, Mitchell Hashimoto, Paul Coplestone, and many more. There's 50 donors so far. They've raised 700k and expect to have much, much more. We will try to have someone representing this group on in an episode to come, but it's interesting in that people are looking at all different ways. to fund open source as it continues to be a necessary part of software, software development. back to Patrick. So this interview is really great. Patrick is talking about how foundations can self sustain and thinking through different business models. And whether you agree with them or not, I think that he is always thought provoking and we need people like him to be. pushing the boundaries and thinking through how we do things and whether there's a better way to do them. So I was lucky enough to get him to speak with me for the podcast and I want to thank him very much and onto the interview. Hello, Patrick, thank you so much for joining me today.
speaker-1: Happy to be here and thank you for the invitation.
speaker-0: Of of course. You've been doing some interesting blogging and speaking, so I definitely wanted to get you on the podcast. And here you are. So, okay, let's start at the beginning with a little bit about you. So you have been a university CTO, CIO. You previously led OSI, and now you run Appereo. How has your definition of open source sustainability changed sort of with the different knowledge that you've gained across these different roles?
speaker-1: Well, I don't know if the knowledge has changed so much as it is the perspective. So from a CIO CTO position at those institutions, we were primarily consumers. So our orientation was ⁓ assessing open source and as part of those open source projects, the sustainability often is a way similar in a way that you would with commercial proprietary software. So in the traditional pre-recurement process, you would have an RFP or an RFI sent out where you're questions about the company and its stability and its practices and, know, to assess not just does the technology meet your needs, but is the company viable and sustainable in itself? And I could go into a whole thing about ed tech turnover through bankruptcies, acquisitions, and others, but I won't get distracted there. ⁓ now in a role of supporting open source projects. The perspective is, as a producer. And so it's the other side of the coin. And I think having that context of what, especially at Appario, where we work in higher education, what campuses are looking at as they assess open source software as a product that they're going to implement is important. You know, I've never heard in my, gosh, 30 years now of working in, in higher ed, and I've never heard a student pick which university they were going to go to based on the content management system.
speaker-0: I think that would hold true still, yes.
speaker-1: You know, I'm waiting for the day that, well, I was going to go to Duke, but I decided to go to UNC because I like WordPress more than Drupal. I mean, that just doesn't, or Blackboard versus Canvas or whatever. That just doesn't happen. And so those are basically commodities now that institutions have to use to deliver the services and the education that they provide. So it's just not something that the institution is looking at in terms of sustainability is just like it would be for if they were engaging with a company. So I think that's a different perspective. And I think there's a different value proposition. So there's development as a by-product. And I think that's open source development is a, higher education as a by-product of your primary work. So you have researchers that need custom tools or to develop some software to do some research activity. And so they create an open source tool because they're working with a, know, collaborative group across campuses and it just makes sense to open source it. so the. The effort there is, you know, to, to the outcome should be shareable and benefit from that collaborative effort. So that byproduct. So I think that's an institutional perspective of in higher education. Then there's implementation as a non-differentiator. And that's where companies might embed open source software within a tool that an institution might use. And isn't really even a factor like the rich text editor in canvas or desire to learn is probably open source. I don't know if
Load full transcript
it's not, but why would they reinvent that wheel? And so the core value is online learning in that example. And the rich tech center, open source doesn't really, it's not a differentiator. Again, I've never heard anyone say, well, I was going to go to Target, but I went to Walmart because I really liked the way their ERP system manages over time. You know, nobody does that. Right. But the consumer doesn't say, why don't you buy this lawn chair there? But now I'm not because over time is ERP systems better.
speaker-0: They want their overtime pay though.
speaker-1: Yeah. And then there's a recent phenomena. And I would say that the development of the byproduct is the sort of original motivation behind open source. Right. Everyone was working on these same things. We all have to put up a web server for our job. So we might as well build Apache and work together. And now the most recent perspective or approach is open source as a product. So you have entrepreneurs and VC coming in to develop open source tools and there's ambiguity. around the support and sustainability and even contracting with those products, not so much projects. So I think those elements present differently in the context or the perspective of a institutional assessment as a CIO, CTO versus presenting your projects as a project leader, maintainer, foundation, executive director, whatever it might be.
speaker-0: Well, and which makes sense. And I think that's a really valuable perspective to have. Right. And I think one of the things, you know, fundraising in this area is something that is an ongoing challenge. And I know that you have more recently been looking at, you know, is there is there is does the process need to be fixed? Is there a different way to do things? How can we do things? So first, I wanted to ask you sort of was there a moment when you were like, this is not going to work anymore. And I guess then what was your next step?
speaker-1: Sure. I don't think it was any, you know, bolt of lightning that struck. And there was a, definitely an upwelling of, you know, maintain the maintainer. And it was a, it was a meme that was out there and there's the dependency meme cartoon. mean, all these things have been around longer than probably most people, even who went through it, seem to recall. It's like, wow, we've been talking about this for 10 years. But I think, you know, I think. Thinking about this, the first instance where it sort of became a disconnect was in, think 2015 and a researcher from Molson School of Business in Ottawa or Montreal, me. uh, uh, think his name was Chitu Okoli, um, and The name of the paper is business models for free and open source software. And he reached out to a bunch of open source developers, including the open source initiative while I was there and asked them, what are the business models associated to support free and open source software? And when that work was done and we got the paper back, if you look at it today, I'm sure it's
online. All of the business models had nothing to do with production of software. It was all the things that you would expect, like sort of red-hatting it. where the services and support and ancillary activities that created value for those who were using that software. So I think that was like, okay, sort of makes sense. But then the question becomes how are projects engaging or practicing in ways that allow for that? Projects aren't doing that. Most of that is picked up by companies. The reason it's red, know, red hatting is doing it. They're a company that's doing it. If you walk through a conference session, you know, the shark tank with all the companies. There are all those companies are supporting these projects that foundations have built. The foundations aren't doing it. So I think that's sort of when this started, I started thinking about this and that's an incentive mismatch where consumers optimize for the immediate value of open source. So they want it now and then they need that support. But the ecosystems, the open source movement requires a shared long-term investment. And this gets into soft money and sort of the traditional ways that folks have. Uh, or projects and foundations have raised money, but in sustain OS 2020, we did a round table and I remember distinctly saying that we need to stop thinking about, uh, open source as a charity. And if you position the organization as a charity, it's first of all, it's going to be perceived as a charity and it's going to suffer all the same financial headaches that a charity goes through. And I had forgotten about that and the perio just has hired. Christian Alexander, who comes from Wall Street and he's working with our ⁓ partnership and business development. And he out of the gate said the same thing and in much more economic and finance terms, but he comes from Wall Street. And he did an evaluation and said, look, if I were reviewing this as an investment sort of a portfolio and you know, do we, how does he worked at Goldman? How does Goldman want to engage with this? It's like, I don't know what your...
speaker-0: Sometimes you need that outside viewpoint.
speaker-1: What's your business model is and not business model in the sense that Stephen Wally would get all upset about business model, but the organization has to have the foundation has to have a business model, not the open source product, which I think or project, which I think is slightly different. Sure. agree. Because projects are dependent on soft money, grants, donations, sponsorships, you know, they, they treat themselves as philanthropy. So this idealistic view of like everyone should be. contributing to this, you're using it, you know, there's a sort of rage that takes over. Or hopeful, right? It would be rage for me maybe. But it's this idealistic view that the companies that are using this are sort of these good natured golly shucks we should, we should really help out these open source developers that we're exploiting. And so that philanthropic idealistic view is inaccurate. I think it needs to shift to an entrepreneurial view of like, what can we do?
speaker-0: ⁓ yeah, rage.
speaker-1: to offer additional value add to the software itself as a community of practice. What are some ways that we can, what are things that we can deliver? I guess one example might be project specific conferences. like PyCon might be an example. ⁓ One really good model is the Moodle. Moodle is a learning management system ⁓ in higher ed and K-12. And they have a model where if you want to call yourself a Moodle support provider. You have to contribute ⁓ some of your profits back to the community. And they do that through a intellectual property licensing of their trademarks. you can't use the Moodle brand logo name for commercial purposes unless you signed a Moodle partnership agreement. And that works because it's creating revenue from those. It fosters an ecosystem of support providers. It also creates a... a channel, a vehicle for funds to come back to the institution. And it also provides credibility because there's an assumption, I'll call it an assumption, but I'm sure Moodle is doing more than just handing out a license. That Moodle has done some sort of review of these organizations to ensure that they're engaging authentically and have the skills and the training and so on to be sort of a Mr. Goodwrench of the good housekeeping seal of approval has been given by allowing that name to be used. And so it creates confidence with the community who might become customers of these third party providers. And I know that if I'm giving my money for real work to these companies that are providing by hosting or help desk or training or whatever it might be, I know some of that money is going back to the project. So I'm contributing and still getting my service that I need.
speaker-0: standards and whatnot, yeah. That makes sense. how are you, so, and you've called this sort of self sustainability and what I've seen when you talk about this, how have you been working towards implementing that at Appereo?
speaker-1: So, well, to be honest, this is a new concept and we're just beginning to socialize it. So thank you again for the opportunity. The good news of self-sustainability. So, you know, we're interested in getting feedback and testing some of our assumptions and we're working through our own financial models to make sure this would work. But I guess the core crux that we're thinking is we give away our code, but we don't have to give away our skills. you know, there's this perception that
speaker-0: Of course. No, think it's really
speaker-1: Well, to be a really like community oriented and welcoming and having onboarding, is all, yes, we need to have those things. We have to go out of our way to provide all the support and services. So when a project first starts and they're trying to build community, it's like, ⁓ they're really responsive to issues or bug reports or,
questions or people who they're totally into it. Then as the project grows, what happens? This is when you hear the classic sort of phase of like getting into burnout because like, I can't keep up. They're making demands of me. Who do they think I am? Well, they're, they're suffering from their own success, but they've created an assumption and an expectation that there's one or two people, three people, a small project is going to do all this stuff because they've been doing it before. And they were originally doing to drive adoption and foster engagement, all sorts of good reasons. And it's sacrilegious. And in fact, if I say this, I will, I don't know, you'll get the emails cause they'll, they'll... But why not charge for different service levels, um, through a discussion forum. So if you want to just post something out into the, you know, project X ether and someone else might come on and help you, that's great. But if you want to post to a, uh, uh, discussion forum where the maintainers and the contributors are hanging out.
speaker-0: That's fine, I can take it.
speaker-1: then that's going to cost you or organization something. Or if you want to get a response within a certain amount of time from one of the community leaders, it's going to cost you a little bit more. But that's, you know, that's scary to say out loud. mean, my own room and I think someone's going to bust in my door and start yelling.
speaker-0: I think it's good that you feel comfortable enough to say it. think you're doing it in a very open source way where you're saying, like, tell me what you think, right? But like that's what makes open source powerful, I think, is that there are different viewpoints. And I mean, I think you're bringing up something that you're bringing up a possible solution to a problem that many, many people talk about. Is it perfect? I don't know. But I think it's good that you're bringing it forward and doing tests and stuff like that. It's interesting. mean, you're seeing it's like a, it's a service model kind of, right? So.
speaker-1: Exactly. I think sort of true sustainability is collective. Maybe we'll talk about this later, but it's not isolated. It's, you know, the misunderstanding is assuming that independence equals strength or that our project has it all. So you just, it's one-stop shop that will do everything for you, but not realizing the demands that's going to put on those who are delivering those support services. When in reality, it's the interdependence that creates durability. So collaboration is what's valuable there.
speaker-0: For sure. And I know that there is collaboration throughout the foundations. And so one of the other things that ⁓ I don't know if we've specifically talked about it, but ⁓ there's shared practices, right? There's things that all of you do. Maybe some of you do better than others, but governance, like IP control, policy, stuff like that. You know, how do you... Well, I guess first of all, talk a little bit about how you see this working well and then how maybe you can improve.
speaker-1: the self sustainability model.
speaker-0: No, sort of no. So there's definitely that. But I think there's also, like you're saying, it's not sort of like one foundation against another, sort of like how can these networks of shared practices, you know, it's basically, I don't know, this seems like less than what it is, but like cost savings life. You know what I mean? Like how can you all work together sort of too as a network to say, you know, this is the best way to do this or this is the, and again, I know that some of this goes on, but so. I guess talk a little bit about what goes on today and are there things that would be cool to see in the future?
speaker-1: Yeah. So, you know, I think, I think Simon Phipps and, um, Thierry Carrera have both sort of talked about too many foundations or no more foundations, please. I forget the titles of these, the, um, the sessions they did, but, know, they sort of bring up this, this idea of like, do we have too many foundations and everyone wants to spin up a foundation? And even interestingly, this is a little bit into the weeds, but the, um, National Science Foundation here in the U S offered a ⁓ Pathways to Open Source Ecosystems grants. And when I read those, and we're working on a couple of them, and it sounds like the expectation is that the NSF wants to promote sustainability with these software projects that prior NSF funding has helped to create, which is a great idea. But the expectation is that each of these projects will evolve into a foundation. And to that I say, we don't have too many projects and foundations. We have too many projects and foundations doing the same things. is what your point was. So last September at the open source Congress in Brussels, this was, think a big theme of folks that we're talking is, is perhaps how can we collaborate more across foundations? ⁓ So funding a single project ignores the shared infrastructure it depends on. Like you said, the governance, the community management, the legal structures, onboarding process, whatever it might be. All those foundations do those things. And what became clear to me after going to the session was like, know, Eclipse Foundation and OSI have really good policy people and the policy work they're doing impacts a lot of the stuff that Appario is doing. So why wouldn't we all work together to fund and set a direction and, and, you know, sort of job descriptions and identify areas of interest that we want these policy folks to work on that help the community. And isn't that sort of how open source is supposed to work? Right? For sure. Aren't projects, they'd be ridiculous if like the example with the rich text editor that I gave before. Like every time we spun up anything that did text editing for any tool that was ever made, everyone went out and not only made the same rich text editor, but also created libraries for aligning left and bold. I
mean, that would be crazy. What's the point of doing this open source thing if you're just going to rebuild everything. So why don't foundations work in the same way?
speaker-0: Do you think, what do you think is the blocker? I don't think it's, I don't think it's anything malicious. I think it's probably just people going on their own paths. But like you said, open source was the, you know, part of it was realizing everybody was on their own path. Like let's come together.
speaker-1: Well, I don't know. think, so John Lewis, who is a former, a period board director and long time EdTech person, has my favorite quote is that open source is a profile economy. And I do think that, you know, the benevolent dictator for life and the persona around some of those folks and wanting to be on stage with the lanyard and giving your emotional speech and being a leader in this tech. I do think that there's a little bit of a profile building that's involved in open source projects. do think that with so many open source projects, it becomes a bit competitive. Yep. It's to take it out of, maybe I'll pick on higher ed instead. So I don't have to name names. Sure, sure. But when I was at University of Massachusetts, online learning was sort of picking up and online nursing programs were becoming very popular because there was a nursing shortage and universities were building.
speaker-0: Sure.
speaker-1: But once it became online, everyone was competing for the same nursing students. we get, you know, theoretically universities all within the UMass system complaining that, you know, UMass Lowell put a billboard in UMass Dartmouth's territory for their online nursing program. Right? So there is scarcity of resources. And so I do think that the projects are all sort of maybe not fighting, but vying for those, that attention. So I do think there's some competitiveness that is in place. And I also think the evolution of many of the foundations, how they started, they needed to do all these things. Think about foundations 1.0, right? They all needed to set up infrastructure, right? Before, you know, GitHub and GitLab and Git in general, you know, people had maybe, you know, their own subversions or some, you know, versioning tool that they were making available. They might've had infrastructure available before large cloud services were available. know, so early in the early 2000s and late 1990s when all of this was spinning up, there were these core services that foundations were providing that were shared resources for the projects that did require sort of a direct investment by those foundations to make sure that the resources were available. You know, there were, you know, I don't know if Confluence and JIRA out at that time, they had all these.
speaker-0: Legacy type of stuff. Yeah.
speaker-1: Right. So, and then as those became available and everyone just had their own GitHub account over here and they spun up their own environments on that cloud service provider, whatever, they didn't need that anymore. So other things took place around events, know, marketing, communications, sort of the non-technical side of foundations. maybe this was just a natural evolution as, as the demands of projects changed and get the communities changed, foundations that were already established because they originally needed to provide the same set of infrastructure for everyone. maybe it just evolved that way. I don't get the sense, and it wasn't this way at open source Congress, the organizations that were there were all very interested in collaboration around policy and also security audits. So do we all need to have our same security staff or folks that are all doing...
speaker-0: Yeah, yeah, I can see that.
speaker-1: Security assessments, CRA, attestations and software building materials and those sorts of things. Can those be services that are offered across the foundation?
speaker-0: What, ⁓ so this kind of to sum up what we've been talking about, what capabilities do you think that like foundation leaders need today to make sure that their foundation is thriving in say 10 years?
speaker-1: Well, you know, it's interesting, uh, in 2012 Wired Magazine, I think it was on the cover. I don't know if it was actually covered, it could have been just online, but it said open source has won. Now what? So I think that's the question you're asking. And sadly, I think open source won, like they said in 2012 or whatever it was, 2014, and it's been 10 years. And I don't know if we've changed or I don't know if we've answered the now what problem, but I would say that foundation leaders. foundations themselves need to shift from validating open source as a, you know, as a viable alternative to proprietary software. You know, that's been that advocacy role and also, you know, proving the credibility of the development model. Not only does the software just as good as your proprietary version, but you know, we also have, we're not just hackers in the basement hobbyists. Right? Those are the two big things is... is how good can it be if it's free? What's the quality like, all that. And then look at who's developing a bunch of jokers in a basement somewhere, garage somewhere. So shifting from that advocacy role to, and when I say business, I don't mean like revenue business, like a company corporate business, to business skills, to change perceptions of open sources and projects as partners. And again, not charities. How you engage. how a perio is trying to engage, at least I'll speak for ourselves, with institutions ⁓ is not just, hey, you're using our tools, can't we guilt you into giving us some money to keep them going? It's actually in your best interest because you're relying on this and making this sort of...
speaker-0: Don't apologize.
speaker-1: Yeah, exactly. Or expect them to apologize and then give you some money. I think instead you have to find business opportunities around partnerships where there's actually
something to be gained by both parties, right? That's what a partnership is. Right.
speaker-0: No, I like that.
speaker-1: And in doing that, the foundation needs to shift into from thinking that it's core, it's prized possession, the most valuable resource that it has, it's premier product is the software itself, and say instead that it's the community of practice around it that can offer services and not just services related to that software project, perhaps even broadly. more broadly. So the way Apparia is working with universities is that they have a project already in place, but they're looking to understand open source development models or community building. They want to understand IP. So there's a training thing that Apparia could do independent of the project. It could be any of those projects that we use, it could be that we develop, or it could be a project that we have nothing to do with. So can we create a service model that supports the projects? but also extends our portfolio to offer more to the campuses. We have a large community being in higher ed of instructional designers and faculty. And a lot of the tools that we, Perio supports are related to online learning and digital education. So can we leverage the community members that might be supporting the Sakai Learning Management System to also provide instructional design for teaching online? through any LMS, hopefully Sakai, but maybe any LMS. And so that brings a challenge back to Appereo. So no one would look at me funny if I said, hey, we should all get together and do a hackathon for a new quiz and test engine for the Sakai learning management system. Everybody would be like, yeah, let's all do that. But if I said, hey, let's all get together and develop a training session on best principles. And our principles and practices of open source development for graduate students. It's like, well, wait, why are we doing that? That doesn't, it's sort of one step away. And people are thinking, shouldn't I get paid for that? Or, again, it's bit of a leap. It's like, well, we weren't getting paid when we were doing the hackathon. We were all doing it because it improved the project. If now we could offer services that the project again got paid, it's the same community of practice. but the output instead of code is this course and the revenue that's coming back and the engagement that's happening, all the benefits are the same for the project. Why wouldn't we want to do that?
speaker-0: Right, no, I think it's a good idea.
speaker-1: So for all of the services that we offer, are there people in the community who are already engaging, setting up events, doing legal stuff and licensing work and all the stuff that it takes a project to do and a foundation to do. Can we do that, extend those services? And if we worked with other foundations, if I could bring the OSI and the Eclipse policy people in, universities right now are challenged. with issues around software building materials,
the CRA, all the sort of ones you know about, but there's a bunch of other ones. If, if a Perio for the ed tech sector was recognized as an authority, yet we were benefiting from the expertise, subject matter experts in other foundations, that just extends our service book that we can then offer to those campuses. And the money would go right back to the other foundations. A Perio would take a cut for bringing the pre-qualified lead and managing the account and all that sort of stuff. But the same thing is true if, I don't know, I'm just picking on, not picking on, I'll just mention Python. Let's say Python wanted to do ⁓ PyCon meetups ⁓ on campuses. Right? So they're doing that. That's something they've done, but they want help with understanding, you know, alumni associations and event management on campuses and putting... I don't know, credit bearing, if you get this, can you get credits for internship or whatever it might be? We have resources that could help them. So what are their options? They could go reinvent the wheel and probably not find the expertise and the experience that a Peri already has and our community has, or they could partner with us. They could deliver that service under the banner of Python. And no one knows that these are a Perio projects of people coming in. And yet they've got that contact. And we're just supporting them. So we're sort of subbing, subcontracting. So I think that creates an economic model that allows for more diversified revenue. I think it extends the capabilities and thus the value of engaging with those core foundations organizations are already working with. So company X already works with these foundations. ⁓ and now these foundations offer all this other stuff. Isn't that great? And it creates. an opportunity between the foundations because now we're all going out and finding customers for each other.
speaker-0: Yeah, I mean, I appreciate that you come up with new ideas. I appreciate that you're not talking around things. Do you know what mean? Like, and it's challenging to, in a good way, talk to you. Do you know what I mean? Like, I like it. I think that's important. So I want to thank you for that. And I do have one final question, though. So it's something that we've started. This will be the third episode. So tradition might be too big a word, but... The whole idea of the podcast really is to talk about everything but the code, right? Because that gets a lot of the shine. So it's the shout out, right? Like, can you, is there someone or a team or a project or an organization that you want to call out that's doing amazing work that doesn't necessarily get the attention that it should?
speaker-1: Yeah, sure. think I've already mentioned a couple of times. think the work that the, I don't even know who the folks are who started the open source Congress. It's the third year. It's coming up on its fourth year, but that, whoever, and shame on me for not knowing.
speaker-0: We can find out and we'll put it in the notes.
speaker-1: Whoever, right, whoever, whatever groups got together, people got together to sort of recognize the potential of a collaborative community of practice around non-code issues to foster collaboration and co-creation and shared resources, I think is fantastic. think last year when I left was the most inspired I've been about. the potential of the next phase of open source where open source foundations begin to operate like the projects they support. willingness. the organizations and the people in attendance to raise their hand and say, yes, we think we're experts in this, but no, we're not in this. And we would love to support those and how that community of, mean, it really felt like people use community a lot, but it like, Hey, we're all in this. We all sort of recognize the same thing. And is there an opportunity now to really work together and, you know, leave our name tags or something at the door. And we're just really thinking about open source. We're not thinking about our foundations. So I know last year Eclipse ran it. So Mike Malinkovich and I know Deb Bryant was very involved from OSI. So I definitely give them a shout out. I know they were working a lot, but I think the two takeaways was that there's definitely areas and there's already some outputs that have come out from that, from the open policy Alliance that was formed out of that. ⁓ so, yeah, I think. I think they're probably unrecognized because ⁓ it's happening just sort of quietly, which I think is good. There's no fanfare around it. And I also think nobody's trying to leverage that group for a sponsorship or foundation recognition or anything like that. think it's like everyone just rolling up their sleeves and getting to work.
speaker-0: Awesome. So we'll make sure that we put that in the description so people can check it out. Great. And that's it for this one. Thanks again.
speaker-1: All right, so thank you so much for the invitation and your interest and your help and best of luck with this. think this, I think the podcast is, I like the idea this as a non-technical, especially with what we were talking about, but I think it should be a great forum for all sorts of interesting discussions to start and then hopefully find an audience and get the more people involved. thanks for opportunity.
speaker-0: Thank very much. You