 Hello, everybody. My name is Daniel Crook. I'm the CTO of Call for Code, the Global Initiative as well as Code and Response, which is a program that we have at the Linux Foundation in partnership with IBM and many other partners like the United Nations and sponsors like Slack, Arrow, the CNCF, another Linux Foundation organization, and many other small and large partners. I'm here today with Derek Thier, my colleague. We're going to talk a bit about the Code and Response with the Linux Foundation umbrella project, and we'll talk exactly how projects enter into that program as well as how developers can take part in some of the projects that are there or even create new ones as part of the Call for Code competition. I'm going to start by talking about the Call for Code program, and this is, sorry, just having a little issue with the slides. Oops. There we go. I figured out the slides. Sorry about that. Let me talk first a bit about Call for Code. Call for Code itself is something that IBM launched with the Linux Foundation as well as United Nations just over two years ago. It's a partnership to not only be a five-year program but also to host a yearly Tech for Good competition, and it's the largest of its kind in terms of participation from developers around the world. The goal with the competition every year is to create open-source projects, sustainable projects that have a sponsor organization, the creating team normally, as well as an open-source community around those projects so that they can make a difference immediately as well as long-term against some humanitarian issue. In the past two years, we focused on what can technology do to mitigate the impact of natural disasters, and this year we've launched with a scope around climate change and COVID-19 solutions, which I'll get into a little bit later in the presentation. But the goal is that we inspire developers over the course of about four months to learn about that important issue from experts, from organizations that know much about it, what the real problems are, how technology might help, and how to measure their impact. What we do with Call for Code is pair developers against those real-world issues. For example, in the case of natural disasters, that would have been the Sendai framework that comes from United Nations Disaster Risk Reduction Organization, and this year with climate change, it's focused around the UN Sustainable Development Goals for 2030. Now, the competition puts forward a theme, a global challenge, and the five winning teams are recognized from the competition. All five get support from the Linux Foundation, help them implement their project as open-source projects, implement some best practices for how to run an open-source project, such as having a code of conduct, contribution guidelines, as well as raising awareness through foundation events just like this one. So there's a cash prize, of course. There's that open-source support from Linux Foundation. Then there's also, through the Code Response Program, folks have access to the IBM Service Core, a set of volunteers that can be drafted to fill in gaps on the submitting team. For example, if they need hardware experts, if they need software experts, user experience experts, designers, branders, things like that. So the winners of the competition win, not only the competition, they don't just go home, take their cash prize and go home. Code Response with the Linux Foundation provides that way to ensure that every call for code winner has the ability to be deployed out in the field. So innovation coming from around the world and the support to make those ideas real. So I've mentioned two programs so far, and just to be clear about what those are, call for code is the competition, is the yearly competition. Code Response with the Linux Foundation is the project for incubating those ideas. So they come in from call for code, for example, last two years, grand prize winners, as well as some of the runners up, and other interested projects that are open-source come in. We help them build out the solutions, matching them with the skills I mentioned earlier, as well as helping them achieve some non-functional goals, doing some security audits, helping them scale, things like that. We help test them. Derek will talk a little bit about some of the extensive testing we did with the 2018 winner, and then we help them graduate out by implementing their solution, kind of getting to a milestone where they're either a sustainable company, maybe they've got their first sale or first contract with some partner organization, or they just generally have the ability to keep on sustaining themselves as open-source projects. So as I mentioned, we are in our third year of call for code, the second year of code response, and the team that won the first year, they created a really interesting mesh network, an ad hoc mesh network that could restore network access after a natural disaster, and it's really about quickly and cheaply restoring that access, and getting to just about 1% connectivity, which is much better than 0% connectivity. When you're trying to get just short emergency messages over the network, you don't need to stream Netflix, you just wanna get some basic text messages over the network with what's already built into the phone or into a PC, because the network access is actually a lot harder to restore than power, power you can have generators and solar and things like that, but it's connectivity that's really been the big challenge after many natural disasters. So let me hand it over now to Derek to talk specifically about the Project OWL team, as well as how code response helped them bring their idea to life during several tests. Thanks, Daniel, appreciate that. So like Daniel mentioned, call for code 2018 winner Project OWL, they have a fantastic IoT based solution that creates a mesh network for people to be able to reach out to first responders. So it's not just the open source hardware that they're using, but they actually have their own DMS, their data management system, running on IBM cloud that they have, and that's kind of a really value add to what their solution is. So not only can you take what they have that's open source, but they also have software that specifically is meant for people to reach out to first responders. And I think it's a really phenomenal idea that they came up with, and it only got better when we use the IBM service core to do this deployment. So like Daniel said, we have the IBM service core where we get volunteers from within IBM from all over the world. We source the best talent globally from within all the volunteers that wanna be involved. For Project OWL, we had people from Israel, from the UK, from Canada, from the US. So it was a very global project. And we brought those people in to Puerto Rico where they had two weeks on the ground there. These are some of the photos you can see in this slide. And basically what we did was we took Project OWL's idea, we brought in the best of the best from IBM service core and we helped them fortify their solution, their software, their hardware to make sure that they had the best product that they can because they wanted to test this in Puerto Rico after being inspired by Hurricane Maria and knowing that people didn't have connectivity there, they wanted to do this and test it in the field. And that's a really cool thing about what Code and Response does. We don't wanna just say, here's the money, thanks, it was great, have fun. We wanna make sure that these companies and these startups and these ideas can grow. And really that's what we did. We did pilot tests in Puerto Rico for two weeks. We were in, Bayamon was our hub, kind of the center of where we were at Engine 4 which was a great co-working space for us. We did some pilot tests in Loisa, in San Juan and Isabella in Comerio. We were also in, I think, Dorado, we did a few tests. So it was great to be able to test this in a wide variety of environments. On the beach, in the middle of the mountains, finding out what impact the environment had, humidity. All of these factors that were, you can try to plan for them as best as you can in your head, you think about doing these tests. But actually being on the ground to test this stuff was phenomenal. And we had some really other great partners as well, ITDRC, which they were instrumental in helping us and Project OWL come up with the best places to test, to look at the actual radio spectrum and determine how things were working, if we were getting interference, anything like that. So it was phenomenal to do. We also had some really essential partners, the University of Puerto Rico, Johnson & Johnson, some local government help as well in San Juan, Bayamon and Isabella. And throughout the course of 2019 as we did this, we also did have a documentary about this, which is really cool. So just a slight little plug for that. If you're interested in that, take a look at our coding response documentary on Project OWL. There's some really cool behind the scenes stuff and just some great footage. You can see our progress as we did this in Puerto Rico. We, between IBM and Project OWL, I think we were in Puerto Rico about a half a dozen times in 2019 working on this. They made additional visits to other parts of the island like Umacau and Mayo Huez and Aguadilla. Great places, again, to continue testing and further building relationships. And the slide here you'll see is where Project OWL and IBM, we engage the students from the University of Puerto Rico in Mayo Huez. And the great part about that was that we had an enthusiastic group of students that were interested in learning about leading edge technology. And so we took what we were working on with Project OWL and helped them understand the hardware, the software, how to set things up. We partnered with the school to actually set up these devices on the top of numerous buildings. And the students got to learn how it works. They managed the devices out there. It was a really awesome opportunity for the students and for IBM and Project OWL. And the outcome from everything that we did with the service core, with Code and Response, we helped improve Project OWL's technical architecture and their solution, created a ton of connections and valuable resources on the island of Puerto Rico with people that are always willing to help us so we can help them and give back. And then they've also, after working with all of us, they've continued the iteration of their product and their software after the service core. So it's great to see Project OWL grow from the winner to the deployment and implementation and then further continuing on as their own company where they're killing it. So really, really cool opportunity with Project OWL. I'm gonna hand it back to Daniel to talk a little bit about our 2019 winner. So Daniel. There we go. All right. Great, hopefully you can hear me here. So there was a question I saw in the chat already. Derek, maybe you can answer that. Somebody was looking for a link to the Code and Response documentary on Project OWL. There's a 15 minute documentary, which is the one hosted on IBM.com. And there's actually a feature length documentary called Code and Response, which is at a higher level about the program. That's also something that's interesting to take a look at. You can find that on Amazon Prime as well as a few other streaming services. Okay. Great, looks like we got side by side. So that's good. Let me just in there. So let's talk now about the 2019 winner. So this was the team that came through the competition last year, a team named Prometeo from Spain. And what was really interesting about them is that there was, as opposed to the Project OWL team, which was already a set of developers that knew hardware and new IoT, what was really inspiring about Prometeo is that their team comprised of a full stack developer and a data scientist, but they also included a firefighter, a nurse and a PhD engineer on the team. So they were able to come to call for code with a great application that was something that could measure the effect of certain chemicals on firefighters in the field and ensure that incident commanders could see exactly what was going on with a set of 10 firefighters, but also track the exposure over time with the end result being that with a small device with many sensors on it, you can really help make an impact right away through an open source project. And it's something that can scale beyond what it was built for in Catalonia to actually go scale around the world to Argentina, to Australia, to Norway, to California, other places where folks are exposed to similar types of toxins when doing controlled burns or working with wildfires directly. So for this one, let me hand it to Derek, take audio and talk a bit about the team itself and what we had done with them with a field test and some of what the future holds for what they're doing today. Thanks, Daniel. So again, this was another phenomenal idea that came out of call for code to be able to monitor specifically wildfire firefighter health. This was a new area to me where I didn't realize that wildfire firefighters in particular, they might be out in the field handling a burn for days potentially. So they don't wear oxygen masks and carry tanks and things like that. So this was kind of a gap where Prometheus came along and said, look, we need to watch out for these firefighters and have a device that can monitor their immediate health but also have access to a history of their health over time. And so it's pretty incredible because they had a device similar to what Project Al was, the same IoT board, and they were just using it a bit of a different way, but they were still monitoring smoke concentration, humidity, things like that. And it was incredible to see the passion that this team had. And again, this just goes to show that call for code is not just for developers. It's not just for technical people. Like Daniel said, one was a firefighter, one's a nurse. It's great to bring people that are experts and bring them together to create a cohesive solution. And I think Prometheus, the epitome of that. We did the prescribed burn or this field test back in February of this year, right before all the COVID stuff kind of happened. And it was incredible to see this in action because we got everything set up. You'll see in the photos here, we're in a big tent that the firefighters set up for us. And they did a controlled burn, got some great drone footage too. And we were able to kind of watch them do this controlled burn, but also monitor what they were doing on this wearable that they had that Prometheus came up with and saw live what was happening. The cool part about this was, and we talk about the importance of open source and tech for good. As we looked at Prometheus and what they were doing with everything, we kind of looked at it and said, hey, let's kind of involve Project Owl from last year because they have a year head start working with a similar device. They've probably learned some really good do's and don'ts and learn things the hard way and have some really good experience with it. So we actually asked them if they wanted to be on site for this and kind of show Project Owl the art of the possible for what they do. Because, I'm sorry, it's Prometheus, the art of the possible, I apologize. Because Prometheus was using a Wi-Fi based technology where Project Owl was using Laura. If you're familiar with Laura, it's a long range low power Wi-Fi connectivity. And so we said, hey, why don't we take this because this will expand what Prometheus can do. We can take the expertise from what Project Owl has learned from this and integrate it together, which is exactly what we did. And that was really cool to see. We had two teams from two different winning years come together, work on something and be able to have it work live in the field. And we had a pretty simple integration process through our IBM IoT platform that made that possible, which is pretty incredible. And we did some really awesome long range testing of how far could these sensors work. We flew one up on a drone like half a mile away and like a quarter mile up. And it was amazing to see just how amazing this technology was and how it all kind of worked together. And again, we involved the IBM Service Core in this project as well. Here's some photos from the prescribed burn, pretty amazing time. One of the coolest things I've probably ever done in my career. But the IBM Service Core has been engaged now. We are just battling the COVID-19 stuff. So right now the work is being done virtually with an onsite plan either later this year or sometime early next year to be able to do exactly what we did for Project OWL and go onsite in Catalonia and do some more prescribed burns and some testing and gathering firefighter feedback. And the thing about open source and tech for good and the way that these solutions can really help people is it does attract some attention. So, Prometeo is exploring options with a large electronic manufacturer looking into edge technologies to do some of this processing on the device instead of doing machine learning on the cloud. So there's some really, really cool stuff that kind of came out of this project and just further goes to show how important it is to focus on tech for good and things like this through our code response program. So, Jayne, I'm gonna hand it back over to you. Great, thank you, Derek, much appreciated. And just to echo a key part of what Derek said, open source was key to not only improving Project OWL solution, they've got a very vibrant project, the ClusterDoc protocol. If you see that on GitHub, I'll give you a link at the end of the session. They had a similar platform and they could bring that year-long headstart to Prometeo, I'm sorry, and use that technology to improve how it can be built forward. And going forward with Prometeo, we're working with them to go to the third-gen platform. We are transitioning to their repose out in the open source organization, breaking out their version one, their version two, and consolidating on a version three or at least three, that's gonna have additional sensors. So the focus for the field test was carbon monoxide, but through the community, we're sourcing new designs for seven new sensors, which will include things like nitrogen dioxide, acrylene, formaldehyde, and benzene. Because these are controlled burns, they actually start them themselves. It's kind of ironic the firefighters starting fires, but to get ahead of any wildfires, what they do is start and they've got a very highly toxic accelerant with benzene in it. So working with those, and hopefully by the end of the year, we'll have a third iteration of that and we'll grow the community out as well. So let me shift gears a bit to this year's program and then talk to how you can take part and maybe you could become the next code and response of the Linux Foundation project. If you place the top five, but we want you to be aware of what's there too and invite projects into the Linux Foundation under this umbrella, even if they don't come through the call for code challenge, which is the case of one promising technology that's gonna come within the next six weeks. So call for code, you can learn about it at this URL below. That'll take you to the ibm.com page where you register for the competition. And then there's the call for code.org site has information, the canonical rules, the judging criteria, the timeline, things like that. But as I mentioned, call for code does focus on some of the world's most pressing challenges. And when we launched earlier this year, we really expanded out the impact of natural disasters on humans, wildfires on firefighters, for example, to look at more of the systemic causes. So we launched in partnership with the United Nations who are in their 75th anniversary this year, as well as with the 10 year countdown to the sustainable development goals. We launched with a focus on climate change. And it's really something that is such a powerful issue. It affects people around the world. It's something that's growing. It's something where action needs to be taken immediately. So it's really something that we have to keep an eye on and to conceive of new solutions to it. So we launched with climate change, with three sub themes of water sustainability, energy sustainability, and disaster resiliency. But we also recognize that there was a growing pandemic that was a much more pressing challenge, one that was having a more immediate and visible impact on human lives. So we added a COVID-19 track to this year's call for code competition. It doesn't focus on vaccine development or medicine research or gene sequencing, things like that. It's really about understanding the social and business issues out there that can be improved by technology. And I'll get into some of those sub themes shortly. So we do have both themes, developers can create solutions for one or both tracks and some potential solutions for an immediate impact of COVID-19 may be also something that's helpful in future pandemics or also as part of climate change type of activities. So there is a bit of overlap and very excited to see the solutions that come into that. So looking specifically at COVID-19, the focus of call for code is to bridge that gap between experts on the particular issue as well as the technology that can be used by the world's 24 million developers to actually make a difference and make sure they're solving the right problems. So what we do with call for code is we call out a set of sub themes. And in the case of COVID-19, we make that abstract issue more concrete by asking developers to focus on crisis communication solutions, perhaps how to create bots for managing overloaded local resources or understaffed supermarkets that need to manage and how information is shared. Remote education, right? So I don't know if you hear in the background here but my son is doing tutoring in the other room over Skype. So just finding ways for folks like him who are lucky enough to have his own iPad but also people are offline, don't have access to computers, what potential solutions are there out there for students and their parents and their teachers. And finally, community cooperation. So how do you make do in this new economic environment? How do you share resources, share information, really track and know the risk from the pandemic around you and understand how you can make a difference and really again, make that abstract now to something concrete that someone can do with technology. I touched on it earlier, but water sustainability, energy sustainability and disaster resiliency are three key pillars behind our climate change track. So understanding the impact of what someone can do, giving them information on the best way to conserve water, make better decisions about how they water crops. For example, based on future weather trends, energy sustainability, so making buying decisions, tracking your own consumption, making sure you're focused on the real things that are consuming power, maybe rather than things you think consume power. So looking at great solutions there and disaster resiliency. So going beyond natural disasters as in the first two years but also manmade disasters, climate related disasters, things like that. So both tracks each have a sub theme within and the price structure is very similar to what we did in prior years. So $200,000 for the top team, $25,000 for the two runners up and then the fourth and fifth place teams get $10,000. All of them get some mentorship from the Linux Foundation which can also connect them to other communities and some potential funding and mentorship opportunities. And by joining this, you'll be able to work together with folks around the world within the Linux Foundation as well as students, small and large institutions around the world. So we're really looking forward to seeing how this community grows and improves year over year to improve the previous year solution but also inspire new innovation on top of that. So just a look at the timeframe for call for code. We launched it in February with climate change, the track there, we added an early track for COVID-19. We decided to recognize the support three projects early. So those are also projects that are starting to work their way into code response with the Linux Foundation. One of them is a really great solution called SafeQ. Maybe Derek can provide a link to that in the chat but it's one of those ones that's really having a great impact already. It's being tested in the field right now with support from code response, really great stuff. But you can continue to develop applications for the competition through the end of July. So you've got 30 days left. Judging will be done by experts from around the world. Earlier for the, actually the early track we had Mark Cuban as one of the judges. We had experts from the United Nations. We had experts from local organizations, law enforcement, climate change experts, disaster resiliency experts, really to take not only a view at the technology and assess that but make sure that it's something that is relevant, transferable, feasible, solving the right problem. So again, looking forward to highlighting these applications in October and beginning their deployments in 2021. Hopefully when we're back, able to do group events and beyond the ground. Actually, yep. So here were the top three, SafeQ. RU Well was another great application which was a way to connect folks with medical resources in the communities and focusing on the situation in India, ensuring that that location is not overwhelmed. It's medical resources are not overwhelmed. They're already experiencing quite a bit, especially Mumbai. There's a lot of overloaded medical institutions there right now. So this solution is being iterated on through Outran, the team that created it as well as with support of Anthem, a large insurance company and other partners. And COVID impact is a way in Canada to connect small businesses with resources, grants and other information that may apply to them so they keep resilient through these tough times. So look out for those applications. They also remain eligible for the global competition. Okay, so if your developer wants to take part, there's four steps. You accept the challenge, which is registering for the competition. You've got access to open source technology. Most of what's on the IBM cloud is based on open source. I think it's 80% at least. So if you're working on Docker locally, you're working in Kubernetes, you're able to take that and host that up on the cloud. Same with OpenWISC, Knative, a bunch of open source platforms, open source technologies are able to run there. You can find teammates through our Slack community. As I mentioned, Slack is an affiliate. They've helped us get a nice community in there. I think there's six to 8,000 folks in there right now, all kind of collaborating and looking for teammates, working and learning about the technology, sharing information. And then finally, at the end of July, submit the idea with up to four other team members and we'll rate the highest ideas that come out of there through the judges. So we do also, as a way to bridge that abstract challenge like climate change or COVID-19 to some feasible use case, we have what are called starter kits. So these carve out one particular use case around that larger sub theme and give you a starting point. For example, you wanna learn how to make a bot, run an offline learning platform, learn what data sets are available for energy resiliency, things like that. There's a whole set of starter kits there. They basically make the abstract real and give you a great starting point. There's also, if you already know what you wanna build, just dive directly into using some of the IBM cloud services, open source data sets. We've got a list of things from around the world that come from lots of different sources that you can use in your Jupyter notebooks, for example, and connect with your open hardware-based systems using it. Again, within the Slack channel, I see there was a question about how do you get an invitation to join the Slack channel? It's a great question. So if you go to callforcode.org slash slack, there's a type form that'll get you an invite. You accept the code of conduct and then it'll send you an email and how you can join. So there's channels for each of the themes and sub themes and you can reach out to IBM mentors in there as well as experts from lots of different companies like here, which is a location-based service and there's a couple of other APIs and things you can learn about in there as well. And it's one thing to create an amazing solution based on all those resources and solve the real problem, but you've gotta also be able to communicate why your solution is different, what problem you're solving, how you're gonna measure your impact. And given that we do have all of these widely skilled judges that aren't just technologists, that aren't just open source experts, but that are heads of NGOs, you really wanna be able to understand the issue you're solving. Try to speak in a common language that appeals to everybody that can quickly understand your idea and then document it very well. There's a starting project sample that has a good skeleton repo based on some of the Linux Foundation best practices you can start with. And that includes some tips around the video and deeper documentation. But it's really just like with SafeQ earlier this year. The value of that was evident that the innovation was quick and amazing just how fast it came together based on a starter kit and it really hit the judges with a nice demo. So that's why it was really a top solution to look at. So you can go check out, as I said, callforcode.org, that is the multi-year initiative page that has information about what the competition is, the rules, the judging, the judges themselves are gonna be listed there. And it also has information on what you need to submit the FAQ. And if you're not just a developer but that you also want to perhaps join as an organization, there's information there on how you can join the ecosystem, sponsorships, affiliates, no cost, supporterships, things like that. And there is also a corresponding Linux Foundation page that links to a couple of the projects we have right now. It highlights just two right now. So the cluster doc protocol, which is the one that came out of Project OWL, it's their open source firmware. And there's also a link there to Drone Aid, which was another very interesting solution that came from one of the first call for code events we did in Puerto Rico two years ago. And this is about solving the problem where folks, you've probably seen it in the news, I know in Houston it was big news, Florida, Puerto Rico, but folks who are disconnected from networks, how do they express their needs to helicopters, to drones, to civil aviation, to satellites, they've kind of put together logs that say help or write help in the sand sort of thing. What Drone Aid does is it sets up a common language based on the UN OCHA standard icon model and trains a visual recognition model that can be put into a drone, again, just take live feeds from satellites or whatever it is to identify the need expressed by somebody on the ground at a specific location and speed some help to them. So a couple of great projects there. There's many other projects that are so in the works in the other ones are in various states of iteration right now. Liquid Prep is one that came from actually an IBM internal competition. They are starting a service core deployment right now they're connected with some organizations in India to test their device. It's one of these that helps give farmers advice on whether they should water now based on weather forecasts and Isaac Simo is one based on a previous year winner as well. It's for assessing building construction quality ensuring that people who've had improvements done to their home through an NGO and particularly in Columbia can prove that the work was done well and if they can safely go back into their homes. And one of the ones to keep an eye on is this open EEW open earthquake early warning earthquake warning system project. You'll be hearing about that one pretty soon. They're coming to Linux foundation as well. What they do is rather than a multimillion dollar earthquake warning system that's at the national level they sell a small or create a small open source device that has a very highly sensitive accelerometer in it. So it scales out where the sensing of earthquakes are such as in Puerto Rico where we have a few installed and get folks alerted 30 seconds to a minute ahead of where they might be affected. So really promising technology, a nice portfolio of what's out there. You can contribute to them, you can join the conversation but yeah, again, if you enter a call for code with an idea and you win, you'll get really some hands on support to take your idea forward. So with that, let's open it up to some questions. I saw some that came into the chat and I'm not sure if Derek caught any of them. Yep, so Derek provided a link to the 18 minute documentary. That's great. And he's got a link to cluster doc, right? So they've got their solution. They've got how you can assemble one of these devices. They're continuing to add additional device support. They started with the ESP32 board. I think it was a hell tech. I don't know, it wasn't 100% reliable. So they're always looking for different platforms. So the community has been able to help them be more abstracted from the specific implementation. If you have any hardware expertise, go check it out. Try to set it up yourself and contribute to it in other ways. You can build an ecosystem of other things around that to kind of help visualize where the information comes from. All right, so Derek's got save queue in there. We talked a bit about Slack. Sounds like we've got that one handled as well. Okay, if you have any other questions, drop them in the chat. Yeah, it's interesting the question. There's a question there about a copy of the presentation which I think. Yes, I do have that actually. That's always the first question I get. So I already put it up on SlideShare. So let me actually ping that in the Q&A. Okay. So anything that you wanna send to them will go to the Slack channel. Okay. Oh, I see, yep, you have the chat there. Okay. Let's see, I can post them in the Slack channel, but if you go to slideshare.net slash Daniel Crook, my full name, you'll see the slide deck is updated there. And, okay, there we go. So the channel is, if you're in the OSS Slack, two track open source project updates. And again, to join Slack, it was callforcode.org slash Slack. And gethub.com, go ahead, Derek. So I think there's like a substantial lag here. So I apologize. One of the other questions in here just says, if you enter that you're not a winner, can you enter again in a subsequent year? And the answer is yes, yes, you can do that. So the theme might change every year. So a solution that you might build for this year might need to be adjusted for the following year. It could be something completely different. But yes, you can do that. And additionally, we made it so that, you know, if you're doing any other hackathons or events like that, you're able to take your solutions that you're creating for callforcode and use them elsewhere as well. And I should mention too, there is a fresh code rule. So whatever you do submit, should be fresh for the new competition, but it can build on anything that was open sourced and available to anybody else at the start of the competition. So if you've got node module dependencies, if you have datasets, if you have your own code or if you're building on a previous year's winners, you know, those are all fair game to build upon. But your code's got to be substantially new. It can't be a project that you created privately last year. You know, a whole new thing that you just submit. It's got to be a new idea or a new set of code that you're submitting. And as you submit, since the goal is to create sustainable open source projects, we ask all winners as a condition of accepting the prize, they patch you to license their projects. And they can form business models around them as Owl and Prometeo have. But yeah, you make your code available through the program. Great, I think that's it for the questions. So again, for follow-ups, so if you go to github.com slash code and response, you can find the repos and then in the Slack channel, there's actually two Slack workspaces. One is the Golf Code one, which is golfcode.org slash Slack, but the open source summit Slack also has its own channel. We'll put the slides into both areas so that you'll have those. Great, and with that, I think we're all set here. So thank you very much for attending. Look forward to seeing some of your applications. If you could participate in Golf Code this year, or even those issues open, the pull request sent to some of the code and response repos already.