 So I worked for IBM, and we launched this program together with other partners. It's not just an IBM initiative. It's in partnership with the Linux Foundation, the United Nations Human Rights Office, and David Clark-Cawes, who's a fellow that helps rally eminent individuals to raise awareness of important issues, whether that's global health, disaster response, or veterans issues. So we have a great ecosystem of partners in call for code. And what we like to consider about call for code that sets it apart from other tech for good initiatives is that there is support for the top-winning teams to deliver their solutions, not only get recognized in the competition with a cash prize, but also to get mentorship so that their project can develop sustainable open-source communities that are very vibrant, that have users and contributors from across the world. And so now that we've entered our fourth year of the global competition, we've got some great technology to show you from past winners. And we also have a whole bunch of other call for code solutions that are in various states of maturity, either as a field Linux Foundation projects with the call for code umbrella, or ones that are just rapidly innovating today that you can observe and kind of keep tabs on for when we invite contributors to those projects. But we do have a bunch of them. They cover all sorts of technology. So whether you're interested in artificial intelligence, internet of things, data science, web application, serverless, mobile applications, there's usually a problem area or technology that can appeal to just about anybody who's interested in open-source technology. So over the years, we've had almost half a million developers take part either in the multi-month, single-yearly global competition, or through some of our other initiatives together with Linux Foundation and other partners to take on specific issues, things that we call spot challenges. And those are issues that arise outside the global competition. So if you are familiar with call for code, you may have associated it with certain competitions. But be aware there's more to it than just that. And we've had participation from around the world, 179 nations so far. And I don't think we expand too, too much farther than that, but there are developers that are new to competition, have been involved in the competition, and we're really excited to see that growing community, that international community, which is a really key important thing about open-source. Now, we did launch in 2018. Our focus then was on preparing, responding to, and recovering from disasters, mainly the natural sort. And we have over the years had other themes come through. So some of the applications are focused on those areas, other focused on different challenges. But the first year, we focused on natural disasters. Project DAL was the team that created an emergency mesh network, something that was cheap and easily deployable after a disaster, inspired by what happened in Puerto Rico after Hurricane Maria, where some folks didn't have network connectivity restored until almost nine months later. Power, sometimes that's easier to get better and back online easier. But network communications, after the fact, as well as during the emergency are very important to be done and to deploy that quickly in a way that folks can have access to that technology, very important. So Project DAL's technology was open-sourced as the Cluster.Protocol, and I'll talk about it a little bit more detail later. The following year's winner, Prometeo, they also took on a solution for mitigating the effects of disasters, in particular, looking at wildlands firefighters are battling wildfires in Spain, in Australia, in Argentina, in the United States and elsewhere around the world. So we've been working with them also to bring their technology to the open-source community at the Linux Foundation. And our third global challenge winner, they were recognized last year, and we've been working with them to take their solution to the open source community as well. So their solution was in response to the call for code global challenge prompt around climate change. So in the first couple of years, we looked at the symptom of disasters. And in the last couple of years, including this year, we focused more on climate change and the issues driving disasters. Last year was a very unique year. We had the pandemic, so we launched an additional track for the social and business aspects of the pandemic. How can you create technology for emergency communications, for community cooperation, remote education, social distancing? So another project that was a great piece of innovation built on open-source technology, including cloud foundry, React Native for targeting Android, as well as iPhone devices, was an application that's still under development in test, but it's out there. If you've heard of it, it's available as a web application for anybody to use today. And that's called SaveQ. Also very important, starting last year around this time, there was a large emphasis around, how do we handle the impacts of racial injustice? Is there a way that technology can make a difference? Can be used in such a way to drive more equality. So another program is call for code for racial justice. And within that program, we have seven open-source projects where folks can learn about a particular issue under one of three sub-themes and look at ways that they can get involved in those communities as users of the technology or to contribute to them as well. Now, I mentioned earlier that what sets call for code apart is this idea that it's not just about putting a project prompt out there or inspiring people to go use technology to go win a competition. With call for code, there is the Global Challenge Prize which I'll talk into a little bit more detail later. There is that mentorship and best practice provided by the Linux Foundation. IBM assigns an IBM service core, volunteers from the company across the world or experts in hardware, software, branding, marketing, logo design, user experience, all those sorts of things come together to support the top projects. And eventually what they do is graduate out into some sort of sustainability, either as a startup that's built a business around technology or if it's an NGO, a non-government organization, a nonprofit that is creating something core to their mission or maybe it even becomes part of an enterprise company's product line, but it's based on open source. So the call for code competition is really about the idea creation. We also have a deployment framework and this is where the Linux Foundation is incredibly important. Is it helps us develop an ecosystem of partners who can help improve the technology, provide feedback, provide expertise. And we take it from being raw innovation at the competition period. We work it through improving non-functional functional requirements, making it easier to use, considering different use cases. And we test it out in the field. In COVID, we actually did go to Puerto Rico with Project DAL. Or testing from Ateo with firefighters or working with farmers in the case of Agrily. So it's very important that these projects are not only inspired to build amazing innovation, but before they're opened up to larger contributions from the open source community, that we validate the core functionality of the project so that when we invite folks through the Linux Foundation model to take part, there's really clear ways to get involved and to deploy it on your own where you might want to have it take on a challenge in your own area. And finally, implementation. So we have a lot of great teams out there that can give you kind of feedback on their experience as well as help you use that technology and mentor you in turn to create your amazing innovation on top of those open source projects. So I mentioned call for code. IBM is the founding pick partner. So we provide the technology, the United Nations and other UN organizations to help us formulate the prompts, tie them back to sustainable levels. But the important part of Linux involvement here is if you go to Linuxfoundation.org, look up the projects, you'll see that we have an umbrella. It's called call for code Linux foundation, easy enough. And you can see the current list of 12 projects that are neutrally hosted right now at the Linux Foundation. And by going to that page, you can dive into either the generic call for code Slack, which has channels for each of the teams, the supporting organizations behind these open source projects. And you can drive into the GitHub organization as well. So some of them are hosted under a call for code, I'm sorry, github.ibm.com slash call dash four dash code. Others have expanded out to include more repos that are in different organizations. But if you go here, this is where you can learn about the ones that are official projects ready for contributors, as well as ones that are working through that maturity, incubating funnel right now. There is also a parallel organization for the call for code for racial justice projects. It has its whole set of other related repositories, including links back to the CNCS inclusive naming initiative. So you can learn about the technology there. We do also as IBM provide on our developer website, a way to understand these projects a little more depth. We've got videos, we've got interviews, we've got other documentation where we can learn about the story of how these projects were created. And you can dive in and contribute to them in GitHub as well. And there are links in all of these repos to Slack and also so you can see some licensing details. The Linux foundation focuses on Apache too. So most of these are Apache to license, except where maybe they build upon additional datasets, things like that that are differently licensed. And whatever you don't find in GitHub, we normally have something on IBM developer that addresses one of three types of users of that open source technology. If you just wanna learn about the technology, understand the issue and potentially just consume it in your own texts such as understanding how a mesh network works that you wanna put one together. You wanna build the skills and IoT to go do that yourself. We've got materials for that on IBM developer. You can learn about the specific projects and how you might get involved, what they're trying to solve, what they're not trying to solve and hands on with the technology. And finally, they all have contribution guidelines that adhere to the best practices from the Linux foundation. So they include a code of conduct, they include some details on how we handle pull requests, how we respond to issues and who the technical steering committee members are behind of each of the projects. So the decision makers who will guide them in the projects and contact to learn more about the project and potentially earn your way into committership in each of the projects. So now that you understand the general structure of what call for code is and some of the ways that we handle the innovation let me dive into a few of our specific examples of technology that's been generated by the competition as well as things that have evolved since. So to do that, let me start with the first year's global challenge winner. It was a team that submitted for the challenge which focused on natural disasters, how to prepare for, respond to and recover from them. And what Project OWL did was they built a way to deploy really cheap IoT devices quickly, cheaply throughout an area that's dealing with the natural disaster, something that can not replace the infrastructure or not the commercial projects that were out there beforehand but things that provide a niche where they can come and provide a quick solution. So this is not a major infrastructure for the internet. You're not gonna run broadband over their mesh network. It's not something that would take weeks to deploy such as a satellite or a weather balloon sort of solution. And what they created was a set of a softening mesh nodes that use long range radio to connect with themselves, assign their own roles in a mesh network and which can be connected with solar and sorry, it's solar and other productivity so that in case there is no infrastructure they can still operate as their own basic network. And what really sets this apart too in the context that they developed it is it provides end use that they can access from a mobile device without having to download a specific app. Essentially what they've done that's really innovative is they take advantage of the built-in active portal that is in mobile devices, that thing that prompts you to join that works at a hotel or at a coffee shop, things like that. And they use that, they provide their interface through that. So instead of providing a password and details to join a network, you're actually building on that to send information over it in a unique way. So they call for code, they open source their core mesh network technology as clustered up protocol and as a startup they continue to build software as a service around the dashboard for understanding the messages that are coming through the system as well as how folks can best respond to that as a commander in a disaster. They've got some really great documentation put together now that they've built out their community from the innovation through to different ways to deploy different types of networks in different situations. So you can learn a lot about what their naming is for the ducks that form different roles in the mesh network. You can learn how to run it on different types of hardware on just ESP32 boards that they started with. And in fact, they've got some great stories too around some of the testing they've done. Long range radio has a certain terrestrial distance it's affected by things that radio is concrete and humidity and altitude and topography, but they've done some really interesting stuff in terms of merging this with satellite solutions by launching some weather balloons to do Laura over really long distances up at certain levels of the atmosphere. So really a vibrant community, a great set of folks to get involved with and people are using this technology in lots of different ways. The students from California Polytechnic Institute are using it for that upper atmosphere testing. You've got folks that are using it to manage their vineyards in California and you've got folks obviously testing it and having ownership of the technology in Puerto Rico itself where it was originally developed. And studying on this journey is that as a top call for code global challenge winner we connected them with public and private partners in Puerto Rico. We base ourselves at one of the great innovation IoT labs they're called Engine 4 and had them test their technology in various conditions that represented the hardest areas by Hurricane Maria. So testing on very humid beach conditions, dense concrete built up areas around San Juan as well as in mountainous regions in the middle of the island in Conorillo where there's lots of valleys and they had the hardest challenges with network connectivity restoration and other areas around the island. And so they through this testing process with folks that we assembled to help them they continued to test their technology and test it in various locations as well as provide a way for stakeholders on the island to have an ownership stake in that tech to learn the skills to maintain or recreate these notes. And what's really a great story about this is there are students involved that are learning tech skills, IoT skills, open source technology, web application dashboard technology and also having ownership and a stake in this potentially life saving technology. So there's about 30 nodes on the island today all continuing to emit back data. Solar powered connect satellites some of them a way to test out the technology for future incidents. And so if we look back at the 2020 year review there's been some great innovation this year as well in the call for code community around Project OWL but really it's about understanding from that announcement from their open source project last year through where they've grown what they've done to refactor the technology with the help of the open source community including making their network more reliable making it more as well as improving and making more efficient their message format that they're sending along the network. So really they're really looking for additional developers to take it forward. You can learn about it at cluster.core.org also the link from the link foundation page and take a look at some of the open issues take a look at that documentation and dive right into that community. I know one of the really big things that they're looking to improve is how you can independently test this without necessarily having access to hardware. So for those interested in simulating MQTT messages building dockerized solutions containerized solutions those are definitely things that you could contribute to today. Okay, so let's look at the 2019 winner. This was a team of developers from Spain a team of five folks that's the limit of people that can be on a team and call for code and they're working with the global challenge. It included a PhD engineer. She was accompanied by a data scientist a full stack and IOT developer as well as a nurse and a firefighter within their team called Prometeo. So it showed that the open source community really benefits from the collaboration of people with all sorts of skills and experiences and that will help them be successful by identifying who the end user of their innovation was and being able to tell that story of why this technology was important, why it hit a real need and how to be adopted particularly within that fire department in Spain. So their solution is based on Kubernetes it is something that we're open sourcing very soon as a differently named project Prometeo will be the startup at all was what the project will be mutually owned under a different name. And what they created was also IOT related and what it did was when wildfires firefighters go out into the field and normally they do much of their work actually don't prescribe burns controlled burns that are planned in advance. And so what they do is they select a piece of land in the Catalonia region of Spain in this particular case they determine which 12 firefighters are gonna go out there, cross the borders ensure that it's only contained to a certain area they set fire with benzene gasoline canisters and they control burns in the way it goes but during this non-emergency situation they're spending a lot of time exposed to chemicals carbon oxide, nitrogen dioxide, acroline the benzene from the fuel from alvehyde all sorts of other things that are burning vegetation and they normally track before, during and after on paper how is somebody feeling? Are they having headaches or they having shorts of breath? And it's always been a paper-based system what this solution did was create an innovative prototype that the firefighter wears includes sensors and could emit data in real time to someone in the field in the tent to see the state of everybody's exposure that they may not even know themselves how they're really immediately affected by that chemical. And what we've done with the open source community is take it from there and with the team that was assembled around the world to help them, hardware experts, data scientists folks that understand Watson Health, for example folks that understand long-term averages of exposure to chemicals as well as folks that helped create a brand new user interface for the device other folks that helped go from the prototype board down to the soldered board which sets them on the path to a new PCB to fabricate work. And so we had a team of IBM from around the world Argentina, United Arab Emirates, the United States and Spain themselves take part in this initiative to bring the project to where it is in its current state. So there's the device now is offline first. It caches information as well as captures and averages over time, which are just as important as the real-time exposure of the firefighter. And earlier this year, they were able to take the latest version of their device and put it into a more self-enclosed unit when it doesn't expose battery or wires as in the first burn site that won the competition. They've deployed everything to Kubernetes. Everything is deployed and auto deployed from GitHub and the documentation is being improved and in general made more welcoming to the open source community. And Samsung was a partner in this. They lent some watches and ruggedized devices to help drive two-way communication back to the firefighters rather than collect the information. So really great ecosystem building around this project. And we're really looking for contributors in the coming months to help drive it forward in terms of improving the hardware, adding more sensors, doing mold development, watch development. Samsung, based on Java or Kotlin, web applications, I'm sorry, watch based on C++ or just web apps, and data science, Jupyter notebooks, things like that. So really looking for a community to grow around this project and bring it from where it is as that robust solution to somewhere where it can make a greater difference not only in Spain but elsewhere around the world. So let's look at our final one. And as I mentioned, these projects come in. They're still pretty rough around the edges and it's usually limited to the team that created the technology, right? Some of them may not be as familiar with open source, but they're really good in consuming open source technology, writing code, building apps, or they have some great experience on the ground with the problem domain. And what we try to do is bring them from that raw state through the incubation so that they can test the technology and it can be expanded around the world. That's kind of the repeating pattern we have with all of our projects. So agrily what they created for the call for code challenge which was focused on climate change last year was an application that's able to combine a whole bunch of data, public data from NASA as well as some of the weather company APIs around short-term forecasting. Digest that down into a way for a small holder farmer based in Mongolia, Brazil or India which is where the team is from. They all met at Pace University in New York though. How a farmer can make use of this massive amount of data that is brought together and run through a set of data science algorithms written in R to give them immediately actionable knowledge to start each day about what they should plant, when they should plant it and what sort of considerations are out there in terms of precipitation or temperature. So a really amazing way to use modern technology behind the scenes and to bring that into a really crisp user interface for the ubiquitous Android devices that are available throughout emerging nations. They fortunately were also one of those teams that had a local audience to test their application with them and they provided immediate feedback during the competition. They tested with some small farmers in Mongolia to start and we continued to work with them using after the competition, what we do with each team is understand their needs based on a design thinking approach. So understanding their end users in more detail, empathizing with what a small farmer has access to, what the information they need and then working back to develop a solution that can improve the outcomes for that farmer in an iterative way so that through the Agrily team startup at their own company, they can build a business model, they can expand around the world and the open source community can still benefit from this core innovation, taking it in different directions, contributing it, maybe using it in other parts of the world where the Agrily team is not focused right now. So stick out, stay on the lookout for news from this project but really great innovation there and you can follow their story through a bunch of videos and updates we've had over the years, including at our recent think conference which targets IBM developers. Now, those were the top global challenge winners but we do, as I mentioned, have a set of a bunch of other open source projects that are in various states of maturity that we need you to look at. At a glance here, there is, Projdall is the cluster protocol one, we'll have the one for Prometeo under their new name soon and I'll mention OpenEW, Isaac Cimo and Liquid Prep in the following slides here but you can also learn about these and the Call for Code for Racial Justice projects through the Linux Foundation website or through the GitHub organization directly. So we do have a really amazing new project in there in the Call for Code ecosystem. It didn't come as a global challenge winner but it was amazing technology that was being deployed in Mexico and Chile by a startup called Grillo. And so what Grillo did was they analyzed how you can provide earthquake early warning to communities that aren't in the global north. They're very rich folks that can afford billion dollar national earthquake early warning systems like Japan, parts of the US, Mexico. And what they did was they created a way to democratize early warning technology by creating low cost sensors with high quality components that can gather information like an accelerometer in your phone, XYZ data on a regular basis that can be emitted to the cloud. And once a consensus algorithm is run between these IoT devices, the cloud can determine, yes, that's not a false positive and not a certain number of devices confirm that there is a potential earthquake send the alerts. So they've done some great testing on the technology. It favorably compares to some of those national networks in Mexico, but it's now open sourced as the open EW project. So the community can get involved in understanding how the hardware pieces come together as well as contributing to those detection algorithms run in the cloud and also build applications that can consume that data and create new alerts in different ways or integrate them into existing mobile applications. So there's a initiative underway right now in Puerto Rico, working with 90 of these sensors. There was an announcement just yesterday, President Clinton of the Clinton Global Initiative talked a bit about this initiative underway with scientific research institutions in Puerto Rico, Grio the startup and the Linux open source project that powers it all behind the scenes. So looked out for those announcements and there's been a great community around this project already within the technical steering committee itself. We've got a set of independent developers, we've got seismologists, IBM is there, Facebook is one of the TSC members and it's a growing community of folks who are improving the technology, helping develop the citizen scientist networks behind this as well as some of the national networks that might want to take part in this either an academic sense or to set one up as an option for their own earthquake early warning system within their particular location. If you go to openew.com, that'll give you great details on the project. I can join the Slack community there. And of course on GitHub, you can take a look at the code right now and learn more about the sensor versions being deployed in Puerto Rico as we speak. And I'll take a look at two other projects. Another one that is in a similar domain as Agrily. So whereas Agrily focused on getting information to farmers, driving things from the cloud, being software based, Liquid Prep is one that's with the Linux Foundation right now. It emerged from an internal call for code competition for IBMers. And this one has been tested, it was the 2019 internal winner and this one's been tested in a field in India as well as through some partners in Canada. And they have an open source community that includes the Central New Mexico Community College that has developed additional types of sensors that can be used to inform a farmer what their current soil conditions are, what the upcoming weather portends and whether they should water today, how much they should water today based on bringing all this information together. See, there's lots of great testing going on right now, lots of organizations involved and always looking for new partners to help improve this technology around the world with different institutions. So this one is already a call for code Project Linux Foundation and you can take a look at that tech today. And finally, here's a new project it comes from an organization called BuildChange. It's called Isaac Simo, Intelligent Supervision Assistant for Construction and it's Spanish translation. This is one that actually came in as a finalist in one of the global competitions but they had such promising technology that we continued to want to support what they did in the context of that challenge and bring it into Linux Foundation as something more generic as an open source project. So it is built on an earlier project that was created in the context of the earthquake in Nepal in 2015. BuildChange is a nonprofit organization that sends out experts in emerging nations to assess building quality that may not be up to certain standards and to ensure that after an actual disaster it's still safe to live in and if not what the homeowner could do to improve it. So the initial solution behind Isaac Simo was a way to train a model on building types in Nepal to understand based on the window placement the door placement, other construction elements and their current level of damage whether they were safe to go back into whether they were definitely not safe to go back into and should be destroyed or whether they should get some remediation in terms of retrofitting them with steel pillars or additional concrete elements. So based on that application that provided homeowners with their own power to get those rough assessments upfront the BuildChange team has been working on a solution that is dedicated more instead of at larger buildings, facades looking at the instruction elements within. So the quality of the rebar the quality of how a brick wall has been created in terms of the stacking of the bricks and the mortar thickness and other things. So really an amazing data science challenge and also another way to use Android devices that folks have ubiquitous devices around the world. And so what BuildChange is now trying to do is based on the context of Nepal and Columbia where they operate is create a generic framework for folks around the world to use this technology as a way to train and deploy their own models for building quality. So in the United States we have certain types of building conditions and standards in Europe, they're different in Africa. And so by creating a framework where anybody can train and upload their models the BuildChange team can also validate the quality of those models and certify them as it were. These things can be created as a ecosystem of trained models and also folks can create their own version of the Android application and deploy something for their local environment. So keep on the lookout for this one. This is an amazing project. We've been working with the BuildChange team for about 18 months to bring this to the state that it's in. So with that, I hope you're inspired about the great technology that's there already but as I mentioned, we are starting our fourth year of the global competition which again is going to be focused on climate change. And if you're really inspired by the solutions that have been created I think this is a great way to learn about those contribute to them and meet those teams in the open source community that we have through call for code and also build your own skills. So if you wanna learn about data science if you wanna learn about visual recognition training machine learning models learning about IoT mesh networks learning about sensors and data science of calculating averages over time. There's a lot of great tech out there already that you can learn from. And we also want folks to take part in this year's competition, build their own amazing stuff, leveraging potentially some of that Linux foundation technology that's there or using additional projects like Kubernetes that are also hosted at the LF or other technologies dedicated to agricultural situations. For example, as with the AgStack foundation which was just announced earlier this month. So meeting the ecosystem, learning the tech and getting involved. So the theme this year again is climate change that was last year. We have a specific focus on the three sub themes within climate change. So you can build an application for climate change generically or you can go look at the starter kits for three themes that we validated with folks at the United Nations and public and private partners in a design thinking workshop we did ourselves around understanding a potential technology solution to clean water and sanitation which is grounded in sustainable development goal number two around zero hunger which is in sustainable development goal number six or responsible production and green consumption SDG number 12. So what we try to do through call for code is bring experts together so you can understand on these important issues how they measure success in terms of what needs to be achieved by 2030 as well as have a look at a potential use case and solution on how you use IBM and open source technology to create the seed of your submission for the competition which you want to support as a sustainable open source project at the Linux Foundation if you've won the competition. So take a look at that. We've got a lot of training. There's some on-demand materials around the competition, things like that. I see we do have a question about the call for code application and deadline I'll get to that in a second but it is a multi-month global competition and you have plenty of resources you've got folks that you can leverage for help in the competition. So four steps to get involved. We have a community in the IBM developer website. This will get you access to free technology to build your solution. We've got lots of tutorials on the IBM cloud which in turns built on a lot of Linux Foundation open source technology which includes the CNCF projects and other projects from Apache and Eclipse Foundations as well but a lot of great open source there that you can consume as a service. You'll have access to $200 in credits with the new account for six months and we've got access to those starter kits. As I mentioned, they're in the call for code GitHub organization as well. There's videos, there's architecture diagrams. There's lots of tutorials to get a feel for how you would build a solution. In Slack, you can find team members. You can reach out to mentors like myself who can help you understand open source technology and point you at the right experts who might be able to guide your solution. And the competition is open until July 31st. So you have just under not just over two months to build your solution and continue from here. And even though we launched the competition in March we opened up participation. Teams like Agrily last year, they wait at the end of the school year at Pace University which is about this time to start working on the solution. So even if you haven't gotten started plenty of time to do that. So July 31st is the deadline. There is a project sample GitHub repository that you can find that has a sample of the deliverable we expect. It's a well-documented reading file. It's a crisp description of the problem you're solving includes a three minute video and any sort of working code you have today that the judges can use to assess whether the solution does what it says. And also a roadmap. So as I mentioned, when call for code solutions come in folks have only had a few months to work on the projects. We know they're maybe not production grade yet but with a roadmap we can tell how mature the project is and what your grand plans are for it going forward maybe assuming you do have funding maybe you do have contributions from IBM experts to help you bring it forward. So July 31st is when things are due but call for code is a year round initiative we do have a lot of other ways to get involved even beyond the competition period and of course in the open source communities. So please do get involved. So with that, let me see if there are any other open questions in the chat. I see that we had some answered ones. Let's see, let me see a general chat. But if you do have any questions please drop them into either the Q and A area or in the chat in general. And I will get to those. We do often have, we do have a frequently asked questions page. So if you go to call for code.org which the website for the global competition that describes the official rules that describe the judging criteria. It has a list of judges who are both technical and non-technical from organizations like we've got Jim Zemlin from the Linux Foundation who judges. We've got President Bill Clinton who's involved in picking the top five finalists from the semifinalists. We have technologists, experts all over the world. You can see those folks we have lined up for this year on call for code.org and you can also find the FAQ. So it talks to what your IP is. It's all yours, but the submission itself has to be a package to license so that judges can evaluate it. And we do want these to live on as open source projects. You can learn about the team member sizes. So maximum of five, minimum of one, you can compete alone. There's links to the starter kits. There's links to other potential opportunities for you as a university student to take part. We have additional prizes there. Your university may already be involved. So they may have access to additional specific resources. And you can also keep in touch with the news and the additional things. Okay, I see we have a question in. How many hours per week on average are required to work on these projects? Does it depend on the project perhaps? That's a great question. So the competition itself expands from we launched on World Water Day, March 22nd this year. It goes until July 31st of this year. So that's a great window to work on your application. And there's really no right answer as to how much time you shouldn't spend on it. The judging criteria, one of them is completeness and transferability. But since that's balanced with innovation, usability and inefficiency in what problem you're solving, some of it, the time you spend can be just, you're in the flow, you're doing things the last week of the competition. You're creating amazing stuff that's powerful. There are other folks that like to pace themselves more, deliver on two-week sprints from start to end. So I think on average, it couldn't go anywhere from a couple hours a week to maybe working 40 hours a week, one particular week. And so it depends on the team, how your team works together, the time zones. And there's really no official level of completeness it needs. You're competing with folks from around the world, so the more complete, the better. But the most important thing to leave time for is preparing your kind of pitch at the end. And we do a webinar on submission best practices, but since you're gonna be sharing your idea with technical and non-technical judges, you wanna make sure in your submission, you've got a well-documented GitHub repo. You've got a crisp three-minute video that talks to what you're trying to solve, showing how you're solving it and where you wanna go with it. And also leaving any additional deeper videos or documentation in that repo for the judges to find. There's a set of four tips I have. So if you go to callforcode.org slash submit, that shows you a video of my four tips. It shows you the submission form of what's required so that you can get ahead of that. Folks can, you know, your video quality can vary. You can be super professional. It can be just something to throw together on Zoom that you record yourself talking on. But make sure you take a look at some of the projects that have been out there before, learn from those, look at the project sample, which is linked to that submit page and build your solution. Okay, another question comes from BJ Choudhury. Is there any computer language barrier? Great question. You can use anything you want to build an application for this competition. As IBM is the sponsor and founding partner, we ask that you use one IBM cloud product or service. So you might use a web application runtime. You might use a service function. You might use the weather company APIs. You might use a blockchain platform, Kubernetes, code engine, anything there, but you can bring in stuff, data sets from elsewhere, open source projects. So if you, for example, want to embed a Google Maps API, something like that, you can do that. You want to pull in data from elsewhere. If you want to build your solution completely, for example, on a local React environment on your computer, just when it's ready for submission, deploy that to the IBM cloud maybe, just as a web application, if it's a static web app. So that's really the only limitation. And keep in mind that the end goal is sustainable open source projects. So if you're building on something that's a really obscure language, you may not have a great audience of people to contribute to it down the road. And so keep that in mind, or if it's a limited access platform, we have seen some great mainframe solutions, but not everybody has access to a mainframe. So think about how you're going to deploy your solution if it were to be carrying on as an open source project at the Linux Foundation. Okay, another question from Ori Gruber. How can I attend the competition as an observer? It would be helpful to see the candidates and their projects. I work with over 1,000 students, 40 faculty as a chief technician at King City, University of New York, great to see you. We've been involved with the Bureau of Manhattan Community College. And actually we've had one of the professors from CCNY take part as a judge in the competition in the past. So we definitely have ways for, as a observer to take part in the community, you can still register for the competition, join Slack, introduce yourself. We may be interested in talking to you about being a judge later, or we may invite you onto a webinar, maybe talk about some of the key client change issues out there. And of course, we'd love for you to share the message to students. So maybe you run a hackathon specifically that targets your agricultural college within your university system, things like that. So yeah, we definitely do welcome non-technical folks. As I mentioned, even within the teams, they are helpful to create solutions that are well balanced and take on a real problem. So one limitation we do have is for prizes, we can't give them to government-owned entities. So faculties of state universities, unfortunately, Winfield was a part of a team, but they can mentor their students who are not official employees of that university to take part. So I look at the participation agreement carefully if you have any questions around that. Great, okay. I don't see any other questions coming in. And I know we're just about ready to wrap up anyway. So let me leave you with some closing, just some comments. Really, to learn about Call for Code, check out hybium.com slash call for code. That's where you hear about this year's competition, join Slack, get the invite there, accept the code of conduct just like the LF has. And then if you're interested in taking a look at the projects, go to Linuxfoundation.org. If you look through projects, look for Call for Code. You'll see the 12 we have there as well as links back to get up. So I'm really looking forward to contributions that you may have to the community. Feedback you may have to make the existing apps better but also things that you might create that become the next big, great Linux foundation innovation. So with that, let me, I guess, wrap it up or hand it over to the host. And go from there. Thank you so much to Daniel for his time today. And thank you to all the participants who joined us. As a reminder, this recording will be on the Linux foundation YouTube page later today. We hope you join us for future webinars and have a great day.