 Okay. Hello everyone. Thank you for joining and for those who are watching online, good morning, good evening, good afternoon wherever you are. Thank you for tuning in. For those who are attending in person, congratulations, this is the last session of this event. You did it. What a week. I had so much fun. It's so nice to see people in person. I know so many people are working hard behind the scene to make this happen. So I want to thank all of the people who worked for this event, especially Linux Foundation team, production team who is live streaming right now, and speakers. Let's give them applause. My name is Teresa Teresaki and I'm a Program Manager at Google, leading brand experience and events in the open-source programs office. I have been in Google for almost 10 years now and have experienced three different orgs, sales, marketing, and now engineering. Today, I'm going to talk about what we learned supporting open-source during the pandemic. Before we dive in, I would love to share my passion first. I love exploring new restaurants. My Instagram feeds are all about food. My favorite place in San Francisco so far has been flower and water. Their pasta-tasting menu is outstanding. This week, I tried Umi Sake House in downtown Seattle. What's my team? Has anyone here ever been before? No? Yeah. All of them from our team. It's a Japanese spot for sushi, is a kaya style snacks, and sake. I apologize if I made you hungry. Dinner time is almost ready. Umi Sake House is 15 minutes walk away from here if you'd like to try out tonight. Enough about my restaurant recommendation. Let's get back to the main topic. At Google, open-source is at the core of our infrastructure, processes, and culture. As such, participation in these communities is vital to us. Google manages over 9,000 public repos on GitHub and over 1,500 on Git on Borg. We originated open-source projects including Android, Frutter, Chromium, TensorFlow, Kubernetes, Go, Istio, Knative, GRPC, Apache Beam, and more. To support this project was in Google. Chris DiBona, who spoke at Keynote yesterday, founded the open-source programs office in 2004. We have helped Google use and release open-source code as well as support the sustainability of open-source communities. Over the 17 years of history, the past one-and-a-half years may well have been the most challenging time. The pandemic happened worldwide. A short-term price order was issued a close award, and most of us were stuck at home for a long time. Now, let's hear from the audience. How many of you think your productivity improved during the pandemic? Oh, wow, that's impressive. Next, how many of you think your productivity dropped? Okay, yeah, about the same. I feel the same. We found that the open-source projects were heavily impacted as productivity went way down. For example, we saw a 38 percent drop in daily core computers for Kubernetes projects, and other workloads dropped as well. On the other hand, corporations are still planning to increase investment in open-source. According to the open-source program survey conducted in May 2020, more than 1000 people in various sizes of companies said that their organizations are creating more open-source projects than ever before. Demand is high, but developers are struggling. To support those developers, several open-source teams at Google took action. Today, I would like to take you through our journey, what we have been doing and what we have learned. Ten days after pandemic happened, our Go team published a blog post to support their community by sharing job postings, online training resources, a discussion channel, and a help desk. Three months later, our old spot team published a blog post on what we are doing to help the community. During the summer, we shifted our Google-wide internship program to focus on open-source projects, so that 1000 interns could still work from their home with limited corporate access. They contributed to open-source projects as well as COVID-19 response efforts. Three months after work from home started, we asked developers what they were looking for. We learned that virtual events were the most popular channel for developers to stay up-to-date on open-source projects. But we had one problem. Audience momentum was not good. People were fed up with virtual meetings, webinars, being stuck at home. So we needed to change the momentum from virtual fatigue to virtual fun. I know it was good old days. In-person events are so much fun. Let's hear from audience. Is there anyone who would like to share what you missed the most about in-person events? Anyone? Yeah. Free food? Yeah. Yes. That's the best. Yeah. Like spontaneous conversation, meeting new people. Yeah. When we took a community survey, we saw three main themes. The first theme is interaction. Networking is more efficient. Holloway conversations are organic and spontaneous. For some people, all of the team members are remote so events are the only opportunity for them to meet in person. The second theme is experience. You can feel energy and motion and excitement and you can also explore a new country or city. Of course, there is a swag in after-party free food. The third theme is practicality. You can interact with experts and get help on projects. We took this learning and tried to apply these elements to our virtual events. We had to launch something quickly. So we looked inside of Google to find existing resources we could use. We have engineers, a close-up company, who are working on open-source projects. We also have ready-to-use virtual platform, like YouTube Livestream and Google Meet. So we decided to combine these three and create a virtual community hub. This is what we launched in September last year. Please welcome Google Open-Sales Live. Good morning, good afternoon, and good evening. Thank you for joining Apache Beam Day on Google Open-Sales Live. Finally, we'll just make some minor modifications to the code. I'm adding a HelloHandler function. With that, it's time for the after-party. Google Open-Sales Live is a monthly live event series. The developers can get together and learn from open-source experts. Each event includes four sessions and the Q&A. We finish with an after-party or Google Meet so that attendees can connect with the speakers directly and have some fun with other developers. When we launched the community event hub, we wanted to focus on three key values, real-time, interactive, and accessible. Real-time. To liven things up in an engaged audience, there is no going back, no playback function until the event ends. So, this helps create an engaged and focused audience. Interactive. We have a Q&A live wall below the livestream window so that the audience can ask questions during the presentation. Sessions are pretty cool there so that the speakers can focus on answering those questions live. At the end, we conclude the event with an after-party with a DJ, a face-drawing artist, quizzes, and prize giveaway. Finally, accessible. All the sessions are pretty cool. There's four weeks in advance so that we can add human-generated captioning to make them accessible to the D, deaf, hard of hearing, blind, low vision, developmentally disabled, and neurodivergent communities. Captioning is also beneficial for non-native English speakers. We also published guidelines for virtual event accessibility so that other open-source community members can plan an accessible event. Because this event is online, there are no geographical restrictions. Anyone can join from anywhere in the world. We set the event time at 9 a.m. Pacific so that the majority of our EMEA audience and some APAC can join live. If the time doesn't work for them, they can watch the recording later. We recently started to translate the sessions to some local languages, including Spanish, Japanese, and Chinese. We add subtitles and voice-over. And voice-over is done by our internal volunteers, including myself. I'm doing Japanese voice-over if you're ever here. These are some examples of top popular activities. Live pool and world cloud are interactive tools to increase audience engagement. We also invite a face-drawing artist to every event. Lucky winners can receive a digital copy of their drawing. If you want to win the face-drawing, you have to turn your camera on. This will encourage the audience to join in the conversation and create a community vibe. Gamification is a great way to increase audience engagement, too. We conduct quizzes related to each livestream session and give away a prize to quiz winners. During and after the event, we saw lots of attendees sharing their experience on Twitter and Slack channel. We saw positive comments, especially along the event's interactive components. And we learned that the audience loved taking screenshots of themselves next to a speaker on Google Meet. We provide special virtual backgrounds for speakers so that the audience can spot them easily on Google Meet. We received great comments from attendees, quote. The live event was surprisingly great experience today. A couple of hours of curated, insightful, and well-prepared talks. Interesting and helpful format, end quote. We have hosted 12 events over a year with attendees from 107 countries and have achieved a 4.5 out of five satisfaction score, which is quite high for an online event. 57% of attendees were new learners and the rest were either contributors or using it in production. If you are free next Thursday, please join us for the October event, open source productivity day on October 7th at 9 a.m. Pacific time. I will take a moment so that people can take a picture. Thank you. Over the past 12 months, we have been trying out new ideas and keep pivoting. We have learned a lot from this experience and I would like to share our six key learnings. Learning one, your personal life matters. The pandemic impacted developers' personal life. They may not have a private workspace. They may have their children at home. For some people, work is not their priority anymore. So we had to step back and think how we can help them as individuals. One of the actions we took was sending out the care package to our contributors. Each item was carefree curated and sourced from local brands and contained something to help them enjoy their work from home. This year, we wanted to send out something people can enjoy outside. So we curated picnic items. One of the contributors who received the package told us that he was in a low point when he received the package. His wife was suffering from COVID-19. He posted a picture of the care package on Twitter with a comment, quote, this is what I needed today, end quote. Learning two, accommodate everyone. We learned from Matenly's survey that 62% of developers prefer in personal events. However, 38% of them still prefer virtual events. It was good learning for us that we have to find a way to accommodate those who prefer virtual events. More and more events are moving to hybrid model and we have to make our event fully global. You may want to host three events in three different time zones, including Americas, APAC, and EMEA. If an in-person event is happening in Americas, we can livestream the recording in the EMEA and the EPEC time zone with local live contents so that they can also enjoy the live feeling. We may want to create a separate chat room by vision so that virtual attendees can talk to each other during the livestream. If we are distributing swag at an in-person event, we may want to consider shipping to online attendees also. We may want to set up a live cam on site so that online attendees can talk to in-person attendees. We need to compensate for what virtual events are lacking so that online attendees can also get an equivalent benefit. Learning three, sustainability, trouble. Not everyone is willing or able to trouble to attend events in person. Some attendees prefer to trouble domestically but not internationally. Some companies may cut their trouble budget. Creating an attractive hybrid model can also reduce the event's carbon footprint. Swag. When we make a purchase decision, we also try to keep sustainability top of mind. Some swag manufacturers offer a charitable program such as 1% of sales donation to nonprofits to protect the planet. Plastic. We may want to provide a drink bottle as a swag and set up a water station at the event so that we can reduce plastic usage. Learning four, if content is king, brand design is a new queen. For virtual event, user touch points are very limited. We teamed up with a design team and created a cohesive brand experience. Shifting to a design-centric event creates a beautiful and fun audience experience. Learning five, internal community is your power source. This year, we hosted an internal summit for open-source engineers at Google. The whole day virtual event became the place where our engineers could find out about other open-source projects. The audience loved all the connections that came out of the event. People found each other in the chat room. People dropped by virtual office hours to talk to project leads in person. Virtual. After this event, communication volumes inside of our company significantly increased. And we could identify our internal needs as well as close functional collaboration. Learning six, keep evolving. Especially in this new post-pandemic era, the world is changing quickly. So we have to keep improving. Every week, we look into our workflow, audience needs, learning from the previous event, and come up with new ideas and creative solutions. This process enables our programs to accommodate audience needs in the long term. If you are struggling to foster your community, you are not alone. We will get through this together. We have more team members in this room today. Could you raise your hands if you're from Google? Rather, cost of fear. Oh, I thought no, you're from Google. Oh, cool. Great. If you find your faces in the hallway, please stop us. Let's chat. For those who are joining online, send me a message through the event platform. With that, that's a wrap. Thank you so much for having me today. Does anyone have any questions? No? Great. Thank you so much. Enjoy the rest of the night.