 Okay, folks, welcome to this session on Call for Code. My name is Daniel Crook, and with me today is Charles Johnson. We both work at IBM, and we're also members of the Call for Code community, which we'll talk about today as a couple of different components and how it relates to the Linux Foundation. So our goal here is to show how you can leverage that community to learn about some of the tech for good projects that we have at the Linux Foundation, how you can build skills, setting them up, running them yourselves, and how you can attribute back to them as well. How many of you attended the Agreg session from these two earlier today? No, okay, well, I'll see you guys. And how about anybody here already familiar with Call for Code? So I won't spend too much time on that. Great, so Call for Code launched about five years ago. And it was launched by four organizations together, one of which was IBM is a founding partner together with the Linux Foundation, the United Nations Human Rights Office, and David Clark-Cawes, he's a fellow that engages eminent politicians, eminent world leaders, celebrities, other types of folks to really inspire people to take on humanitarian challenges. He's had some other programs, for example, for veterans, for clean water, things like that. So it was launched, and from the IBM point of view, we really wanted to continue to build upon our legacy of doing great and amazing things, putting a man on the moon, having a machine play jeopardy and win. So it is really an extension of what IBM kind of represents in terms of having that tech for good point of view. So it goes back into our DNA. So what really does set it apart though is that we don't just run a competition, a global competition every year. What we do is we also want to inspire those ideas and not just recognize them, but also help them live on as sustainable open source projects. And that's really where the Linux Foundation comes in very important here. We also, as the IBM side of that, is support the teams with mentorship, open source best practices, and we support the projects, deploy them through our set of IBM volunteers called the service core. So in those five years since we've launched, we've had half a million developers, data scientists, project managers, folks of all kinds take part in the competitions, as well as students from around the world, and from every corner of the globe, which has been really amazing to see in our communities, people communicating, collaborating, working together. And in fact, one of the teams that won one of the competitions, they had a member from Taiwan, one from Mongolia, one from India, and one from Brazil. So really a global community. And we've taken on, in that global challenge each year, there's a focus on one particular issue, and it's gone from disaster resiliency, to responding to individual needs, health and wellbeing of folks taking on natural disasters, through to more of the cause behind that disaster resiliency, which has been the climate change, and in particular in 2000, we had various activities and events around upcoming challenges, like the social and business impact of the pandemic, and racial justice, right? The struggle against racial injustice through a program called Call for Code for Racial Justice. And so we've had various projects that not only took part and emerged from competitions, but also things that grew organically from initiatives inside of IBM, started by folks like Gaurav, who we actually have an internal competition for IBMers and Red Hat folks, created a solution as well. So Tech for Good, coming to take on broad series of issues, resulting in a set of open source projects within the Linux Foundation. So as I mentioned, what sets it apart, it's not just that competition, it's not just recognizing a project, giving a prize. What we do is, together with partners like Samsung and the United Nations Disaster Risk Reduction Organization, and plenty of other folks in the ecosystem, is we help those teams that emerge from the challenges to get through an incubation phase, we call it a deployment framework, basically that gets them over the course of about a year from that raw innovation through to improving their functional, non-functional requirements, security, usability, having them partner with GoToMarket or other experts that can test and validate what they created was something really important for that issue, that they were going after the right issue. And finally, we get them to a stage where they're ready to graduate as it were. So all of this work is through an incubation framework and at one point they, whether they're a startup, a part of an enterprise, maybe a non-profit, they are ready to live on as a sustainable project, that is, that doesn't require the incubation phrase anymore, and they are released as open source projects at the Linux Foundation. So let's take a look at those projects and I'll come back to the 2022 competition in just a bit. But within Call for Code at the Linux Foundation, so Call for Code is the initiative itself, this is an entity, a legal entity at the Linux Foundation, which holds all of the projects, governs them neutrally, maintains their trademarks, and adheres to several of the other best practices for open source projects. So ensuring there's a code of conduct, ensuring that there's a contributor agreement and that the GitHub projects are properly structured in a way that encourages contribution and use as well. So we do have 14 projects in there. If you go to the linuxfoundation.org projects page, it's kind of linked from the mast head any time you're at that page, you can find them, it's a highlighted group of projects. So it's kind of like an umbrella in and of itself, and that has each of the 14 projects, including ones that have come through the global challenge as well as the other programs like Call for Code for Racial Justice. And speaking of Call for Code for Racial Justice, this was not a set of projects that came through the global competition. This was actually using Call for Code as an engine to build amazing new technology to take on racial justice using that same framework. So as I mentioned, there's Call for Code the competition, and then there's the open source structure of everything at the Linux Foundation. So we had seven projects come in, came from within IBM and Red Hat and launched in 2021. The other part of what IBM does for these open source projects is we make sure that people are able to kind of understand and consume them so they can use them, put them to work wherever they need to apply maybe in their community. There's also a bunch of tutorials, videos, blog posts that we've produced for them, and we ensure that they all have those proper governance documents, right? So making sure that they've got code of conducts that's clear that if someone creates a pull request or opens an issue, kind of what they can expect in terms of the time that it'll take for it to be addressed or taken on. So always just working within these communities, making sure as they're fledging projects, fledging projects that they're becoming mature and really taking advantage of best practices. So we'll take you through a couple of these projects, actually all 14. The first seven, Charles will describe a few of them and some of the ones he's new to the team, he's actually leading one of the projects right now, mentoring the open source community, but also contributing back some new features. So he'll take you through this seven call for code for racial justice open source projects, and then I'll talk about the other ones that have come from the global competition and go from there. Hi everyone. Again, my name is Charles Johnson. I'm gonna speak on a few of the call for code for racial justice projects. One that I am actively working on is the Incidency Accuracy Reporting System. And what this provides is a platform for victims or someone who's observing a scenario or interaction with the police department. And they find that they need to provide feedback from that incident, whether that be photos, audio, video. Many of these projects came about due to the George Floyd tragedy. And people wanted to do something. So many of these projects came up through that chain, specifically this is one of those. And with this platform, it provides a two way interaction, not only for the observer or the victim, but it gives them a direct channel into the police department as well. So what you're seeing on the screen here is actually the mobile app, which the person submitting an incident would use, someone in the community. And what you see on the laptop behind there would be a dashboard that the police department would use to collect these incidents and integrate them into their existing platform. Okay, moving on, legit info. This project provides a platform for those who wanna come and provide more information on legislation, okay? Fair change, fair change is another platform that is in ways similar to what we call Incidency Actors Reporting, but it takes a deviation where it rather targeting local police department, it takes it to a national level or a beyond, okay? And in addition, it does also have an app that you can go in and capture photos and videos and so forth and collect location information also to provide that back. So take two, take two is another project where it seeks to analyze information that's out in the world and try to reduce or eliminate racial bias language within that structure and platform. OpenCitizen takes a similar approach, whereas it empowers the public defenders to address racial disparities in the justice system. Now, Five Fifth Voters is an interesting one where it targets the voting system and tries to make sure that when an election takes place it is fair. TruthLoop provides a mobile friendly way for users to examine policies, regulations and legislation information allowing them increasing legal awareness and start a discussion. And I'm gonna pause here for Daniel to come up and talk about some of our other projects. Awesome, thank you, Charles. So I think one of the great things about those projects that Charles mentioned, it applies to these other projects as well is that they're all based on various technologies that different developers can get involved in. As you notice, some of them were data set oriented for data scientists. Some of them are mobile applications. I think they're based on React Native, some of those projects. And then there's others that are like browser extensions enabled through the Chrome browser. So lots of different ways in those projects to leverage open source technology themselves to create those innovations. So really cool projects. Now, going to the ones that came from the climate change and disaster resiliency track, one of the first, actually our very first global challenge winner was, came from a team called Project Owl. And you'll see the way the Linux Foundation works is there's often a startup or a company that creates the project, the innovation. And then when it's released as an open source project at the Linux Foundation, they take over the trademarks and the logos and things like that. So some of the projects actually have gone in as what they were named. They're completely donated, just like the call for code for racial justice project. But some of these have the dual naming. There's kind of a sponsor or lead project behind them. In this case, that's Project Owl. They won the global challenge in 2018 and they released their code through Linux Foundation, the open source part of it as the cluster duct protocol. So in this case, what they did was they built an IoT based system and actually Charles is one of the folks that was on this team taking part in the competition. We recruited them into IBM to continue to help with call for code but also support the open source development of this with the Project Owl startup that lives outside of IBM. But here is the network that was built to be quickly and cheaply deployable after a disaster. A lot of the solutions, for example, that took on connectivity challenges in Puerto Rico after Hurricane Maria, they were expensive or they took months to deploy. And in many cases, while it was easy to get power back on through a generator or solar, network connectivity, even enough to send basic messages, sometimes wasn't restored for nine months. So this is really looking for making cheap and ubiquitous mesh networks that can be put in challenging locations and in fact, even something that can be deployed into space which is really cool if you want to check out that project. The following year's challenge winner was a team named Promoteo from Spain and they released their open source project together with Samsung. It's called the Pura platform. And again, it's an IoT solution. It's focused on wild lands firefighters. So folks that don't have the city apparatus of a regular firefighter inside of a building. There's a lot of equipment for that but when you're battling wildfires or more likely when you're preemptively doing burns, you're getting exposed to a lot of toxins and chemicals and it's kind of hard to measure that. A lot of the ways that this was done and particularly in Spain was there was a nurse or an EMT that followed around firefighters to kind of record how they were feeling in kind of an analog way. So it's one of those ways that you can use digital technology, find the averages over time and plot it on a dashboard. Isaac Simo came from a nonprofit named Build Change and what they do is they focus on ensuring building quality in the emerging nations. So ensuring that when, for example, a wall is structured like this, the bricks are in the right pattern and that the spacing of windows over doors ensures continuous column. So really cool data science in there to actually detect the centroids and locations of bricks, giving a quick way for someone to assess or validate that the work done by somebody else is right up to quality specs. Another project came into the call for code community, but through a different path is from a team in Rio and this is again an IoT device but it's focused on earthquake early warnings. A lot of countries around the world do not have a unified national system. It's only at the West Coast, the US, Korea, South Korea and Japan and those are billion dollar systems and what this aims to be is use cheap sub $100 components, high quality components but fairly low cost to aggregate those together to give people a minute or two extra warning that an earthquake is on its way so they can get someplace safe. Liquid prep is a solution built for measuring the current soil humidity and understanding that in places with scarce access to water, that farmers can make better decisions about when to water based on predicted and upcoming weather. So IoT solution with an Android component using open data sets. Drone Aid is a project that was also inspired by Hurricane Maria in Puerto Rico and what this was inspired by was a lot of folks were writing help messages when they didn't have the connectivity on painting on asphalt, writing on bed sheets but by using United Nations OCHA standard iconography together with visual recognition and machine learning, it's a system for actually detecting those whether you're using a drone, whether it's civil aviation flying over or even satellite so that these things can be detected on the ground during search and rescue. So really simple, powerful way to use open source, train a model and deploy it in a way that can be used in lots of different ways without needing to be localized really. And finally, I think the most fun project that was in the call for code inventory is something called Rendomatic. This was inspired by folks in the United Kingdom who were really looking at how do you continue to support singing inquires, kids singing inquires, people trying to get together remotely to collaborate on songs. There was a lot of that in the early pandemic but if you'd noticed that it had to be recorded separately and mixed together. If it was live, there was Echo from Zoom and Webex and things like that. So this is actually a software solution that supports up to 300 synchronized bagpipers singing the same song. It links all the sound waves together. It reduces that delay. There's always gonna be an incremental delay when you're matching up these videos, these separate segments. It's really a fascinating demo but really cool technology that kind of took on that challenge of how do you do a concert together. And as I mentioned earlier, for all these projects there's plenty of resources for getting to take part in those. And we do have, of course, plenty of other projects that underway right now. Agrily, if you were at the Ag Session earlier is another solution that won call for code in 2020. We're still working through releasing their project as Open Tempus with Linux Foundation. You'll probably hear about that one this summer. And soft water was last year's winner. Really for measuring the quality of ground water focused on the use case base in India where some of the team developers family were affected actually by changes and chemicals being introduced in the water. So leveraging SMS technology to alert people there might be a problem and providing mitigation strategies for it. So these are hopefully some great projects you'll be seeing in the open source community pretty soon. And let me hand it over to Charles again to talk a bit about some of the work that's being done from a framework level to deploy these projects in more consistent way. Okay, so my background within IBM here recently has been work within OpenShift Kubernetes platforms. And coming on to the call for code community one of the observations that I had was the most or many of the projects do run on the cloud. The manner in which you deploy them varies. You have a set of instructions that you go through to deploy them. Well, coming from a different enterprise application the deployment there was standardized. And within Red Hat OpenShift we have the Red Hat OpenShift market where you can go choose operators and install applications at a point and click. So our push that we're gonna have for this year will be to implement operators into the platform to ease the deployment of these projects that you've seen some of them that do deploy onto the cloud. It's gonna be a stair step process of course but the time involved to deploy these projects will significantly reduce through that web interface. It'll take out a lot of the command line necessity from this. In addition to that we want to enable those who may not know much on the operator of optics to educate. So we'll also provide this as an opportunity to provide education on operators throughout the year as we level through this process. So stay tuned for that. There will be more coming on the topic but expect that some of our projects will be announced soon with operators. All right, so a second topic that I wanted to talk about and one of these projects I mentioned earlier but let's talk about a dashboard. A lot of our projects even the ones that come in several and they all have varying levels of UIs that are associated with them. Whether that be a homepage that someone wanted to create, a dashboard for admin. So if you have these IoT devices, where are they reporting? How are you looking at information, right? Everyone's developing their own UIs and things like that. And if they want to go that direction, that's great. Sometimes they don't. They want to just get to the work and not handle the UI aspect of it. Well, within IBM, we do have a design system called the carbon design system. It's actually available for all major JavaScript frameworks, not just React. This dashboard is built on React and the community is mostly behind React but there is a community involvement in both Angular and Vue.js. So those options are available too. But we're providing a dashboard that showcases components of the carbon design system along with providing anyone. It's not just call for code projects that want to submit but anyone that wants to use the carbon design system and wants a starting point. That you will have a ready-made UI available to use. And we're gonna do a short demonstration but I don't want to... I'll get a little tabbed to it. There's carbon. Okay, so I won't spend too much time on the carbon design system but if you want to know more information there is a wealth of information. And one of the best tutorials that I've been through before is on this website. It is, I believe, React-based but it is an awesome tutorial to go from nothing to something. Okay? And if you're interested in the components you'll see that there's a list of them here. I don't want to go through them. A lot of these are taken into this design system, this dashboard that we're presenting. And this is the dashboard. It's available on the call for code page. I think it was on the slide. We'll get back there in just a moment. It's that tab. That's the repo, yeah. For the repo here? Yeah. It provides the code there. We welcome feedback. Let's make it better. That's what this is all about. And the demo here, if you just want to log in with the credentials demo demo you'll be taken to the dashboard here. And you can see, there we go, that there's quite a bit going on here as far as components that were listed on that page. From charts, to towels, to varying designs of fonts that are standardized. And we have a dashboard here where we can then get into a few things like searching. Let's say we're looking for Harry, right? And then we can expand this out. Now we're just showing five. Well, let's show a few more. Let's say 50, right? And these are all provided standard through the platform, okay? And you could come in here and archive or edit these entries as you see fit. And again, a standard UI throughout. That's what we wanted to achieve here. And this is built on the latest version of the Carbon Design System which just recently launched back in, I believe, it was March, or maybe April. But, and there are other pages here that you can visit. The user profile, the new report. In addition to, if I log out and register, there's also a registration page. So some of the key components that you would seek when you're developing an application online, this is ready-made if you wanna use it. Though, don't get me wrong. If you, this is your passion, you wanna go create your own. Carbon is a great platform to use. It's not the only one. But it is one that has a lot of support behind it, okay? That is everything that I wanted to discuss and I'll let Daniel come and move it back over to the presentation. Great, thank you, Charles. So yeah, there's, as Charles noted, there's plenty of other, in addition to the core Kafka projects, we've got a whole bunch of resources there as well. And what we've noticed over the years with Call for Code is, you know, originally we thought Call for Code was going to appeal just to developers who are ready to build solutions and use their code skills. But we realized really quickly, and especially with the second year, when the project team included a firefighter, a PhD engineer, a nurse on that team, that a lot of folks weren't that familiar with open source, they understood kind of the idea of it, but they didn't know quite how to do the mechanics of it. So what we've really done in the last, in addition to what else you'll find in that Call for Code GitHub organization, there's new repos in there. There's a, basically a project sample that captures many of the Linux foundation best practices. So it's a template repo you can clone and reuse for any project, whether you're taking part in Call for Code or not. It encapsulates some of that. And then there's a new one we created, which is actually based on the carbon one that the Charles mentioned, which is really cool. And that's why I reuse kind of the bot technique behind it. But it's an automated way for people to kind of make their first contribution, their first pull request to a project, going through that mechanic of writing new code, or forking the repository, writing new code that fixes a bug, submitting it back to the project, and then being told whether to fix the bug or not. So it's an automated system. When I was first getting into open source many years ago, that was one of the things that always scared me is I didn't want to mess with anybody's project, right? I didn't want to do something wrong and get yelled at. So really that's the intent of this practice pull requests repo. So give that a try. We've got a GitHub account. Go ahead and play around with it and get familiar with that. And together with both these resources, there's also a badge you can earn for an introduction to open source course. It's about four to six hours of time. You'll learn a lot about the best practices, the things we adhere to in the Call for Code community. You can get a nice little badge and certificate at the end of that. And there are other different ways too beyond GitHub that folks can contribute to Call for Code projects. We've had folks, it's particularly with the Call for Code for Racial Justice projects, I think come from a very wide array of backgrounds. So even if you just have a few hours, maybe you have some days, maybe you have some weeks to contribute, documentation is always a great place to start. Design, new logos, the OpenEW logo came from Aktoberfest. A couple years ago, somebody just created that amazing, cool, little, simple waveform. Sharing information, providing feedback. For example, with this new dashboard, if you play around with that, you find a bug or it doesn't work. I know we have a dependent bot alert in there, for example. We can at least get some full requests to kind of fix that. But people can kind of test and let us know those things. And obviously community events as well. But yeah, documentation, providing legal advice was one of the big ones as well. Helping do some hackathons around the things, reviewing licenses, and really helping drive adoption, whether you're a user, a contributor, or you want to otherwise build your own skills and take part in the community. So definitely encourage you to do that, even if you're not technical. Okay, so we focused at Open Source Summit on purely the open source side of what we do with Call for Code at the Linux Foundation. But in order to generate that innovation that is eventually released as the open source project, we do run the global competition every year. And this year's focus is on sustainability, which includes lots of different kind of sub-themes too. So if you give that a scanner, just go to ibium.com slash call for code. You can learn about this year's challenge, kind of how we're providing the tools and the tutorials and the mentorship to help you build applications that address these issues, which basically acts an umbrella over many of the themes we've done on call for code of the year that we found really inspiring and in need of solutions by talking to experts. So carbon emissions, clean energy, supply chain, things like that. Lots of subtopics within, lots of great ways to take part in call for code. Again, this inspires some folks, but we've got $200,000 grand prize for the top call for code solution this year. And then the top five also get cash prize and support from the Linux Foundation. The Linux Foundation beyond what we do with call for code includes mentorship, funding, stipends for interns that your project needs, dashboards. And in fact, they've got a great booth up on the show floor. If you wanna go talk to the LFX folks to learn about what sort of things, if you bring your own project to the Linux Foundation, even if it's not call for code, kind of how you can take part in that. And then of course with these, we'll also be supporting the top project through a service core deployment with top IBM volunteers. And we did launch back in April and we've had one accelerator event which kind of had its own mini challenge with its own prize, but there are two other upcoming challenges, two week accelerators and submissions and judging will go through the end of the year. So a little bit of a longer window than normal. Normally it's only four months in the middle of the year, but we expanded out to see some greater contributions this year, submissions. So to take part in call for code, it's really about finding some value in the community, expanding your network, learning new skills, start building those solutions. We've provided four call for code participants a particular type of IBM cloud account which gives you free access to things like Kubernetes clusters and other free services that you can use to build your solutions for the competition. And we hope you submit something this year. Okay, and with that, were there any questions? Any audience? Okay, we've got maybe something queued up from the virtual audience or she's got a microphone, if anybody has questions. All right, so we got a virtual question from Tim. He said, I would like to submit a project. However, I don't like the privacy policy as too much of my info is shared. Any suggestions? Should I repeat the question or did that go to the audio system? Okay, so yeah, so the question was somebody wants to take part in the competition, but the participation agreement is a little bit too, asking for too much information. I don't have a direct question to that. I'd answer to that or maybe we can have someone answer that. But I'd love to, for example, have you joined the Slack community, raise that question to anybody tags an IBM mentor and then we can get you direct message you or answer in the help desk channel. Exactly, yeah, Brandy mentioned something good. So if you can call out especially what you didn't like in there, that's helpful as well. I think the participation agreement, it's been consistent the last five years. There may be some new things that apply to the Be My App platform, which is the third party platform running it this year. So we'd also like to know if it's a call for code thing or a Be My App platform thing. Was there another virtual question or was that one? Okay, okay, great. Great, and just a couple closing slides, right? So if you were at the keynotes and basically I think the common theme to every keynote today was security, security, security. So IBM, we've got our point of view on that as well. We've been involved with several Linux Foundation type of efforts, including OpenSSF. So you can check out some of those materials. That is definitely, I think that's always important in software engineering, particularly with open source, being transparent, understanding where your data is coming from, how it's handled, all goes into software supply chain. And then we've got some folks that are working the booth today, throughout the week as well. So stop over there. There's a book signing tomorrow afternoon. I know Emily, she did a great talk earlier today on micro profile. If you wanna see some of that code, see some more of the demos, some hands-on ways to build REST APIs, you can do that. We've got a coffee barista there. You can do some other hands-on labs, program the Liberty Space Rover. And we do have Voodoo Donuts. If you haven't had a Voodoo, this is your first time in Austin, and you haven't had a Voodoo Donut, that's one of the cultural traditions or institutions you gotta try out. And then we got all sorts of swag in there too. So be sure to find us. If you have any questions about call for code, hopefully you take part in the competition, but in any case, we've got a Slack community, we've got the Be My App platform. So we'd love to see folks take part in that. All right, well thank you very much. Have a great day.