 Good morning everyone and welcome back to open source Summit North America We are very happy to have everyone here for our virtual conference. We wish we could have seen you live But unfortunately these are tough times this morning we have an amazing group of speakers and a few special announcements in In particular I want to start with an announcement from our open power foundation Today the open power foundation is announcing that IBM's a2i power processor core design An associated FPGA environment is being contributed to the open source community It's available right now on Github This is an in-order multi-threaded 64-bit power isa core that was developed as a processor for customization and embedded use on system-on-a-chip devices It was designed to provide high streaming throughput while balancing performance and power You may be familiar with some of its work The a2i was used as the general-purpose processor in IBM's blue gene q family of systems which helped advance scientific discovery over the last decade Mandy Furmanek and James Collina president and executive director of open power foundation Are leading a session at 2 p.m. Central time today in the os project updates track Definitely tune in and learn more about the a2i power processor contribution Our first speaker this morning is also from IBM Todd Moore vice president of open technology IBM developer and developer advocacy at Camilla sharp global business line executive for IBM software support business are joining us to talk about trusted AI Our world has changed and environmental and social factors are making taking AI models into new territory They will discuss how we can come together promote ethical AI use and trusted models to drive our world forward Please welcome Camilla sharp and Todd Moore. Hi, I'm Todd Moore. IBM vice president for open technology Today, I want to talk to you about something that's near and dear to me topic that I've talked about before actually at one of the Linux foundation open source events And that's trusted AI responsible AI We're in a world today that is Caught in a pandemic We have a global health crisis that depends on data and how we collect that data and how we make effective use of it Can save lives at the same time We're in the midst of a global movement around race and equality And these things intersect and they intersect with how we handle AI our models our data and and where we go from here at IBM's core um Our values are those of equal rights and these are long-standing policies that go back to 1953 and thomas j. Watson What do you put in place policy letter number four? that's Stated that IBM would be an equal opportunity employer and that we would not Have bias as a result of race color or religion Now arvin christner has also taken up this task arvin has Taken the IBM company out of facial recognition. So here's one avenue that will no longer be available for Uses that could create bias in our society and he's opened this up to public dialogue as to whether this technology makes sense and How our society should handle it but trust and transparency in AI goes beyond just facial recognition As the data that we collect gets used privacy issues will certainly Be at play Ethics of how that data is used how it's transformed how we as a society Respond all need to be sorted out and IBM has been providing tools. We've open sourced a number of projects We have a robustness toolkit. These are all python libraries We have a fairness toolkit that looks for biases within models and data We have an explainability toolkit that allows you to Very quickly Look at the black box that is potentially your AI model and turn it into something that you can recognize how it's behaving These are essential things that will help us go and take bias out of it At the same time, we're also working now on what we call AI Fact sheets and here will essentially be how we hold models accountable Think about it in terms of like the labeling that you have on Food products, right? It took a long time to develop But once they did you get quite a bit of information out of it as to what's actually in that canasuit that you have And that's what you'll find as we go and develop this project as well too now these projects have have progressed and What we find is that the Linux foundation AI Organization where we want to see these in open governance Has a TAC and they voted positively to now incubate these projects You'll see all three of the ones that have been out in open source available through the L of AI Organization so we thank them very much for doing this and we think it's a great place for others to come join in And openly shape and drive this work forward. We think it's important to society The group already has quite a few really important companies who are involved and Universities as well too. There's a trusted AI committee that we Would hope that any of you who can would come and join because they've been developing the principles by which we will Take advantage of and and use the models and the data that are coming out of the AI technologies involved So they have seven work group or seven principles that have come from the work group equitability Recreducibility transparency governance privacy security accountability These are the seven principles that they are working on right now as we speak So please come and join that now Since the last time we were out there and talked about this I I just mentioned obviously a fact sheets have come into play and we're starting to open source those but the AI 360 group has Worked with psychic learn and our studio and now have made themselves available the Cufo pipelines for ml ops are out there now and we can do fairness and adversarial detection on those pipelines And ml ops has taken a step into apache nifi and we now have a processor available as well So all the projects are also making great progress and Thank you for the folks who have been contributing Again, I think this is a really important thing for our world. Okay, let's switch gears to something for this a moment I have with me Madagana Villa Who represents a group in columbia the largest community of women in tech in columbia? and and she's here with me because IBMers each quarter get a chance to vote for The organizations that they feel are really deserving of community grants and we started this back last year Where we've been giving out essentially $50,000 worth of community grants to really deserving folks out there And it's 25,000 in cash 25,000 in cloud credits and allows them the freedom to to do is as they would like as well as to be supportive of of the organizations with cloud resources so that they can also Use those for for good and and so I just wanted to introduce Mariana and and Henry to say a few words about the great things that you do because you really captured the hearts of the IBMers involved and you overwhelmingly were voted in this for this this point Hi, so thank you so much for inviting me to be here and to do thank you to all IBM employees because they they trust in our in our Purpose and and we are really grateful to to be here to be selected to this wonderful grant because it's it's hopefully it supports our cause with Creating more impact in our community in columbia and in our region of latin america region Thank you, and and you do great work down there and you've spread to all sorts of areas that really You know are underprivileged that that need the support and the help and and we at IBM really love what you're doing So thank you very much and we appreciate everything you do with that Thank you We are we are super excited because with this is our first grant We are creating this community with no resource. We receive a little amount of resource for local companies to create meetups and and have like our teachers and our Registration as a foundation in columbia But we never tried to to apply to a grant Because we believe that we need to be sure what was the right moment to do it and right now it feels like really Really amazing to have these opportunities to have this resource to create more impact because our dream is to reach seven countries in columbia Main cities and we have a special project in rural areas when they don't have Like a network or connectivity So our dream is impact more indigenous people and perhaps we have an african really hard african heritage And and they don't have the same opportunities here in columbia And as as our as our in the main city So we are trying to to reach their rural areas and try to create that impact in in other In other places Excellent. Well, thank you again. Thank you for all the great work you do Organization is very deserving and Hopefully this won't be the last time we you get to see it Thank you, sir Thank you And now to talk about unlocking the full value of open source. I would like to introduce camille sharp global business line executive for technology support services here at ibm camille Thanks, Todd My name is camille sharp and i'm the global business line executive for ibm's multi vendor software support I'm very excited to be speaking today at open source summit north america. This is an event that I participated in myself And so it's just a pleasure to be here I've actually been asked to speak a little bit about ibm's open source support practice Now as Todd mentioned earlier, we are all experiencing an unprecedented time in history right now And organizations are being forced to adopt to new challenges And they're really looking for ways on how to rethink how business is done I'm fortunate enough to work within an area of ibm where we can help our clients address some of those big challenges specifically we provide support solutions for Multi-vendor software products and this also includes focusing on open source technologies So providing support solutions for commercial as well as community open source software Now about six months ago We actually commissioned a study with forester consulting Because we wanted to examine in depth how our clients were using open source software across their enterprises And one area that we focused on specifically was really around the challenges that organizations face when they're not only building with But also deploying and maintaining solutions built on open technologies So what we wanted to do was identify, you know, some of those key adoption challenges And some of those inhibitors that organizations face when deploying, you know open source at scale So in my opinion if we were to rerun that study today, I do think that we would see the biggest challenges You know the same ones popping up But I do feel that they would be viewed through a slightly different lens And that's just what I wanted to talk a little bit about today You know enterprises are now trying to figure out how they move their businesses forward Well adjusting to a lot of different things. So whether that's, you know, a remote workforce, whether it's new ways of You know selling and delivering services and products Or of course, you know, additional cost pressures that that we often see So a couple of the ones that have changed slightly Again, in my opinion Are the ones that I've got listed here. So first, let's talk a little bit about governance now In my experience, if you ask 10 different people what governance means you're going to get 10 different answers because it's a very broad topic But when I talk about governance, it really refers to kind of the people and processes that are used to create a management system around technology usage And we're finding that this is actually a really hot topic right now Obviously, it's because we're using, you know, we see customers using more and more open technologies for mission and critical it But they're also looking for help with a much broader set of services And I would actually argue that all the challenges that you see listed here on the page They're actually all elements of a good governance solution When that's still hot, you know, top of mind for customers is complex software stacks You know, as we continue to see the acceleration of digital transformation initiatives It's not uncommon for, you know, our customers to be using 510 or even a lot more different packages when they're creating individual solutions And what this challenge is it's really about making sure that, you know, all of those different packages They all work together in harmony and they stay that way when something in the environment changes Another one that's top of mind right now is really around choice. It's having too much choice. So initially, uh, this was about selecting the right technologies So what were the technologies that were best suited to achieve your business objectives? But this has actually taken on a whole new context because what we're seeing now is that enterprises are really trying to determine If this is an area of cost optimization and we get lots of questions around that Um, and the other one I'd like to talk about is really just enterprise support Um, you know another trend that we continue to see is that organizations are leveraging more and more community open source in production And there's a lot of different reasons for that But one of the biggest challenges they face when they do this is around support So it's a lack of enterprise quality support for these products and that's really where my team comes in So look my organization We work with our customers to build comprehensive support solutions for the open ecosystem You know our goal is to help address and build solutions for all of the challenges that I've just discussed Now a lot of people know us And are familiar with the fact that we from providing support on the linux operating system and a lot of commercial open source products You know in excess of of two decades But they're not familiar with our broader portfolio of services Which includes actually our community open source support offering And this is where we have the ability to provide that enterprise class support on over 150 different versions of community open source products Um, now the other thing is around our advisory services So that's where we provide assistance to clients around things like interoperability guidance installation configuration Um, really just different services to help address some of these challenges that I just talked about today So look if you're part of a development team or you're a business leader and you're facing some of those challenges that I've covered Um, I would love to talk to you. So please um after our session today come on by the ibm digital booth I'll be there along with some of my team to answer some questions So when you get there just click on the open source support link and I'd love to hear from you With that I'll turn it back over to Todd. Thanks to summarize You've seen quite a bit today. We Also been able to give a very deserving community A hand up with with some funds and some resources to help them um, we thank the Pioneer asked the dev organization For all the good work that they're doing in columbia And I ask that if if you feel inclined, please join one of these projects or or join the the trusted ai committee and help us shape where things go These are important times and and this is a topic that is is going to help us as a world Organization of open source contributors help move the world forward. So thank you very much Thank you Todd and Camilla That was a great talk. Um, our next speaker is kosuke kawaguchi He is the creator of Jenkins and co-CEO and founder of launchable Prior to launchable, uh, kosuke served as cto of cloud bees and today he's going to talk about the symbiotic relationship between Jenkins and cloud bees Sharing his lessons learned and how to build business Value around a viable open source project. Please welcome kosuke kawaguchi. Hi, I'm kosuke I created this open source project called Jenkins about 15 years ago And then for the last 10 years or so until very recently I've been building cloud bees where I was a key part of building a business around this open source project And in that process I learned a lot. So today I wanted to talk about that lessons On my experience on building a business around by an open source project So um, so yeah, I guess I already talked a little bit about myself I you know, I started as a open source developer and then became a cto of this company And spend a you know, good bit of time trying to bridge this relationship between a company and a source project So much of what I talked about today kind of came from that experience things that got me thinking So, you know for the context of this conversation, it's not overly important What cloud bees does or what Jenkins is as open source project So suffice to say if you think of the cloud bees to Jenkins as what the red hat does the Linux Then hopefully you can understand more of what I'm going to talk today um, and that is you know, the flip side of it is I think the lessons that I Learned I think it's pretty universal to any open source project and any company is trying to lead it. So The first thing I think that made an impact for this project because of its Beening was this notion of you know, who owns the project and usually this is not the first questions that the founder of the open source project We think about Because it doesn't really you know, it feels like it doesn't really matter and it feels like a subtle problems And that is correct But when it matters it actually more matters a lot and it makes a huge difference So this is something I think it's worth thinking about So in case of thinking what happened was that the I used to work outside a company And at some point they wanted to exercise their control over the project so the way they chose to do it is by You know the trade claiming the trademark to the name of the project And then they told the developers that if they want to continue doing something They better accept the control by the by the company. So this naturally obviously pissed off the open source developers royally So that's how you know, the the new name was adopted and Jenkins and that's how the project was born so um Because of that origin story, I'm very happy to oops. I'm very happy to say Jenkins is a community-owned project So that is you know, that's that is why this project joined the Linux foundations. So that We have a neutral place where the project name means project is governed by Because I think one of the things that lessons that that fiasco in the beginning that I just talked about Taught me is that the projects open source projects that is owned by one company is fundamentally risky Even if the current owner is well behaving benevolent You know owner of the steward of the project. It is still just one wrong acquisition away from a disaster And that was exactly what happened to my previous employer So, you know, in order for other companies other participants to feel the ownership stake into this project and feeling comfortable, you know, putting their precious engineers time to this project I came to believe it's so much better to utilize the foundations like next foundations or in apache or eclipse or Really anything to do in that regard and I think I I think they derive the participation in ways that otherwise impossible But so I'm very proud of this setup But at the same time for business it does create challenges because you know yourselves people and marketing people can get so much value I look more straightforward association between the company and the project when they are one than the same So I think a good example that might be, you know, like a docker right the docker the company and docker the project One and the same and there's no need to explain those two things And their relationship, you know, I can't say the same thing with clavies and Jenkins So this is something that you know leadership of the company needs to be able to understand and articulate and defend And then there'll be always the constant questions of like a widely set up its chosen Another sort of a key question for me In the clavies was how to balance side to the open source investment against the company interest You know, like engineering resources are always precious like the regardless of the size of the company So there's always this tension between how much of that should be spent on pushing open source forward versus pushing the company forward So, um, I think for too long I feel like I failed to frame that into the right term So from one side, you know, one set of people are arguing for more investment in open source from the other side You know, some other set of people are arguing for more investment in the product And it kind of became a nasty tiger war and in the end like we ever control the resources between so That's somewhat There's a little bit like this tension between devs and ox and how the demox movement Uh, kind of came into being so I'm extra ashamed. I go one hand. I was pitching for that kind of message Right on the other side. I I failed to see the parallel between those two nasty stories So I think in looking back, I wish I spent more time figuring out You know, what is the right metrics that guides us the right level of investment between open source and the you know, the um the proprietary product side high baby sort of What are the lines in which we connect the open source products? You know, thriving viable open source project to the overall success and health of the business Because I think every reasonable company leadership would understand that the right investment level is not zero But the line between, you know, the the effort that's spent open source And how it contributes to the company needs to be drawn even if you know, the metrics might feel a little bit bullshit Even in that I think there's still a value in having some guideline the baseline that other people agree on So that you don't have to like turn every fight into You know, the tiger war. So that's that that coming up is that metrics is something I feel Um, I am the under invested and I still don't have a, you know, right answer But I think if I get to do the next turn next round, I think I know how to do this a little better So anyway, um You know off onto how to make these inside of open source projects So the first thing the the young club is a company did was to build a hosting service hosted service of this open source project Um, so, you know, the service hosted service was great But one because, you know, the you don't need to keep any changes you make proprietary In fact, it's so much easier if you can push them all upstream So in the early days when we really don't have that many engineers working on it The fact that our engineers can both push our services forward And also the open source forward at the same time from one commit has been incredibly useful To make us look bigger than we actually were And hosting also very nicely complements the key pain of open source, which is the overhead and time and effort It takes to keep the software running so So those were great But unfortunately Jenkins was not designed with this kind of high density multi-tenancy hosting in mind And these are the things that's very difficult to insert from after the fact So in the long run, you know, they You couldn't make economics work well enough. So this business sort of faded away But nonetheless, it provided this great horse stage of the rocket that allows us to take on the next way of adding value Which is the enterprise version so Enterprise version was great For all sorts of reasons. I think allow us to create a bigger value. It allows the company to build up more ip And then, you know sell that to multiple people and you know charge the full price for each one of those Like unlike hosting where you know, every every value you sell it comes to the high, you know Cost of goods sold so So that was great but it also Not great in the sense that it created a bandwidth challenge So this was around the time when this type of war was the most difficult because Your engineer is either working on the open source project Or they're working on the product because they're all they're completely different code base And then when they work on the products, they you know, from the prospect to open source It's it's it's as good as this It's not it's indistinguishable from them disappearing. So You end up needing to chase those two different boards and that's been that's that's painful and challenge And there's also another more subtle challenge that i'm going to try to explain here. So Now if you think about like a space of value That the open source could provide and or the we solve Right. So naturally there's this like organic growth, right? You know the circle deep presents the problem that open source already solved And then what's happening is like around the edges and the peripherals People are constantly pushing that envelope out and it tends to kind of grow over time slowly but steadily What the enterprise person does in essence is like it stakes A neighboring space of problem and value and then solve that in a separate circle, right? So Where this gets a problem is like imagine like you're some of your engineers In your company working on the open source project They are incentivized To not to grow open source into the directions toward the enterprise version. That's why this arrow is trying to be present You don't want the open source product to solve the same problem that the enterprise version is solving Because that's where you make money, right? So if not managed carefully what this ends up doing is it's sort of it could interfere with the natural organic way of open source growing And you can end up creating this station when somebody who is not if it doesn't have that bias when they look at it They might feel like there's this obvious growing Big pain that every key contributed product seems to be oblivious to And of course what's happening is that it's not that they're oblivious to this problem They're just they just don't want to solve that in open source because they feel like that's about the enterprise version I'm supposed to provide so if you know about the the what I guess what i'm trying to say is In the eyes of outsiders, you know, they don't appreciate those internal motivation Why the product doesn't solve this doesn't solve this pain doesn't solve these challenges Why it has this giant pain? So they might simply choose to go elsewhere and that in the long run Can cast a shadow in the viability of the open source project and that is not good So anyway, the third thing that the company because this club is taken is the support And this was also great if you can get there and I say that because in the early days of the small company You know, let's say if you have just a signal with a few engineers It cannot it can't provide the support in a straight face Now you need something you need to achieve a sufficient scale and the creativity as a business before Companies would come to you and ask you to take your money to provide them the support So once you get there though It's really great because you know, your customers will drive you to improve open source Like they're coming to you to solve the pain they have in open source and they they actually much prefer If the the way you solve it is also a part of the open source. So the host is in something else So that's great and it's like I'm the the it was the same station with the hosting stations except What you need to be careful is the people who Who buy support from you are actually a small subset Of small uneven subset of your audience So if you end up spending too much time to solve their problems and neglect the other Larger number of smaller ordinary voices users Then you might end up creating this kind of skew to In the open source project again as well So for example, you might you know, you might cater to more complex use cases more flexibility, etc And you might not value the ease of use or ease of installation or somebody who is only using it casually And that's so that can be a problem And it also you know support fundamentally denies on the fact that your product is somewhat painful to use And that's not really a healthy long-term tenable stations Because the same frustrations that led your users to become your customers Can also push them to your computing solutions and you you know, you not only lose the revenue, but you might also lose the user so So I think in some sense this This sort of underscores the importance of figuring out the right level of investment in the open source Almost oblivious and then kind of give them in a free hand so that they can solve the problem They see in the open source period But you know with all that said I really think the support is a great way to add value That it really adds value it makes the open source project form a credible in the eyes of the users, for example And support is so much more than just asking you know answering questions. And that's something I learned Over the time of copies. So, you know, I did you mind it Anyway, so the last phase I think of this business to open source relationship is that the business choose to move up stack Right. So in the process of you know, getting to know your customers and users so well Um, and your company getting bigger You can now tackle on the bigger challenges that the customers are facing that increase the open source as a part of it But it's not the whole thing And I feel like that's certainly what happened. The guy is when we tackled the software delivery management Which is to say how the organization tackles the effective software delivery Where it's it's naturally increased the city as a part of it, but that's not the entity so so finally like we could you know Some of these second dilemmas and conflicts that I talked about earlier are no longer the program for us So, um, I'm gonna be I'm short on time. So let me quickly talk about some of the other lessons I learned in the course of clavism thinking and one is that You know, as an ambassador from the from the company making money in and around open source products Um, you don't you don't need to be apologetic about the fact that your participation into this open source project Is bringing revenue to your company and you don't you just you don't want to become descending either But for example, like you need to help other people in the community see the value that your company brings to the community Including for example the credibility that it brings the project Which I just mentioned about or the fact that the company can put other different functions like design Marketing event and so on so forth to the project and that does not happen in the organic the pure developer community Right Or like a company can put together organized team of engineers to take on the bigger big effort Which is traditionally it's difficult for a bunch of volunteers to coordinate Also early on when the company was small, we only had people who knew how to roll in the open source project So, you know, it was easy but as a company will be here and we wanted to put other different function people than developers It's kind of important to help them understand how to be effective in the open source projects Like there's this tendency to you know, what you don't want to be is like a come across as a faceless group of people And then like hiding behind the banner of the company Like, you know, we all know that what xd open source project is a human relationship a personal relationship between participants And that's something I think important for the your your company people understand Like they need to be able to engage with the other participants and the product on their own and there it's okay for them to have their own opinions and It also means I think the project needs to be both to accept the fact that there are other participants people not writing source code And they are actually an important part of the community. So educating that I think is also important And you know, the hiring people from the community has also been interesting questions and challenges So, you know, it was great that you can bring in qualified people from day one But it also creates by which I mean like a higher contributors of the community into your company But it also tends to create a monoculture Because they are kind of all the fact that they are being a long time contributor And they tend to you know, it tends to bring like mindless folks And then so that's And that makes that creates a certain blind spots like it kind of creates a group thing And the that makes it difficult for that group to address the pain that other You know people from other backgrounds, you see so I kind of fundamentally believe in this diversity And I don't just mean like You know, like a race or the gender or really like a different background different perceptions and different values they place on the technology And those I think the conversation and exchanging of ideas among these people Actually pretty critical to create a thriving open source project. So And then another part is like as you get bigger and you keep hiring from the community You naturally like lose that and then some of these people you put on to work on other things in open source You start to deplete the pool of contributors from the project and that's not great. So These people can be you know Yeah, anyway, so that I can I can talk a lot about this point, but in the interest of time, let's move on so the last bit is that the It's sort of important they always have some level of creative destructions I think in viable open source project this naturally happens or else it didn't have survived But the company I think Tends to coordinate its act together far more than the bunch of volunteer open source devoprons are willing to do So they tend to you know, they tend to not to want to run this experiment. So like wild shot And then etc now So in that coordination is great because that's what makes the organization attractive But if you think about it, if you have to convince everyone about something That you want to do then you only get to really do incremental improvements And then that's great. That's okay for a while. But in the long run that just alone is going to kill innovations. So I You know, if everything needs to be aligned then also like none of these efforts can fail because it's so interdependent on each other And if you cannot take on projects that might fail, then again, you're not going to have innovations So I sort of like one thing I learned is it's important to have a little bit of slack Like a little bit of willingness to say Well, this may or may not work out and then be able to take it on and be able to kill them if you discover that it is not working out so If you wrap that up, you know in the end I kind of feel like I've been telling you whole lots of why Why this is a challenge? So I want I want to end my talk on the high note You know despite all the challenges, you know I still very much believe in open source because open source is in the world Like it's just handstand better way of developing software. It creates more flexible software It creates more high-equality software it evolves faster and you know, like I'm preaching this to the to the room full of believers But I really think it's too like it helps us tap into diverse set of talents from around the world Coming from different perspective and different parts of tech stack and collectively I think even though we are not perfect I think it just tends to create a far better software than group of engineers working for the same company from coming from a similar origin And I just fundamentally love this idea like, you know From anywhere from the world we can work together And they did not like this just does not happen in so many other like model preparations so I think the open source business Compliment is there for and it helps Helps the world to have more open source. So that I think makes this endeavor worthwhile And then on that note, I wanted to end my talk. Thank you very much Good morning everyone It's so exciting to be here and I thought I would start off by telling you the backstory The backstory of how I became an advocate for inclusive workplaces And this is actually my second career in my first career. I spent about 25 years working in tech building software products I started out as a software engineer writing code for a living And over time I moved into leadership roles And most recently I was a vice president of engineering at adobe And during that 25 years, I noticed a decline happening a decline in gender diversity And so while I was still at adobe, I started being a very vocal advocate for women at the company I started our women's employee resource group I started mentoring a lot of women and Basically looking out for women across the company I love doing that work so much that about seven eight years ago now I started my own business as a leadership coach for women working in tech And that business I love doing that work. It's very fulfilling. I think I helped my clients But I have to tell you All of them are working in environments where And companies where basically the closer you get to the c-suite the ceo The mailer and paler it gets And well with all due respect to anyone who's male or pale listening to me today It's just the demographics. It's what it looks like in tech And so I started paying attention to how people could be more inclusive at work And not just for women but for people of color for black people for people of different religious backgrounds gender sexual orientations and identities Ages abilities I started looking at what could we do to make all of tech more inclusive I kind of wanted to change the world And of course these days, what's the first thing anyone does when they want to change the world? Well, either you make a hashtag Or a twitter handle And so about five years ago, I started the twitter handle at better allies And this twitter handle my goal was to share simple everyday actions people could take to be more inclusive at work Things like, you know, I'm going to notice when an interruption happens in a meeting and redirect the conversation back to the person who was interrupted I would share things such as well I'm going to ask at the next engineering all hands what we are doing about pay inequity And ask if we can, you know, raise awareness of what pay inequity is and do something about it These are just simple everyday actions I would tweet Now over time I started getting speaking engagements And I started speaking about this approach this better allies approach of simple everyday actions and inevitably during the q&a someone would ask Hey, uh, Karen, do you have a book? And for many years I kept saying no, I don't have a book and they're like well We'd like more of this we want more of these everyday actions This seems so approachable and so smart so so actionable And so I eventually wrote my books Um, I didn't just write one I wrote two um The first book is better allies everyday actions to create inclusive workplaces And I followed it up with the better allies approach to hiring And I think this topic is actually more important than ever before because In the wake of george floyd's murder and countless others People around the world and definitely here in the united states Are not satisfied with the status quo They do not want the racial inequity to continue that we've been seeing in our country Workplaces and so forth So people are protesting People are donating money People are electing new officials and demanding policy change And I hope that for all of you here today That in addition to anything else you're doing That you will also be looking for how you can disrupt the status quo in your workplaces to be more inclusive Of people from you know, definitely be more inclusive of black people and people from other underrepresented groups And I firmly believe that This whole job of inclusion You don't have to have it on your business card You don't have to be your chief diversity and inclusion and belonging officer to make a difference There are things all of us can be doing every day In our workplaces and in our open source communities to be more inclusive And so what does this look like? Well, first up You need to get to know people who are different from you from different backgrounds and different gender orientations and so forth You need to get to know people And unfortunately Most of us have these just like me networks these networks full of people who Are similar to us because we'd like hanging out with them We have things in common with them Whether that is going to a sporting event like these guys here on the slide or something else We have something in common we like hanging out with them and we tend to be drawn to people who are like us Now I want all of you to reflect for a minute About your own professional network Would you say it is very diverse somewhat diverse Or you could do better I bet as you reflect on your own network You most of us would probably vote on number two or three here like we have some work to do. They're not super diverse And I want you to think especially if you are a white listening to me I want you to think about What the experience might be for For example, just one demographic a black woman A black woman in your workplace or community. What's her experience like? And I'm going to share some survey results Where black women surveyed said their manager has met one on one with other people on their team, but not with them another survey of found that black women And I apologize that supposed to say 60 percent almost 60 percent report that they've never had an informal interaction with a senior leader More than half of black women have never had a senior had had a senior leader do things and say things like Well, you know, how was your weekend? Maybe in the coffee room or the break room or in the elevator into the office They've never had a senior leader reach out to them in a virtual chat saying hey nice to see you here Those are what informal interactions are like and those lead to feeling belonging and inclusion in the workplace And I'll also say what happens outside of work Outside of work There's social science research showing that men tend to hang out with other male co-workers Whether that's on the golf course or a virtual poker game or something else But men tend to hang out with male co-workers and that deepens and strengthens their professional network even though they're outside the office Women by contrast we tend to hang out with people in our community people whether we Perhaps we're in a book club or we are volunteering at a nonprofit or If we have young children we're hanging out with parents at their school Perhaps it's a religious organization we belong to So we women are strength or are broadening our network, but not strengthening the deep professional ties like the men And over time that really adds up it adds up in terms of this inequity in terms of how powerful a network can be And these just like mean networks really limit diversity Let's face it. You know As we think about who we hire we look to our networks. We trust those people We want to hire them and recommend them. We know them. We know they can do the job So if we have homogenous networks, we will hire homogeneity And these just like mean networks also impact who we trust who we trust at work or in our communities As we think about stretch assignments new leadership positions promotions Maybe if we're doing a reorganization or doing some succession planning as a leader We know and trust The people we've been hanging out with we've been spending time with And those are the people we're going to put forth for these new opportunities So I want to share four everyday actions. All of you can take to diversify your network And the first is get to know colleagues who don't look like you found so obvious But the next time you're at a live event, you know, go over and say hello to someone during a networking opportunity Um, perhaps it is doing something more virtually as well But get to know them introduce yourself start a conversation I also recommend you join slack channels or other forums for underrepresented groups Many of them exist And all you have to do is ask permission if you as not a member of that demographic can join So that you can listen and learn about the conversation And get to know people You can also attend events for people from different underrepresented groups. For example I am a white woman. I've recently been to some black in tech events, which have been incredibly insightful powerful And I've gotten to know new people Um, I'm I'm straight. I could attend a lesbian suite tech event again to get to know folks understand the conversations Understand some of the discussions they're having these events are out there. They're easy to attend virtually And if you're not sure you'd be welcome again, just ask the organizers or check the website They're often open to allies And last but not least look to volunteer with nonprofits who are serving these marginalized communities nonprofits such as Maybe there is a robotics program at a local high school that you could volunteer with Or be a mentor virtually for a coding bootcamp that serves one of these communities So just some ideas of how you can diversify your network But that really is the first step in being a better ally and creating a more inclusive environment So once you have diversified your network You can get started with the next step which is to sponsor people What does sponsorship look like? Maybe you have formal programs at your company. That's great But you can also look to sponsor in smaller ways without having it be a formal network a formal program Here are five things you can think about doing To sponsor people from underrepresented groups co-workers colleagues members of open source communities that you belong to The first is recommend them for stretch assignments and speaking opportunities You know, these things are like these rocket booster rocket fuel for one's career They help someone gain visibility They open doors They help someone build credibility with a group So as you think about the next time you have to recommend someone for a speaking opportunity It could just be at your engineering all hands Or at a big conference Think about who just normally comes to mind And if that is not someone from an underrepresented group, you know, maybe take a step back reflect on your network Think about someone else that you could recommend and if no one comes to mind from an underrepresented group Well, maybe you need to go back to the first step and diversify your network more so that you do know these people They're out there. They're talented. They're skilled. They can do the job Second thing is endorse them publicly You know, I was on the receiving end of one of these endorsements And it felt so good I mentioned I used to work at adobe And when I first joined the company, I remember being in a large engineering leadership meeting And I heard my boss Who was a very respected longtime employee Um, and senior vice president of engineering. I heard my boy my boss say Well, what I learned from Karen is the following And he went on to say something Those few words of what I learned from Karen Were a game changer for me. They elevated my standing with my new peers This very respected person learned something from me They he gave me credibility in the moment, which was long lasting and it as I said it felt really good So that's one example of how you can endorse someone publicly is share something you learn from them There are other ways to do this too Think about how you endorse people publicly again and think about upping your game and doing it Even more for people from underrepresented groups third thing Share their career goals With influencers with decision makers As you get to know people from underrepresented groups, do you know what they want to be doing? Do they want to move ahead on their career ladder? Do they want to work in some new technology space? Do they want to get involved in, you know, if it's an open source community with one of your leadership roles down the road Find out what they want to be doing and then Look for opportunities to connect the dots for them to these opportunities fourth Invite them to high-profile meetings. Now you may be thinking, oh my gosh, I had so many meetings already Who would want to go to another meeting? But these high-profile meetings can be game changers for people who aren't normally invited high-profile meetings such as You know a customer advisory meeting Or some strategic planning meeting where you're planning the future Or it could just be a virtual drinks with some newly Hired, you know vip at your company or in your organization Look to invite people from these groups who really don't have access So they can start expanding their network with those people But also have insight into the conversations that are happening in the room And if you feel like you need permission before you invite someone, go ahead and get the permission That's fine. If you don't ask, it's not going to happen And fifth, last but not least, I encourage you to speak their name when they're not around What do I mean by this? I was watching a TED Talk by Carla Harris and Carla Harris was a or is a senior vice chairman at Morden Stanley And she gave a TED Talk in 2018 where she talked about meritocracy Or the lack thereof actually She talked and debunked the myth that all you have to do to get ahead is to do good work And that people will notice and you'll advance She debunked that myth and instead pointed out how powerful and how important it is to have someone Who is in those calibration meetings in those promotion meetings someone who is speaking your name And who knows you well enough to talk about your accomplishments and your potential So this is a powerful way to sponsor someone Let's get to know them enough so that you can speak their name and advocate for them in the meetings you're attending All right, so A quick note for my open source friends out there There is language that we use in tech that is not inclusive And here are just two examples. Let's use a blacklist to deny access to our trial product or our service Or the master slave architecture that we've configured for our servers or database or whatever These are not very inclusive at all and I encourage all of you to think about changing your open source code to Be more inclusive a simple instead of blacklist. It could be a blocklist. That's what you're doing your blocking access instead of master slave something like Primary replica for example, maybe you don't like that exact phrasing. That's fine. Choose something that you think is is appropriate for your technology Okay, I'm going to wrap it up now And I hope that through my talk today You also feel and want to join me on this journey of like inclusion being a job for everyone Not just for people who have diversity inclusion and belonging on their on their business card There's something we all can do And if you'd like to learn more about this, I have my books. I would encourage you to read better allies I also have a newsletter that I send out every Every friday. It's called five ally actions I kind of do a roundup of what I've seen during the week and provide these tangible everyday actions people can take And you can also follow me on social media at better allies And a final note. I will head over to the Slap channel called to Dash track dash diversity dash inclusion I'll head over there for about the next 15 or 20 minutes and answer any questions and continue the conversation there Thank you very much. And with that, I'm going to hand it back to Jim Thank you, uh, Karen. That was a wonderful talk and uh, I loved your book Uh, particularly the chapter on everyday language. I have to admit I have been trying to Eradicate the term guys from my language, which just almost became a verbal tick But you have some pointers in your book, uh, and uh, I am going to keep working on that So I really appreciate the work you're doing and and your book really is an inspiration people should go out and get that book Uh, you also mentioned, uh, uh, uh, eradicating racially charged language in code Could incidentally our next speaker, uh, published a blog yesterday on Making open source more inclusive by eradicating problematic language Uh chris rite from uh red hat is suggesting we do that Uh, and you'll be seeing some news from uh, preamp. Sharma Who is the head of our cloud native computing foundation? She's going to be leading an initiative from the linux foundation to help coordinate eradicating That very language. So, uh, thank you for the inspiration this morning and, uh, Loved your book again folks. Please go out and get karen's book. It's a full of wonderful advice on how to become An ally So next we're going to hear from chris rite senior vice president and cto at red hat. Please welcome chris Open source code runs our largest companies our governments the infrastructure of the internet It powers scientific discovery and space travel Building software using the open source development process creates real business value sure But not all the world's problems are business related In fact, some of the biggest issues we face can't be solved by business alone Sometimes we're so excited about what's possible that we forget about social responsibility and the repercussions of our actions Like racially problematic language that filters into open source code and it terminology Like the implicit bias within ai models Where the need to secure personal privacy from surveillance Where the global issues such as our carbon footprint and climate change Will respond into a global pandemic like covet 19 These are all examples where communities can gather and make a difference In fact in response to the current pandemic red hatters really wanted to help So we identified a few specific projects And are encouraging red hatters to work together in these projects to pitch in and help Open emr an open source electronic medical record system used by health providers for scheduling tracking and treating patients COVID net an open source neural network used to detect COVID-19 from chest x-rays And connected health IDAS bringing camel drools kafka and kube flow together into an intelligent data as a service platform That enables health care providers to make informed decisions And acknowledging this virtual event I'd be remiss not to highlight that we can all do our part to fight COVID-19 by practicing social distancing and wearing a mask in public We're in this together each and every one of us Open source communities like these are one way we can facilitate global collaboration in order to create impact right now A way any of us can contribute We cannot overcome challenges like these without continued broad cooperation across organizations and societies at all levels from technology to policy to individual actions And it's worth noting That technological solutions created in isolation from the parties they may affect will typically fall short All right So let me bring this back to open source and it Open source software development is about opening access and removing the barrier between IP owners and users It enables engagement between developers and users and empowers communities with freedom with flexibility and choice There's creative value in the virtuous cycle of user driven innovation Collaboration to solve big challenges is not at all new Collaboration drove our industrial revolutions by agreeing to uniform standards of size and measurement for industrial spanning railroads and international communication channels Or take the scientific method, for example We eradicated diseases like smallpox by enabling the scientific community to work together across international boundaries Open access is crucial when building the software and infrastructure that will help solve today's problems The world needs IT infrastructure that does not constrain cooperation in order to maximize business value We must ensure innovators can focus on creating solutions and worry less about whether supporting technologies allow their experimentation This flexibility and choice is why red hat is focused on the open hybrid cloud We're building a platform for this essential collaboration Now we want our portfolio to be successful obviously, but also responsible And at the same time we want to continue our work supporting innovation across the digital landscape Even if we don't see the value of that innovation immediately or directly It matters to someone somewhere as they scratched that itch And someday we may find it matters to us too in ways we couldn't imagine because our eyes were focused on a different goal After all your memory foam mattress wouldn't exist if nasa didn't need to make pilots comfortable on long flights So when it comes to it operations we can apply that same approach building a place for information to be shared Building the railroad to connect the community Sharing the formula that makes up your mattress Because the history of operations isn't like that of railroads or communication standards or medical and scientific practice It's not all connected. It's not a community It's operational knowledge in silos divided by industry By individual business practices even among teams in the same organization And as open source communities have redefined how software is developed and features are delivered We must advance and consider how communities deliver operational excellence along with open source software Operate first is how we address these divisions and how we'll build an operations community Operate first is our effort to encapsulate Operational excellence within our platform in in order to enable creativity across our broad partner ecosystem Operate first is about making operational considerations as much a part of what we do as upstream first is for code Making operations first our guiding principle in the development of our cloud computing platforms We're doing what we've always done We're connecting with our communities and using the foundations and principles of open source to meet the challenges of today In this way, we continue to try to make room for all the voices and all the innovation Even the ones we're blind to today and we ensure that open source can continue to unlock the world's potential Thank you Thank you chris Our next speaker is Megan Byrd Sineke. She's a manager of research and operations in the google open source program office Where she champions open source citizenship within google and the industry at large Today she'll share a few words on citizenship during cove. Welcome, Megan Thank you. That's what google wants to say today COVID has impacted open source in all industries And we are so grateful to work with so many of you to make sure open source stays Sustainable during this really challenging time of course google has been committed to open source citizenship Way before COVID and that's because we use over 2000 projects and contribute to them as well We need to make sure these projects remain future-proofed and we do this with three main sustainability efforts First we contribute talent whether it's code or tech writers design. You name it plus we Contribute funds directly to projects And we create sustainability programs that we use and also share broadly with the industry and we hope you'll check these out such as oss fuzz Which uncovers security vulnerabilities and it's used today by 250 projects and has already filed 16,000 bugs and 30,000 vulnerabilities We also have google summer of code Which is a 15 year long program that has brought 15,000 students to over 680 projects and together they have contributed over 36 million lines of code to open source Plus we have our newest program season of docs that brings tech writers into projects and so far they help Improve the documentation for 44 projects And I hope you'll check these out. We really do want to share these resources with everyone in the industry especially during this time of COVID And that's because so many challenges popped up seemingly overnight First there were financial challenges as events were canceled or we had to move to virtual events Plus there were talent shortages as people had to find new jobs and didn't have time to contribute Or they were finding themselves at home providing care for people they love and working at the same time And of course We had to all figure out how to take our communities fully online and understand how to make that work such as Meetups or conferences like this It hasn't been easy and there's been some pain that came with these challenges But what's really inspired me Is how well individuals and organizations came together and started to solve this and they started solving it quickly And i'm so proud of the ways that google Was able to step up and help with everyone else We started to reach out to projects that we use to find out What they're experiencing and seeing how we can help them and it's helped us form stronger relationships that we can build off of now into the future Plus we pivoted our internship program You just can't have students go into your offices And so we decided to bring them into open source And so now a thousand interns are going to work with googlers who are going to mentor them So they contribute well and they do it right Plus many googlers have been contributing to open source on the front lines with projects like next strain or covet act now in schema.org And we also Share it everyone share with everyone an online community guide And it's to help you Learn how to quickly pivot and have your online events and it comes from all of the tips and tricks that we've learned over the years Providing this here at google I'm really honored that we can help in these ways But mostly i'm just so grateful that we can work together to make sure Open source remains sustainable because it can only be sustainable if we work together So you can count on google to continue its commitment to citizenship Now and beyond covet And if you would like to contribute as well There's some simple ways to do so and you don't need to be a large enterprise to make a difference You can go into your project and see which issues you can answer today You can also look for some languishing pull requests and close them out And you can do a small donation to a project. It can really make a difference You might buy some swag or maybe you just do a small membership fee And again, we really would like to share our open source resources with you and all of our sustainability program So please check them out at open source dot google and lastly We want to hear new ideas of how we can help open source. So please share your ideas Use today's platform And let us know what we can be doing. We're going to be listening So thank you so much for your time and especially thank you for contributing to open source Thank you very much. Uh, Megan. We hope to see more Our next speaker is eddie taheda He is the director of cloud dot gov in the general services administration of the u.s. Government Created by industry experts cloud dot gov is a response to large-scale technology failures like the initial launch of healthcare dot gov Today eddie will highlight the impacts of open source software and working in the open to bring high scalability High security and highly compliant solutions to one of those regulated environments in the world. Welcome eddie Hi, my name is eddie taheda and and i'm the director of cloud dot gov We're housed within another office called, uh, the technology transformation service within gsa in the federal government So my goal in this presentation is to make the case that pass should be defaulted in government I think some of the experiences that I have will show you why I think this might be the case and hopefully you find it a valuable perspective as well But first I want to give you a brief overview of cloud dot gov How the government's mission is to make it easy for government to access cloud services It's pretty straightforward We're created by another office within Uh, gsa called atnf and this is a digital consulting office that works across the federal government To help improve the user experience of government services by helping them build and buy technology We've had some great projects. I recommend you all check it out at um atnf.gsa.gov but some of the ones that you may have heard of are usaspending.gov which tracks a lot of government spending data And uh fbi crime explorer which looks at crime data One of the things that These early teams found themselves running into in these projects was that they found They ran through the same exact hurdles over and over again first provisioning resources provisioning these cloud services could take weeks And then the ato process which is the gold standard the thing that allows you to move To production that it means authority to operate That process could take months And most of it is primarily because of documentation that you have to build before you launch to production So instead of repeating these processes over and over again, what the team did was implement a version of cloud foundry in-house And they called the cloud.gov This is also there's also this uh the special sauce called fed ramp which is Something that allows agencies to inherit the secure the security compliance from other cloud providers So i'll get more into that i'll talk more about that in a second because i think that that is going to be an important part of this Since cloud.gov launched it's worked across The federal government at a lot of different agencies. So we've been able to Have a pretty good view of the federal government And everything we do is open source you can go to cloud.gov to learn more Or check out our repository on github where you can see all of our source code everything we do happens in the open We love sharing our experiences and our lessons. So check it out So this is what I was talking about this is One of the index pages of a 400 page report that you have to create in order for you to launch to production for a moderate level system And this has to be created for every application that you are going to launch to production No matter what uh, some might be shorter might be only 200 pages if it's uh If it's impact if the impact is low, but it could be Many more hundreds of pages if this has if there are some serious security risks with launching And what cloud.gov is able to do is say out of Say 325 security controls that must be documented for you to move to production for a moderate system We can handle 269 of those within cloud.gov. So your Uh documentation process is it's a lot simpler You are responsible for 41 that we could work together on and then 15 or so that you are responsible Uh as somebody who is um as the app developer So just in this diagram, you can see what it is that cloud.gov provides And you've all probably seen this diagram showing How a platform as a service allows you to Think and work higher on the stack and not have to worry about All the lower level components of your application But this takes on a whole new meaning in the federal government Where it's not just about the technology that you're managing. It's also about the documentation And the atl that you need to have in place before you move to production So biggest benefits cloud.gov you can move to production sooner You can provide a consistent developer experience. So once you've worked in one agency you can work on another agency's project with a similar toolkit And small businesses love the platform because small businesses don't like to do a lot of this documentation This is not where the value lies In many ways, it's what excludes a lot of businesses from being able to participate and work with the federal government So as the public cloud becomes much more sophisticated, it's becoming a lot more complex as well One thing that we know about complexity and choice is that it can be overwhelming Now this has been studied from a lot of different perspectives In psychology, there's this idea of paradox of choice about how people are less satisfied with individual choices that they make The more choices that they have Behavioral economics, the people overwhelmed by choices and don't often make the best decisions for themselves And we need to nudge them to make sure that they for example enroll in the retirement plan And even in software development, we have seen the rise of convention over Convention over configuration, which um, especially in the early 2000s where there was a focus on Having best practices baked into the platform as opposed to a lot of XML files, which We all had to edit So this is where platform as the service comes back into the conversation You know Kelsey Hightower, which I suspect most people here know Um has been talking about this recently, you know, he he recently tweeted Just a couple of weeks ago that there's a ton of effort attempting to modernize application of an application at the infrastructure layer But there isn't equal investments at the application layer and thinks that frameworks and application servers There needs to be a lot more focus on them. Otherwise, we're only solving half of the problem And in government, we're already seeing increased interest in paths We've had a number of folks reach out to us who said, you know, we've built these complex tools these complex systems Serve our homegrown environments, but we are willing to give up control for simplicity It's becoming too hard for us to manage And right now we're at a really interesting phase where Orchestration tools like kubernetes are everywhere This is this is part of the shift and part of the power that allowed people to access a lot of these different tools But I think that that's not the whole picture. We need to start thinking also about the experience of developers And this is where cloud project kicks in We can replace we can start thinking more about Kubernetes and and different components of the developer experience to be in the background They don't have to be something that developers interacting with every day And we can provide Government employees and contractors a consistent developer experiences while the back end a lot of that technology in the back end can change And this is massive in government We can build we can have automated security compliance requirements built in directly into the stack Agencies will be able to attract new businesses who will be able to build on an existing infrastructure that they can trust and become familiar with And we also can leave space for some projects that do need to squeeze out every last value out of the infrastructure But in the future if we're going to continue to invest in the cloud Especially in the federal government where we're just getting started when you start thinking about the next generation of developers That are going to be maintaining these tools Yeah, we love sharing our experiences um With agencies and other businesses If you're interested in learning more Feel free to reach out Thank you Thanks, eddie Our final speaker today is also going to touch on the effect of corona virus and how it's impacted us all Grace francisco is vice president of worldwide developer relations and education at mongo dv And has for over two decades Been working as a leader in worldwide developer Initiatives at companies such as microsoft into it yodely atlassian in roadblocks Today she will talk about community and belonging in the time of corona virus. Welcome grace Good morning. Good afternoon and good evening to all of you wherever you may be dialed in for this event My name is grace francisco. I'm the head of developer relations for mongo dv Um, and I've had the great wealth Privilege of being in developer relations for over 16 years across a variety of different companies both large and small I recently also joined the Board of the Drupal Association Which was a great honor for me having worked with the Drupal community Well over a decade ago while I was still at microsoft It goes without saying that we are living under extraordinary times Today and while we've been sheltered in place for several months now here in my area I've been thinking a lot about this book. I read many many years ago Love in the time of cholera by gabriela garcia marquez for which I Had the inspiration for the title of my own talk today Cholera was actually a pandemic as well and there are seven Incidences of cholera over the course of 150 plus years And in this book largely on the surface It's about this romance between these two people over the course of 50 years where in that 50 year time frame They were separated by time space a marriage cholera and war And while I've been thinking about this and developer relations during this pandemic I think about the fact that I certainly hope that it doesn't take us 50 plus years For us to have meaningful connections again with developers as we do our work And the other thing that comes to mind for me frequently as I get up is that I've woken up into some wacky episode of the twilight zone And so very appropriately the washington post had read this article about seven specific episodes It seems so appropriate for this particular time And interestingly the pilot episode of the twilight zone itself, which was entitled where is everybody Is very appropriate for today It opens up with this air force officer who wakes up not knowing who he is where he is And he wanders about this empty town looking looking for someone Anyone and as his panic escalates as he's not finding people but finding signs of life He runs out into the open space into the town square Screaming where is everybody and he's been trying to wake himself up saying it's time to wake up. It's time to wake up And you know, this is very relevant to me right now as we live through this pandemic And the virus has really significantly changed the way we internet As many of us are seeking to connect virtually across social networks like facebook Or to really forget about this experience for a brief moment by entertaining ourselves And not surprisingly, we're not on the go right now. So mobile app usage has plummeted And in this period where we've all been sheltered in place Many of us are seeking minute by minute updates on the news and so news channels have gone up significantly in traffic As we sit and ponder What's going on in the world? What the latest updates are about coronavirus about what's going on with the riots and protests and really Thinking where is everybody? Where is everybody? Is everybody okay? And I will tell you where everybody is right now. They're all here in mucket land on zoom Trying to connect on things like even google duo and house party these social networks that were Really not being used much until recently during this pandemic. We're all striving to reconnect to still have that social fabric And yet is this really how we want to connect? Well, no, it's more like this being a little bit more personal with someone one on one Except that you try to do this over zoom and kermi is actually looking off into some other part of the screen And so his eyes aren't looking at you. He thinks he's looking at you But he's not and you have the same experience So you actually miss the true connection and it becomes exhausting to actually try to interrelate And to feel that connection when you're not actually having that face-to-face eye-to-eye connection And we are all over taxing our home internet as many of you know And we are in these zooms or whatever a video platform that you're on And we often hiccup our way through internet space and we leave our meetings frozen like this as our internet hiccups And freezes us in time and often have this expression like Han Solo being frozen in carbonite And this this is the impression that we leave our colleagues as we drop out suddenly from that meeting Well, I don't know about you guys, but that's exhausting So sometimes I just have to take a break from that virtual space and be out in the real world and so I go out on this Walk to contemplate the meaning of life and how to belong in this world or we have to have social distancing And I walk these deserted streets thinking about how to belong when you can't really be there in person How do we belong and have meaning? And so I take these long walks and I contemplate contemplate Then I get home with my furry pets who are absolutely Exhausted with my multiple walks a day contemplating the meaning of life And how to belong and how to relate in this virtual space of ours And really these poor pops are reflecting the absolute sure exhaustion We're all facing right now and trying to make this work in this virtual format Some of us have really been leaning into learning as we've been sheltered in place and interestingly these massive open online courses that were declining have seen seven times the traffic During the pandemic than they have in previous periods And so people are reskilling learning new programming languages new frameworks new technology disciplines like data science in their time Sheltered in place, which is great interestingly though the most popular course the breakout hit during the pandemic is really about the science of well-being And not surprisingly it's about well-being because we're all struggling to keep our sanity during this pandemic That's really crazy twilight zone era of ours that we're experiencing together Evan's data published this report a while ago forecasting that by the end of 2019 We would have well over 24 million developers through the end of 2019 And these are global professional developers I expect that this forecast is going to be changed quite a bit in the coming years in terms of the volume of growth given All of this new learning and people really leaning into And we are very fortunate in tech to have work that can be easily done From home and so people are going to be looking to these kinds of Workloads and jobs that can be done from home as this pandemic is going to be here for quite some time And we're seeing massive shifts in the biggest developer conferences either Canceling or virtualizing or postponing in hopes for that in-person experience again And now we get to this picture of fish. Why am I showing you pictures of fish? And this is the part where I where I'm a broken record with my developer relations team about the fact that we can't possibly meet 24 million developers all in person anyway This is a discussion we were having well before the pandemic hit And so the team has been well positioned to really lean in more into their online component and workload Because we're always talking about scaling scaling scaling But the truth of it is Many of us really miss being on planes Traveling to that next destination to meet developers in person Because honestly nothing replaces this experience of being on the stage Being there seeing all of you speaking with all of you feeling the energy and the vibe of the community this we miss a ton and In thinking about this and reflecting about this new virtualized format I remember this question I had from an open source attendee at a conference I spoke at many years ago and he came to me after my talk and he said Are you relating yet? And I was completely perplexed and I thought Am I relating yet? Oh He's referring to the fact that my title has developer Relations in it And so I asked this question to myself a lot right now Am I relating it are people relating yet because these this virtualized format is so hard to do that And to be honest, there's no silver bullet. There's no magic formula to this right now We're all learning as we go Because really I miss Muppet land that we're in right now This is as close as we're going to get to how do we belong when we are this far apart? And this is as close as we're going to get for some time during this pandemic Some of us are really leaning into our technical skills And using that for good by leaning into the things that are so important to us like saving our oceans And for some they're really leaning in with their technical skills and creating net new solutions in the battle for COVID-19 Such as this employee driven initiative employees across MongoDB Apple alphabet and Amazon got together to build this solution in partnership with Boston Children's Hospital and Harvard Medical Research To build a solution which people could opt in to help with data tracking around COVID incidences across the United States And in the Drupal community the Drupal association is at the heart and core of what keeps the community going and alive and connected And as the Drupal association has a high dependency on in-person events The community really rallied together to keep the Drupal association afloat And we were able to raise enough funding to keep Drupal association alive because of 150 businesses and 2,000 Individual members who contributed to the Drupal association And that's important right now because there are many many organizations who really depend On Drupal who are right now in the front lines of this battle that we have with COVID-19 And when it comes to belonging at MongoDB our premier developer event MongoDB world Is where we really strive to get to and really look forward to meeting with our community and our developers Well, that too had to become virtualized and we had that recently and became MongoDB live We decided in this to really lean into the reality of our experience today And that we used to our to our event and our keynote speakers were all in this zoom like gallery Experience as part of the keynote experience really reflecting what life is like today And we even listed the help of one of our keynote speakers children to help close out the keynote with their own custom made exit note some of the most creative Solutions come from community members such as the dev ops community here Boston actually used his favorite gaming platform to create a virtual trade show booth And it was done in jest But someone else in the community then said well, hey We should actually do that conference that we're going to cancel in animal crossings Well, guess what they did make that happen and One of our own developer advocates Adrian actually presented her full presentation as herself and as in her avatar There were other people in this virtual classroom of hers learning from her in this new virtualized format And to boot of course she had MongoDB swag to share And when I think about gaming and my own experience as a gaming How appropriate gaming really knows how to scale and what a great opportunity to keep the conference going in even in this virtualized format So back to Han Solo being frozen and time and carbonite And I feel this way right now during this pandemic that we're all sort of frozen waiting waiting waiting for things to be normal again but the reality is That that normal we're going into a new normal of things and so we can't keep Being frozen in time like this We can be together while we are this far apart In fact, we are so uniquely positioned to do Really great things in this broken world of ours We have valuable technical skills that we can contribute to really make meaningful impact during this time So whether it's really leaning in with our technical skills to battle This issue of COVID-19 all around us all around the world We're helping with this battle on racial injustices that happen to Black Americans every single day in America Or whether it's to help our open source communities continue to thrive in the face of all of this that we Are experiencing right now because they too are also in their front lines or users are in their front lines Battling COVID-19 or helping with social injustices and writing those things So I ask you to think about if you're done with just learning If you are done with just binge watching all the things And you're done with being exhausted with all those contemplative walks with your furry friends Are you relating to any of this yet? Does this mean something to you? I hope it does Because all of us as humans have a deep desire and need to belong And I know it's hard right now in these virtualized formats, and I know it's hard being socially distanced But really together especially in tech especially with all of us who can code and do things for good You ask yourselves Where is everybody? Where is everybody? We are all still here. Our communities are still here and they still need you to make a difference The world needs you more than ever before So I I ask you find your belonging in your communities again because we're all here And we're all here together Thank you Thank you Grace. What a perfect note to end our morning session on and thank all of you for being here This is the end of our keynote sessions for today. Enjoy the rest of the event today, and I'll see you all back here tomorrow