 Welcome everyone to the Open Source Strategy Forum 2020. This is our fourth edition and once again I'm very excited to have the opportunity to speak and connect with all of you to talk about the state of open-sorting financial services. For the fourth year in a row this is our fourth edition. We have a record number of attendees from across the globe. I am thankful and very humbled to see the interest around this movement grow by the day, especially if you consider where we started a few years ago. While we wish we were greeting you in person this week and trust me as an Italian I'm feeling this 2020 and the lack of person interaction particularly heavily, we are still very grateful to have you all joining us from virtually around the globe and we have what we think is an amazing event planned for you. I hope you will enjoy and you'll see up there this is just the beginning. This is a recurring theme that you're going to hear throughout the next two days. Again this is a very exciting time for our community and I hope you will enjoy the show. But first of all, let me start thanking all of our sponsors with a special shout out to our leader sponsors, GitLab, IBM and Red Hat, our contributor sponsor, Tidelift and our community sponsor, TradeWeb. This wouldn't be possible without you, so thank you, thank you so much. And to the attendees make sure you connect with our sponsors. We have virtual booths in the event platform and we have our Slack channels. Before we start, let me give you a couple of housekeeping notes. We have several ways for you to engage with our community. We'd love not only for you to engage in the next couple of days but hopefully to remain engaged and contribute to the Phoenix community. So you should have received the Slack invite, finals-left.slap.com. Make sure you engage in QA with the speakers during breakout sessions and we have several rooms where you can engage with our sponsors, with our community and with the speakers. Also don't miss the Ask the Expert sessions again in Slack. Speakers are going to be very, very useful areas where you can ask questions to the experts in our community. And finally, as I said, we'd love you to stay engaged. So a great way to do that is to sign up to our community mailing list and start engaging, discussing with our community. Of course, if you think open source and financial services is great and there should be more of it, but maybe you can contribute directly. A great way for you to participate is to help amplifying our reach by spreading the word on social media. So you can see the O.S. Spencer hashtag which you can use as well as at Phoenix Foundation is our handle both on LinkedIn and Twitter. Finally, before we get started, we want this to be a fun event for everyone. So please make sure that you take a look at the Linux Foundation Code of Conduct and that you abide to that throughout the day. It's linked at the bottom of this slide in case you don't know what it is. And if you see or experience any issue, please do get in touch with anyone of the Phoenix Foundation staff on Slack, on email. We'll be there to support and we appreciate your cooperation. And with that, I would like to invite our first keynote speakers, Dove Katz, our chair from Morgan Stanley, and Kim Prado, our vice chair from RBC. Dove, Kim, take it away. The Finno's governing board includes representatives from the many types of companies that make up the financial service industry. This includes buy side and sell side financial firms, fintech companies, and open source technology and service firms. This diversity is essential in shaping strategy and direction. Representatives from these companies come from both technology and business areas and this is key in shaping views and understanding of different projects with a different value. Some technical projects, for example, include the cloud certification and assurance effort, which ensure that infrastructure that we set up in the cloud has all the appropriate controls applied. Data transformation efforts with Goldman Sachs legend ecosystem and synthetic data management with cities data project are two other examples of tech projects going on within the Foundation. The planning standards to share financial objects between desktop applications, regulatory technology in the Finno's open-reg tech initiative, expressing business logic in a way that can generate coding projects like Morgan Stanley's Morpher are just more examples. Board members perform the dual role of driving interest within their own firms and working closely with the Foundation staff and other board members to identify and share industry challenges that can be addressed by open source solutions with real potential to impact the industry in a great way. The diversity of views and the trust to speak openly with peers, who may also be your competitors, like Joe, for example, is a critical factor in driving the direction of the Foundation. In our last governing board meeting, we took a step further and established a Finno's diversity and inclusion committee. Allie will talk more about this later this morning. Last year when Allie and I were on stage, Gap mentioned that we had reached a chasm. 2020 has been a blockbuster year for Finno's and we've definitely crossed that chasm, validating our several years of hard work and partnership. We finally hit the tipping point where financial institutions make up the majority of coding project contributions. Our relevance in the industry was validated when we joined forces this year with the Linux Foundation and code contributions reached a record high of 1,500 last month. We had about an order of magnitude less last year and this shattered our previous record by 40%. We are really excited to have joined the Linux Foundation as their financial services umbrella. Finno's has always approached accelerating open source and financial services from multiple angles, supporting firms as they establish their policies and procedures around open source contribution, providing a trusted neutral platform from a technical view, as well as a cultural and strategic one, sharing experiences and opportunities, and providing a home for open source projects and standards of that particular relevance to the financial services industry. As Jov mentioned, we're seeing this approach pay off with increased contributions and engagement from banks. Some banks making their first contribution as they find that tipping point that they did last year while others are making their third, fourth and beyond and are becoming more streamlined. Firms are recognizing the benefits of leveraging Finno's projects. Here today I'll be speaking about perspective which was originally contributed by JP Morgan. Others are getting the internal buy-in to take the next steps. This increased visibility is also driving interest. And DevOps SIGs are two examples where we're drawing both wide interest in new participants. New participants in partnerships and collaboration with organizations who recognize Finno's potential to help further a common cause, such as ISDA and AIR collaborations that are on the table, and partnerships emerging at home within the Linux Foundation where there is now a more devoted focus on the financial services industry. Open source and financial services is a reality because it's good for individuals and it's good for companies. It's good for business. We're pleased to be involved with Finno's end-miss conference and hope it gives you some idea of what open source and financial services can do as well as some of the exciting things that are happening within the foundation. If you're not already involved in a Finno's project then please do ask us or any of the Finno's team or check online about how you can be. Well thank you Kim and thank you though for sharing your experience and perspective on the growth of our community. And you know most importantly thank you for the support, the advice and the leadership in changing the status quo in this industry. It wouldn't have been possible without you. So today before I leave the stage to much smarter folks than I am, I wanted to give you all an update on our community and more broadly the state of open source and financial services. And spoiler alert, the state of our community is as strong as it's ever been. We've seen a regular amount of contributions this year and I'm glad to report that the vast majority of these contributions are coming from financial institutions. And completely unheard of even a little over two years ago when we started Finno's. This is an important milestone for us but before we look ahead at the opportunities that we think this opens up for the industry, let's take a quick trip down memory lane. In fact, we started Finno's two years ago or even further when we started the Symphonies Software Foundation four years ago as I pitched the idea of open source collaboration in the industry, a highly siloed and regulated industry. Let's just say that the reaction was less than lukewarm. And that's understandable. It's an industry that not only has to abide to strict regulations but that it culturally can be very competitive, not just across firms but also within firms. Not only there were several myths about open source that needed to be debunked but there were concrete legal, technical and strategic reasons to prevent even internal collaboration models like for example inner source, let alone open source collaboration across firms. So that's when we started our open source readiness initiative which paired, you know, if you pair that with the changing nature of this industry and the forces that will touch upon a little later, that has delivered major progress in how financial services can now collaborate through open source. And since we started, we've seen an amazing progressions. I mean, just take a look. When we started in 2016, we were focused on collaborating on a single platform, Symphonie. The platform was originally born out of an investment out of the largest financial institutions, pretty much all the bulge bracket banks out there. And based on a contribution from Goldman Sachs, their internal collaboration platform called Live Current. And the idea behind that was that an open source foundation could be the neutral place to build an ecosystem on Symphonie and that inherent transparency of open source would increase adoption and acceptance by other financial institutions, Vintex and regulators. So you see, even four years ago, there was a spark of this idea of open source collaboration. But then it was 2017 when our platinum member Deutsche Bank contributed to Lexus, a battle-tested messaging bus used in the Autobahn single-dealer platform that effectively that was the spark that made us realize that maybe, you know, just maybe, we could leverage the trust and the network that we had built in our community to collaborate not just on Symphonie, but to leverage open source to address really long-standing technology challenges and collaboration challenges across the industry. And that's when we hosted our inaugural OSSF and there we heard loud and clear the message from the industry over 400 folks validating this idea and pushing us to, you know, expand the remit. And so that's when we launched FinNOS in 2018. The Symphonie Software Foundation became FinNOS. We had the amazing representation from other financial institutions, from technology firms. And we also started seeing, you know, quickly the power of this collaboration model in, for example, standards like FDC3, our interoperability standard, moving quickly to deliver releases. This was a really early sign that we were, you know, on the right track. But then 2019 was really pivotal for us. We received what, you know, to date is still our most starved project on GitHub, you know, perspective. This was a real-time visualization library contributed by JP Morgan. And we continue to bring, you know, the industry along with our open source readiness program. And we culminated the year with the largest OSSF to date last year. You know, everyone I spoke with felt a unique energy last year of a community being born. Very much looking forward to what we could do together. Well, and then 2020 stroke. You know, the silver lining is this has actually massively accelerated, you know, if you think how much now firms are comfortable with remote and distributed teams, very much, you know, the open source default mode of operation, this has really resulted in strong membership growth. Our project portfolio has grown drastically this year in 2020 with contributions from, you know, Goldman Sachs, Citi, JP Morgan, Morgan Stanley, Nomura, pretty much all of our platinum members and financial institutions are now actively engaged in contributions. And let's not forget, we joined the Linux Foundation. This has been an amazing year for us as we partner with the bigger family, the larger family of the Linux Foundation, which is also, by the way, helping us produce this event today. This has been an amazing partnership and we look forward to what this can bring to the industry and beyond over the next years. Before we talk about our projects and, you know, the major progress we've done this year, I want to send a shout out to our members. You know, today we are 38 members strong and, you know, all of this wouldn't have been possible without you, without your support, without your funding, without the sweat equity you put every single day to grow this community. And so every time I look at this slide, I am incredibly proud of having such a corporate representation spanning from, you know, financial institutions to Pintx, from technology companies to other consortium nonprofits we're now partnering with. A representation that keeps growing in diversity as we look to engage very much every constituent of this ecosystem. On this note, I am very proud to announce today the addition of three new corporate members to our family. Today we're welcoming Susie and Intel as gold members. I'm very excited to have such open source leaders joining our foundation and very much look forward to working with them. We're also announcing Div Blue is joining us as a silver member out of the UK, once again showing the true global nature of our community. And finally, please join in welcoming these corporate members to our community. Make sure you connect them today, today through the different collaboration channels that we have available at this conference. But that's not all. Today Phoenix is also announcing the creation of the Free of Charge associate membership program. It's targeted for nonprofits, industry consortia, governmental and academic institutions. And we're actually welcoming our inaugural three associate members to Phoenix. I'm very proud to announce that Air, the Alliance for Innovative Regulation, is partnering us to involve regulators in our open source endeavors. And you're going to hear about it much more tomorrow from our COO, Tosha Allison and the air team. We're also welcoming today the inter-work alliance to our community, excuse me, inter-work alliance to ensure that our standardization efforts can span across the world of decentralized technologies. Finally, last but not least, we also formalize our associate membership with ISDA, the International Swaps and Derivatives Association, with whom we already partnered throughout 2020 on the legend pilots, formally known as Alloy, to make changes to their common domain model and successfully hosted collaboration on this powerful modeling platform. So what's the common thread here? Phoenix and the experience we built is now recognized as a enabler for other institutions, for other nonprofits and consortia in the industry that are maybe less familiar with open source. And we think we can help accelerate their progress. You know, we're here to help to consolidate, not to fragment. Now, I just mentioned legend. And so if you haven't followed the news lately, let me give you a quick reminder. And again, spoiler alert, this was a huge deal for us at Phoenix, for our community and for the industry at large. If you were here last year, you remember that Goldman Sachs announced the intent to open source their Alloy modeling platform and the underpinning language called Pure. So I'm really happy to report that this process of open sourcing completed in October with the contribution of the platform, which is now referred to as legend. This is a huge step for Goldman, for our community, for the industry at large. Not only we expect, you know, other financial institutions to start adopting the platform that Goldman uses for all sort of modeling from regulatory pricing. But we have seen a great potential in Phoenix actually hosting a legend instance, which has been already used by over 100 modelers to collaborate on common pan industry standardization efforts. So check it out, download it, contribute to it. And if you'd like to try it, we are hosting our legend sandbox. So go to Phoenix.org slash legend and we can get you set up. But it's not just about legend. You know, as I mentioned over the last two years, our project portfolio has grown to include so many high value and high quality projects for this industry. After all, financial institutions, you know, should be no surprise, financial institutions have massive technology organizations. And amazing software components that when contributed can deliver immediate value to the industry. So we talked about legend from Goldman Sachs. We touched on the perspective visualization library originally contributed by G.A.T. Morgan. But while I won't be able to discuss here the over 40 projects in our landscape, there's a couple of projects I wanted to highlight to showcase the depth and the breadth of our community. WOLF, for example, was contributed this year by Deutsche Bank. It's a very mature, active project that allows you to visualize and define your organization technology landscape. When you think about the sheer size of these financial institutions, well, you can easily see how this project has a massive potential to be used across the industry. I also wanted to send out a shout out to the Morpher team, a project that was contributed earlier this year by Morgan Stanley. This project aims to represent your domain model and your business logic in a technology agnostic fashion. And we can see great potential here for standardizing some of the common challenges required across the industry. For example, in Heria where we're seeing very high potential is the regulatory angle where Morpher could be used to define common regulatory implementations. Last but not least, just a shout out. We quickly talked about our FDC3 standard, which stands for financial desktop collaboration and connectivity consortium. This is probably the most mature standard we have in Phoenix. In case you didn't know, yes, we do also open standards, not just open source projects. This standard has reached its 1.1 version, it's very mature, and it's being increasingly implemented by both vendors and financial institutions developing applications internally to harmonize the ecosystem of these applications, not only on the front office, on the traders desktop, but also in the mid office and back office. So it's a very powerful standard and we think it's going to help bring together a previously largely disconnected ecosystem of applications. And make sure, again, I couldn't cover all the 40 projects here, but make sure you check out the landscape, the over 40 projects in the Phoenix landscape at landscape.phenos.org. If you're engaged in other Linux Foundation projects, you probably are familiar with the landscape. So please check it out and we're hopefully going to see you contributing to some of these projects. So given the growth that we had this year, it should be no surprise that in October 2020, in October 2020 has marked the all-time high in number of commits to the Phoenix community. Not only that, but in 2020 over 70% of our projects contributed, came from financial institutions. I'll stop a second to let that one sink in. I mean, this is an industry that has historically struggled to collaborate and we think this is an amazing achievement. But as much as I'd love to credit the Phoenix community and our team for the relentless work done with our open source readiness initiative, and trust me, that has massively helped several of our members to get through the hump and start contributing. The truth is the industry is leaving a seismic shift and the context we're moving in in 2020 makes open source in this industry not only strategic, but almost a foregone conclusion. So let's have a look at some of these forces. Why is this industry now seemingly suddenly embracing open source contribution and collaboration? Well, first and foremost, the business context we're moving in has drastically changed over the last 10 years. Not only the advent of electronic training and just generally very highly competitive market has driven spreads and margins to their historical loads impacting the top line. But if you look at the bottom line, the regulatory span has steadily increased over the last 10 years. So there simply is no longer a cozy, infinite amount of money to be thrown at the problem. And if you pair that with a mandate to become technology companies and more generally to deliver customer centric solution for the digitally native new generation, well, then you can see that the business imperatives points to a much stronger need for efficiency and a tech native approach. On the other side of the equation, the technology landscape has drastically evolved over the last 10 years and presenting really new opportunities cloud, first and foremost, which by the way itself, I believe wouldn't exist without open source and the advent of the centralized technologies which are in a way threatening the very notion of these large centralized financial institutions. And if you add to that equation, the increased talent crunch the industry is experiencing for both older technologies like mainframe and most importantly for new technologies, you realize why the industry is looking very seriously now to tap it into the ocean of talent that exists in open source communities. If you pair that, those business and technology drivers with the tensions of an ecosystem, a landscape that is still largely divided between the up and coming fintechs on one hand who really target to deliver drastically new user experience as their differentiator. And on the other hand, incumbent vendors still having a dominant position in the market and continue to leverage in that. Again, if you pair that with the growing number of new generation technologies who are called in senior and executive positions in banks, coming with a strong open source experience, grown in years of delivering technology quote unquote on the West Coast, then you realize that really open source is here to stay. But make no mistake, this is just the beginning. I want to draw a parallel, of course, as an Italian to a love relationship. I think that where we are now is being happily married after years of dating in a way through large consumption of open source but limited contribution. And so what now? Well, like any marriage, now the goal is to nurture this relationship. It's not going to be easy. Each side will have to give something up, but the reward will be able to collaborate, to create solutions for some of the long-standing challenges in this industry. This is the imperative. This is just the beginning and it behooves on us as a community to leverage this amazing community that we've built and go after higher-order challenges. So that brings me to the road ahead. I think first of all, as I said, we have an opportunity to seize. And by far, I don't expect this to us to only make an impact in financial services. It's no longer a mirage to think that with this community that we have and the representation from the largest financial institutions in the world, we can make an impact beyond our business problems into areas like sustainability, financial inclusion, diversity, which continue to be massive problems. In order to do that, we need to build a commercial ecosystem around the open-source projects that we have. And we think there is a huge first-mover advantage there for FinTechs that are going to jump in and repeat what we have seen happening in pretty much any other industry, commercializing open-source. But in order to do that, we need to continue nurturing our projects in the open. As you all well know, it doesn't just take to throw code in GitHub to make a project successful. And so it is our imperative to work together with our contributors to make our projects wildly adopted and contributed to. And the way we're going to do that is to really embrace all constituents in our community. We are a global and inclusive community. And as you hear a lot tomorrow, we're doing a lot of work to include the regulators, to include the global financial institutions, all the other industry consortia as you've heard today. So so much work ahead, but we see a major opportunity here. And finally, I want to close with this. Open source in financial services is a positive sum game. Let's be clear. Nobody will have the time, the attention, the resources, or the goodwill to just do open source for the public and see it through. But the good news is that there are massive opportunities, commercial opportunities, for each individual constituent, whether you're a bank, a fintech, a big tech or cloud service provider, or even a regulator. Because as you go after those opportunities, the open source way enables all of us together to create faster innovation, better interoperability, data standardization, a truly open fintech ecosystem, and definitely mitigate the risk market-wide. I think these are all very worthy goals, we think. And so we do hope you'll enjoy the next two days. And after that, you'll join our community and contribute to our projects. Thank you so much for listening. And I hope you do enjoy this conference. Now, let me move, as I said, to much smarter folks than me. Our next speaker this morning is managing director at Goldman Sachs and lead architect of the recently open source project Legend. It's Pierre de Belen. In addition, he co-manages Goldman's data platform team, which is responsible for developing data-centric and user-focused solution to power the firm's data strategy. Today, he joins us to share details about open sourcing legend, the flagship of Goldman Sachs data strategy, and maybe now yours. Please welcome Pierre de Belen. Hello. My name is Pierre de Belen and I manage the data model engineering department at Goldman Sachs. We just completed the first phase of open sourcing the legend platform by contributing its code to the Phinos Foundation. I'd like to thank the whole Phinos team for their help and their support throughout this journey. Today, I'm going to give a high-level overview of our platform and describe several of its use cases. Some can be implemented with the code currently available on our GitLab projects, while others may require code that will be available in upcoming contributions. As you may know, the problem of data management in finance are less related to the volume of data processing than they are related to the fragmentation of our data and the incredible amount of actors participating in the finance processing flow, creating communication issues, processing breaks, and other inefficiencies. Legend is a data management platform that provides solutions to these problems by focusing on data discovery, helping technical and non-technical users to find data, data transformation, linking information together, and building a leverageable lineage graph. Data quality, improving quality checks all along the processing pipelines, and data delivery, making it possible for all actors to easily and safely acquire data. However, it is sometimes better to define something but what it is not that by what it is. In this respect, Legend is not a data analytics platform. It does integrate with existing analytics environment like Python and R, and also business intelligence tools like Tableau and ClickView. It is meant to help users organize and transform their data so that it can be easily and safely delivered to these platforms. What does safely means? It means that users will have more confidence that the data they are retrieving is what they expected. This is thanks to the transparent lineage, that the quality is appropriate. This is thanks to the centralized and collaborative definition of constraints, and first as early as possible in the transformation flow, that users only see what they are authorized to see, respecting data sensitivity and privacy. All these functions are made possible by effectively managing metadata. We ensure that the metadata is always up to date and accurate because it's driving the execution flows. So let's look at the tools that constitute the platform. The platform relies on two servers, the SDLC server and the Engine server. Both of them can be seen at the bottom of the diagram. Let's look at them in more detail. First, the SDLC server. It currently provides a driver to the GitLab product which manages the lifecycle of our metadata. SDLC is key to our platform as most of our metadata ends up being leveraged in production flow. Having the proper level of audit and review is critical to operating our environments and also to meet the requirements of our auditors and regulators. The platform also relies on the Engine server that provides functions like grammar parsing. It converts the pure language into an abstract syntax tree that are returned as JSON structure. The pure language is a legend molding language. It is used to describe structural models but it is also describing queries, constraints, checkup transforms within the mapping DSLs and data derivations. The Engine also provides a compilation API that provides feedback about errors that could have been made during code writing. Another important Engine feature is also to provide query execution, leveraging three important inputs. First, a function representing the query, then a mapping that maps types expressed in the query to elements of a data source and finally a runtime that provides a way to connect to a data source. We will cover this use case in a little bit more details later in the presentation. Finally, the Engine provides APIs for model transformation. Example would be generating from a model a JSON schema or Java code. JSON schemas can be leveraged to validate serialization or to define contracts in data servicing since using swagger or open API for example. The two servers enable several client applications that help users during their journey working with data. First, a Cuban variant that provides simple relational like queries with operations such as filter, join, or compile. It is mainly used to investigate new data that we could acquire from vendors or by looking at legacy databases. When investigations are done and users decide to invest in their data then they graduate to Studio. Studio allows them to build models that document the semantic of the data and mapping that binds modeled information to data source. This provides APIs that can be leveraged by a large number of users and that can be maintained for a long time period. Once the models and mappings to data sources are created in Studio users can leverage the query tool to easily access data. They don't have to remember any localized knowledge required to join a trade to a product that they would have using Kube. They can also write any graph query they can imagine without being blocked by a static service layer. And finally, if users want to leverage their query programmatically they can publish it to the service tool. It calculates the necessary query plans and enables self-service operational support. Now that you are familiar with the legend and its components, let's go over some use cases. Let's start with the derivatives use case. It was one of the main motivations behind the open sourcing of our platform. The derivative flow is complex because derivative contracts evolve frequently, have deeply complex tangled structures, are processed by many different parties within each firm and also outside each firm. Which means that derivative contracts are leveraging different schemas and thus require transformations. They are built with different technologies as many of these processing steps were built at different times and also require different query engine capabilities. They require many validations to encode all the knowledge and requirements of all actors. To illustrate these facts and looking at the diagram booking and quote require simple data entry schemas. These schemas need to be available for service technologies so that, for example, they can be easily externally available to clients. Thus, the model needs to be transformed to API language like Swagger or OpenAPI. Price and risk need to interface with calculators that may require deeper integration than services in order to perform calculation optimization. Clearing will require interfacing with external standards like FPML or CDM. Read reporting schemas are optimized to report information across assets and thus are represented in a really different way than the original contract structure. How does Legend improve these flows? First, by letting users express models that can be converted to different technologies in a central environment. By defining mappings between the different models. By letting any users define constraints that can be enforced anywhere in the flow. For example, backoffice can define constraints enforced at booking time. And by finally operating all these models and transforms in a strong SDLC to optimize communication among the different teams and to accelerate the potential modifications and improvements of financial terms. The current open source code can operate this use case. However, as I'm speaking, we still have to contribute transformations like pure ToroZeta or pure to JSON schema and also the integration with the GuildLab build pipeline so that the creation of artifacts and the execution of tests can be done automatically. Both will come shortly in the next weeks. Another use case heavily used in our environment is a self-service data access use case. Once a model and a mapping to a data source have been defined in the studio, users can leverage the query tool to easily access information. People often ask me, why is it easier to formulate a query using models than it is using the data source directly? First, data sources have many different query languages. It may be harder to train all your users to know them all, especially business users, than may not have the time or the interest to do so. Second, the model provides safeguards during query creation and makes data access simple. It also helps users not to waste time on things that are not necessary during query creation. For example, how to technically navigate from a position to an account, especially if they are stored in different systems, or the navigation requires a complex join expression. Let me illustrate that with an example. Let's look at product and signals. It looks like a pretty simple example that is an important building block in the finance data space. Let's look at their database representation. Focusing on information that defines their relationship. A product will have many synonyms, and that's why the synonym table contains a product IDI key. As we can already see, the information is encoded in a technical way and can already frighten non-technical users. This is usually because databases use historical convention, mostly understood and managed by DBAs. Let's go through the process of modeling the tables to remove ambiguity about data access. So the first thing to do is to create the concepts we are interested in, so we can create product and synonyms. We can already see that the properties are clearer to users. We represent the relationship between product and synonyms as a property named synonyms. This is already interesting as joining two tables is never as simple as joining a primary key to a foreign key. There's always something else to think about. So we provide these models to users and we let them query. The first feedback that they want to easily and quickly get one specific synonym using the model. So we can modify the model and add a qualifier. It makes it clear that you can get one synonym out of the related synonyms set given a synonym type. So the models start to carry more information than the initial tables. So we give it to our users and they come back saying that the model is broken and that they had multiple products come in when they filter products for a specific synonym. This is because not all synonyms are global. They do have different scopes. Some are valid for a market, some for a region and some are global. So we improve the model. I illustrate only for global and market synonyms but the same principle scales for different scopes. Now users are protected by the API and understand that in order to access a market synonym without any ambiguity, they will also need to provide a financial market. The model comes with far more depth and documentation than just the raw tables and is more suited to ease self-service and is as built-in answers to usual questions. Now that we have a model, users can easily access information by walking the graph and define a tree that univocally qualifies the market. Univocally qualified the information. We can see that something called simply price in a grid can be fully qualified as the stop price of the last-order version, for example, which avoids these communications and error. This is exactly what the query tool enables users to do. This use case requires the model to database mapping capability that will be available by Q1 2021 and the query tool that will be made available by Q4 2021. Thank you so much for your attention. If you want more information, you can find some on our microsite at legend.finals.org and please don't hesitate to check out our call on our GitHub repositories. Well, thank you Pierre for the very cool presentation and the amazing overview of Legends. And since I'm here, I want to thank you and the whole Goldman team for the passion to get this platform contributed. I know it's been hard work, but it's also been an amazing experience for our team to work with you. And one thing I want to point out for the community and it's probably very worth pointing out is that Goldman Sachs is now effectively developing Legend in an open-first fashion. That means that development happens in the canonical source in the open, in our Finals GitHub organization. This is a key element of an open-source project which is aiming to engage effectively its community. So please, everyone, make sure you check out legend.finals.org and if you'd like to try the platform, go to finals.org slash legend. We're hosting a Sandbox instance. Moving on, our next speaker is an enterprise DevOps evangelist and a product marketing leader at GitLab. He is a multi-faceted IT software leader with 20 years of IT leadership and software experience. Today, John will talk about how innovation plus security equals customer joy. And how you can stop sacrificing customer experience for security. Please welcome John Jeremiah. Good morning, everyone. I'm so excited to be here for this year's open-source strategy forum. I'd like to spend a few minutes this morning and talk about how innovation and security together can help you deliver customer joy. My name is John Jeremiah and I'm an IT leader and a developer and I currently work at GitLab as part of the product marketing team. And I'm really hopeful that we can share some insight about things we've learned at GitLab and things that will help you. So I'd like to start by talking about what is customer experience anyway? First off, it's important, I think, to realize that a great customer experience is really not a destination. Rather, it's a journey because the customer's expectations they continuously change as does your organization. So you have to really get to know your customers and their needs and you have to really double click into understanding what really matters to them and then measure that. Now knowing what they want is really the first step. But what the hard work really is in the transformation that you have to do of getting your business to align to meet their expectations. So it requires the business, the IT, the technology side, the product side, all of the organization has to align to deliver an exceptional customer experience. And then the last part of this really is it's about improving and iterating because as soon as you've implemented the changes, customers' expectations, they too will probably change. So you have to be prepared to always improve and to get better. But what do customers really want? I mean, I think it's important to realize that many organizations, there's a huge gap between what customers expect and what they really get. According to Gardner, research is almost two-thirds of organizations are focusing on competing on a better customer experience. By the way, that's doubled from just 10 years ago when it was about a third. But that means that if you're not focusing on how to deliver an exceptional customer experience, you probably should be. You know, in many ways, your customers are looking for an opportunity to experience that delivers joy. They want suggestions and ideas to help them be more productive. They want a personalized experience. At the end of the day, they want something more than what all too often they're not getting because, you know, if you think about what they really get and what you really experience, it's there's a gap. I mean, think about last time you had a robo call where there was a voice response system on the other end. Frustrated. Or when an app or a system was updated and changed and now it doesn't address your needs it made things harder. You know, these kind of experiences they all add up one after the other. And they have a lassy impact either strengthening the relationship with your customers between customers and the brands or weakening. And it doesn't have to be negative. In fact, you all have the power to change it in improvements. So I want to talk about what I think are three things to consider as you look at how do you improve your customer experience. And first off, it's velocity. You have to be able to move as quickly as the market in order to keep up both with your customers' expectations and whatever else the competition is doing. Second is you have to address the reality that trust and security and privacy really are permanent. They're table stakes in building and strengthening a relationship between your brand and your customers. And lastly, the ability to innovate to deliver new value that surprises and delights your customers is really how you're going to be able to differentiate yourself from the competition. So I'd like to unpack it and double click into it because I think it's important to understand that velocity, for example, isn't just about going fast, but it's not going fast with purpose and with controls and intention. And at GitLab where we're part of this amazing open source community building, you know, GitLab the product, we've been practicing high velocity from the very beginning. You know, we deploy over 3,000 times a day to GitLab.com and as a product, we've delivered over 100 consecutive monthly releases where we've almost always include hundreds of changes and updates and contributions from our community. See velocity is what's helping us to deliver amazing customer experience for our customers and I want to share with you some keys as to how do we go as fast as we go. First off is we practice what I would consider to be radical transparency. We work with our community our customers and with each other in ways that are open and transparent. By being open, we're able to collaborate on our roadmap and our strategy. We're able to collaborate on new ideas and features and together we build a better solution and because we're open the transparency it builds trust. The second thing we're doing which is I think also you know radical and extreme is a form of iteration. We've embraced the concept of what we call minimum viable change. We're it's way beyond the idea of a minimum viable product but rather it's a minimum viable change of what's the smallest change that will make something better will improve it. Now in practice minimum viable change is incredibly hard to do but when you've mastered it you're able to implement small changes get feedback and keep moving rather than what typically happens in organizations where ideas get stuck. They get stuck in review they get stuck in the process and they never ever see the light of day. At GitLab we move really fast because of minimum viable change. Now if you're going to move fast you've got to have the ability to eliminate the bottlenecks and barriers and automation I think is absolutely one of the most important things to embrace. In GitLab we embrace pipelines for continuous integration continuous delivery to to remove the bottlenecks and to streamline the flow of innovation to production. That's how we build in quality and reduce risk across the whole journey so that way we're testing everything an exceptionally large number of times including security testing and security scans and all sorts of steps in the pipeline to speed things up and lower risk. The last thing I think that's really really important to make sure that is clear is that at GitLab we don't build things and do things in a static way but rather you have to embrace the spirit of continuous improvement or in my Lean Six Sigma days the idea of kaizen of continuous improvement. We practice continuous improvement in everything we do and in fact when we do uncover and learn new things and share that we publish it. We publish in our handbook for everyone else in the community to be aware of and we publish it in the form of videos and other interactions where we're always being selfish. We're always thinking about how do we make this better over time and those lessons learned then is what we build upon to go faster. Now you know it's it's one thing to talk about velocity but you can't go fast and and do it at the risk of security at the risk of quality and so you have to deliver value fast and to do this you've got to promote and embrace security at all levels of the organization across the whole life cycle. You have to think about the security of your data the security of your applications the security of your infrastructure and from an application perspective you need to ensure the security is baked in from the very beginning as a requirements to giving developers immediate feedback and in the world of DevOps we would call this that you know shift left security. The idea is that you don't want developers and people to wait for security at the very end which has been the way security has traditionally been delivered but rather you want to have security baked in up front so developers get fast and immediate feedback about what they're delivering. You also want to embrace automation to help streamline compliance so that way your applications are shipped in a way that's compliant and ready so that way you're not running the risk of jeopardizing the privacy of your customers information or risking their trust. Now at the end of the day the ultimate goal is really to deliver innovation and joy you're trying to deliver capabilities that surprise and delight your customers. You know think about the last time when a brand did that and delivered something that surprised you. You know for example as a former frequent flyer I used to travel a lot I would like to get back doing it but it was an amazing experience the first time when an employee came up to me and recognized me by name out of the thousands of pastures they deal with and they had the data and it was a way of a great personal touch and it strengthened my loyalty. So you have to really understand your customers and what they expect and deliver that for them. You know in many ways what we're really trying to do is achieve an amazing experience for our customers an experience where we are where we're fast and delivering value that's safe and exciting in a way that strengthens that relationship and you can do this thing you can do this. You know I've been in the position at GitLab where we have succeeded in doing this with our customers. When I would go to conferences and events you know in the real world when we used to go to physical events it was so common to have members of our community and customers come up to the booth and they would want to hug us and I don't mean in a socially distant smile or a wave or a nod but really hug us because they were so fond of everything that we did to help them deliver and if we can do it so can you. The relationship you're building with your customers will deliver delight and innovation and value from them and you're going to have a relationship with your customers that will stand the test of time. At GitLab we've been doing this we've been building a solution if you don't know what GitLab is we're an application that helps software developers and teams build and deliver software we cover the whole life cycle in a single solution and it helps people to deliver at high speed without sacrificing security it's all about how you deliver innovation faster than ever but this isn't about really GitLab this is about you and how you can do the change to improve your customers experience I'd love to connect with you all of you or any of you in the future on LinkedIn have a wonderful conference and thank you so much for the time. Well thank you John for your insights and I mean thank you also GitLab for being such a valuable gold member of FINNUS and having been so functional in supporting us in open sourcing legend. Next on Joining us is Alejandra Villagra she's managing director in the markets and securities services division of Citi she's also the head of Citi Velocity Citi number one's ranked digital platform for institutional clients Ali has been an invaluable leader of FINNUS representing Citi on our board since its very inception and then in our tenure first as a vice chair and then chair of our board not only that but Ali has been a huge advocate of our movement in our firm which is now actively contributing more broadly for open source in this industry. Earlier this year Ali has also stepped up to chair our diversity and inclusion committee who's working to advise FINNUS on concrete actions we can take to grow diversity in our team our board and our community this is a fundamental area where concrete action is needed now as diversity remains a huge issue both in financial services and in the open source community so Ali joins us today to talk about building an inclusive community by sharing our own personal experience please join me in welcoming Ali Villagra Hi everyone it is such a pleasure to be here with you all today albeit over Zoom not not as good as in person but a pleasure nonetheless I'm absolutely delighted and honored to be here to speak with you a bit about FINNUS diversity and inclusion efforts and a little bit of my own experience in the space as well so with that I'll get to it the first time I stepped onto city's trading floor I was completely awestruck excited and beyond intimidated I studied social sciences at Dartmouth to be honest I did not know what a stock or a bond was I did corporate recruiting because it seemed my 21 year old self lazy not to and since my friends were then low and behold I'm in New York City at a final round interview talking about a world I barely knew even existed there's a lot that is fuzzy about that day but three things stood out number one the trading floor it was intense number two an extremely kind extremely kind administrative assistant named Ellen who must have read the terror on my face because she complimented the new bag that I bought from a big day and number three my interview with a very confident very warm and very pregnant Sunni Harper almost on the spot I knew that I was meeting a new North Star that day Sunni took an incredibly important place in my heart and in my brain because I wanted to be just like her she had important clients she was the boss of a big team and yeah apparently she was about to be a mom too and there was her name Sunni what was it I didn't know I didn't ask I just knew that on some level it was like my name it was different but here she was so preparing for this talk and in fact right now made me really really nervous I knew from the moment that I said yes I was going to stress about it until it was over I also knew that I absolutely needed to say yes to be visible in the way I'm asking my colleagues at FENOS at Citi and in the broader open source community to make efforts to see that underrepresented people are visible so here I am after stressing about saying yes I quickly moved on to stressing about what I could possibly say to you all over zoom in a pandemic and in a moment of reckoning with racial injustice everything I could think to say just seemed really unimportant on a relative basis so finally I settled in on what I know best my own story my tiny tiny sliver of an experience that might personalize for you all why representation matters how it happens how it shaped my career and brought me to you today since that day when I first met Sunni on the trading floor I've had a lot of ups and downs in my career like everyone I've had moments of pride I've had moments of disappointment I've had times when I was short I would not make it in the world of finance and moments when I knew this was exactly the right place for me but this talk is about representation and why it matters through my eyes and the story I'm telling is about how important it's been to me each step of the way to see a person I aspire to be it is proof hard data evidence that it can be done the list of reasons my career has been successful is full of intentional interventions it's full of luck setbacks successes and my own stubborn competitive nature and while Sunni and other senior women have been my North stars I have benefited enormously from men who've been fierce advocates and mentors who've taken chances on me and put their faith into my abilities I've also worked with incredible teams women men black East Asian Indian white straight gay colleagues who have poured their talents into our shared goals and more importantly who believed in me as a leader they believed in me as a leader and in doing so created a self-fulfilling promise representation takes a village it takes effort from everyone the role models who prove it's possible the leaders and the managers who set the stage and the colleagues who embrace it but those of you listening who are in the minority I see you I am rooting for you you can do this for those of you empowered to change the numbers identify the underrepresented talent in your organizations and give them an opportunity to lead for those of you who work for black for Latino colleagues for women for anyone in the minority in your world embrace and accept them you have more power than you know to help them succeed I'm here speaking to you today because Finos has made diversity an inclusion of priority Gap the Finos leadership team and my colleagues on the board entrusted me with responsibility to serve as vice chairman then chairman of the board during an exciting but really challenging time for our organization but beyond this one example we are working to define our diversity and inclusion strategy by setting representation goals for ourselves for our board of directors and we'll be reaching out to you our open source community to help us grow the number of underrepresented people in our ranks if even one person reaches out on the back of today that will be progress so bear with me through one more story just one more later in my career to drive home the point in November of last year having recently taken over is the head of velocity at city I was asked to present my strategy for the platform to the heads of the trading division and their management team 20 minutes or so before I was due to speak I was invited into the room there were about 40 people in there and a lot of jackets sort of slung over the backs of chairs the room was almost entirely men my heart rate absolutely went through the roof I felt really really intimidated and nervous and that's not something I typically feel among the senior people in the room was Deidre Dunn the recently promoted co-head of our global rates business I was close to Deidre and sent her an email from my phone saying I am really nervous I was sitting in a chair by myself kind of off to the side away from the conference table she replied right away saying she totally understood how intimidating the room felt and she reminded me that I know a lot more about what I was presenting than anyone else in the room and that I was here to teach everybody something and she kind of nudged me and she said you should take a seat at the table you should take a seat at the table she said so my heart pounded and I pulled up my chair and I found a little spot at the tightly packed table thank you Ali thank you so much for this inspiring presentation not only I cherish being able to work with you but the empathy and the passion that you provide has been invaluable so thank you so much diversity is such an important topic for us moving forward our next speaker Alessandro Petroni from our Gold member Red Hat and a fellow Italian he leads the business and technology strategy to accelerate the adoption of Red Hat open source technologies in the financial services and fintech industry additionally he leads Red Hat in assisting banks and other financial firms to go in the go-to-cloud journey today you'll be talking about how quickly you can deliver modern banking products and services with modularity in the enterprise open source way please welcome Alessandro Petroni from Red Hat good day we are here to discuss how can we modernize banks using a modular approach in the open source way my name is Alessandro Petroni and I lead the strategy for financial services at Red Hat I'd like to introduce this topic to you and also an experience that we had at Red Hat and other partners in the banking industry how to tackle this quite difficult problem so while we are approaching this concept of modernization if we take an x-ray of the application portfolio in a bank it's quite complex we have probably in the range of 10,000 type of different application highly interconnected with spaghetti integration 100,000 plus databases where data are difficult to be fetched and reused across the firm and also the granularity how these interfaces between applications being developed over the years is not consistent and is not granular at the same level does the banking industry has been working for the past decade to formulate the business framework from a functional perspective of business capability of the part of the bank coming out with the blueprint which define modules that can be eventually reused recomposed to create business applications but why are we talking about modules? we've been using modules since ever in the industry even though we've been using in different form and shapes why? because we didn't adhere to one framework or business framework technology framework or together that's the opportunity here to work collaboratively to work at the parts and also the assembly of the solution in order to better provide services to the associate in the bank and also of course the customers the modules are essentially common languages to define boundaries of roles and responsibilities and liabilities operationally speaking and then are also a particular type of definition how to access such capability in form of for example of open APIs and furthermore in a more modern architecture of open eventing where information flows from inside the bank to outside the bank from the customer that are behaving and engaging with the bank and other constituencies and also inside to detect patterns so the integration comes in much more loosely coupled way and eventually all the business functions are somehow listening to what is happening and they can react to re-engage further for example the customer and the certification and the quality of such componentry and the specification are important to create this kind of modular solutioning without the ecosystem participation of course is not possible because the part become just basically produced by one and only one producer maybe the bank itself which doesn't scale we have been using services in banking for quite a while MQP is a technology standard that has actually been built by JP Morgan and eventually open source with the help of Red Hat but also other standard in the business like FIX for brokerage and the trading in the FX industry ISO-222 for payments down to FDX for customer consent FDC-3 the very standard that we have been creating here at Phinos for business for desktop interoperability on the trading floor and also frameworks like the business industry association network buy and that has created with the banks in the past 10 years a business framework to define the partition of the bank but while we're talking about modules if you take solutions there seems to be in different domain that could be a loan origination versus a knee wall procurement if you dig inside there are certain capabilities and function they are all basically the very same we need to we need to work with the product category or directory and also we need to deploy the loan or the ewall itself meaning we need to get the loan to the customer or we need to install the ewallet into the customer's cell phone to start for example making a payment open source here comes into many layers so the business layers where companies and partners can build capabilities that stick to the standard that can eventually be plugged into the solution of the bank but also the open source framework itself how this component connect how they are described how they are looked after where to find them is very important and it is important that this framework remains open because it's like the lattice the framework for the interconnectivity between the players if we go down into stock into the technologies where such component are operator are deployed are developed we recognize of course open source started with languages with Java with Kafka for streaming for example and moreover down in the infrastructure the de facto frameworks standard like Linux and now moreover the cloud world the Kubernetes framework which is common to every industry and every vendor but why is important this component mindset the idea is that if there is a pool of suppliers that adhere to certain specification I can have a choice who to shop with and moreover I can always decide to either shop or build or rent the capability elsewhere so the opportunity here to have a collaboration with your FinTech and banks is kind of clear but it's very well defined given specific business function moreover from a technology perspective innovation every function can be implemented in many different ways that does not imply that this function is changing the way is being consumed by other because the interface is stable so we might see technology they are connected to legacy mainframe or maybe using very new technology in the hardware space like accelerator like GPUs or maybe even quantum compute for no risk calculation or whatever else and application are not even part of the solution deployed at the bank because are consumed as a service over the cloud like could be Salesforce or service now of the likes but the best way to explain is to read by example and creating a proof of concept so that's why we've done here at Red Hat with the participation of few banks and also FinTech and we'll build collaboratively one example we took a process we didn't was important like a new wallet procurement for a customer wanted to pay using the phone and not cash which is kind of important during COVID and so the solution end up to be composed by four business function which are depicted here and eventually by orchestrating those function we created the solution of the aggregation by using some web technology this was important to understand the effort to build application using this capability in a modular fashion and here is an opportunity to work a little much wider scope in the community level it is clear that wide problem in the world like for example disaster management for for natural disaster is a quite complex business solution that also is the correlation between different different business providers the bank maybe a retailer an insurance company even the government itself that comes in the form of regulation and also subsidy to the family that are impacted by a disaster we model all this using this business architecture methodologies one by one we selected all the capability needed to understand the various phases of the recovery going from you know an immediate response of the disaster all the way down to re-establishing the access where we focused on later on and all the way back to the new normal after the disaster is gone how is it possible well first you look at the model from a business perspective you dissect in the capabilities you create the various use cases that you want to accomplish and eventually you given the use case you select the business capability and now you start looking at the choreography of the business capability and eventually you lead to defining how people can start collaborating because the interfaces between the different components are very clear and the case we have shown is working with the fintech we were mimicking the bank side and the other team was working as a fintech side and we were essentially only talking about this business capability and exchanges and eventually where it's off doing their own implementation independently and then we met again at the interface level and recombined all together combine a quite compelling application the idea then was to describe what has happened we have been able to create an experience that goes from formulating the business scenario with business analyst and business practitioner down to a technology and business architecture that is eventually translated into component and micro services how to connect them how to build them and eventually how to deploy them into maybe a construct of a cloud so we use Kubernetes OpenShift Red Hat which is the implementation in the enterprise and eventually we ran this application in production using different clouds and we succeeded doing so just to recap why we should collaborate of course you know we collaborate because we want to scale faster the resolution of problem that might be bigger than the boundary of the bank itself or the fintech and supporting the standardization and open APIs it creates this consistency between the ecosystem of the industry player to build together we also reduce the risk because having more people supplying capability and consuming capability the overall reliability is augmented because we don't depend on the few but we have a network of support and of course more important we continuously improve using the open source fit that loop to generate new ideas and improve constantly with requirements and implementation and moreover I would say because we would like to have more fun working in the community is really awesome with that I would like to conclude seeing how you can how can you work with us well you know you can call Red Hat you can call Phinos you can also moreover contribute your piece your idea there are many ways to contribute and everything since everything and everybody is really important for us and everything matters and eventually more important share your ideas write blog contribute with your code with your artifact whatever you feel able to consume and contribute and with this I'd like to thank you very much for your time and I hope you'll join this beautiful conference thank you Alessandro very insightful vision and always a treat to listen to the vision of an open source leader and a great supporter of Phinos like Red Hat as I mentioned earlier I'm very convinced this community can learn a thing or two from the leading commercial open source vendor in the world as I mentioned before you know creating a lively commercial open source FinTech ecosystem is going to be critical to the success of our projects so I hope the FinTech folks in attendance have found that useful last but not least moving on with our final speaker of the day and no no more Italian accent our final speaker today Sarah Novotny who is with Microsoft in the Azure office of the CDO in recent years she has focused on open source cloud and utility computing infrastructure automation and data big and small relational and non-relational today she's going to be talking about some of the enduring lessons of 2020 please join me in welcoming Sarah Novotny from Microsoft hello and thanks for joining us today I want to chat about enduring lessons in open source technology more broadly and definitely specifically learned from 2020 so let's just take a moment and have a big breath because 2020 is almost over and it has been a deeply weird year doesn't matter where you live or what your interests or persuasions are this year has been hard so take a moment with yourself and say we're almost done there's a lot of cleanup ahead of us but we're almost done with 2020 so I want to talk about people because within 2020 I have found that very few of my problems have been technological problems they've frequently and usually been people problems and people challenges and ways that the people interact with each other and the world that are the hard bit so let's talk about the world for a moment this year this year has been long and hard and of course in March February and March we were actually hit with the coronavirus and the COVID-19 pandemic this has led to so much change in the world in the last nine months that we really are struggling with all of these changes most of us many of us are working from home a lot and that is completely different making our engagements with our peers engagements with our projects completely different and that is something that we really need to understand especially as we look toward a global workforce that can work on our technological problems around the world with all these different perspectives come summer we found that the U.S. is still deeply deeply divided and suffering from systemic racism well we found this out we many of the privileged white people who are not able to or not experiencing this challenge on a day today are we're suddenly brought to attention for the challenges that are facing our peers and friends and people of color within our communities that is incredibly important as a thing that we need to work on we also struggle this year with the fact that global warming is not a little thing the west coast of the U.S. is on fire and the way fires are behaving is changing because of the problems and challenges with our global climate change it's tough to say you know that this is that this is anything but a global problem when it runs the gamut from fires in the west coast of the U.S. or fires in Siberia to methane escape in the Arctic Circle and methane does so much more damage than even carbon dioxide to our world we really need to focus on all of these things so it's been a rough year and I hope that most of you have gotten the support and guidance that you've needed have been able to connect with people at work felt supported in work been able to connect with your social circles your communities that you engage with and feel supported in those and that you've been able to support other people in this what I have found in these communities is seeking out someone else's perspective which is completely different from my own has strengthened and deepened and opened my eyes to the change that is needed in the world learning from people who have different perspectives and then being able to share and grow and interact with those around you who may not have had those same experiences is a way that we can continually improve our world and we need to be focused on that at this point in order to make sure that we are impacting things that are important and consistent we need to make sure that we are measuring things that we want to change not necessarily measuring second order effects but measuring directly the changes we need we need to make sure that we are listening and engaging across differences and making sure that we are able to internalize what we hear just listening and trying to respond or trying to argue is not enough listening internalizing synthesizing and maybe even changing your own opinions about this about whatever you're listening to from this different perspective is very important today and emphasizing we need to make sure that everyone's experiences become more equal today my wish to join a person of color or be a person of color in a particular experience would be very low I recognize that they have a very different experience in the US at least and across some portions of the globe as well but I recognize that they have a very different experience and I have to be empathetic because how they interact how I interact in a world that has such different experiences is super important it's really important because we want to get back to a world where we can interact with people where we can be focused on what we are interested in while the rest of the world is moving around us without nearly as much effort and attention as we have had to put into it this year but that means we need to fix underpinning systemic challenges we have an incredibly divided world right now we have a world that is moving more toward nationalism and less toward collaboration in a global economy that's worrisome we need to be paying attention and collaborating across those people who are happy with the policies and those people who are unhappy with policies it's work that needs to be done and that work is not glamorous that work is work that we need to do in every one of our communities open source communities preschool communities city communities and we need to make sure that we are able to and invested in doing the unglamorous work doing the heavy lifting the change requires and when we see a change that's happening and behaviors that are supporting that change we need to be sure that we're rewarding those behaviors we're celebrating the people that are making that change we're celebrating the way that change is happening and most of all in all of this especially since we are technologists who are building tools and building new ways to engage with the world we need to make sure our tools cannot be weaponized and that our tools respect privacy and do good in the world any tool can become a weapon but starting from the premise of how to limit any damage created by this tool is also an important ethical consideration as you're developing something just because it can be developed just because it can be a product doesn't always mean it should be I'm looking forward to 2021 I think there's a lot of possibility ahead of us I think there's also a lot of work ahead of us but I wanted to end on a happy note I wanted to end saying saying respect your privacy for sure but I wanted to end and go through 21 with a positive note where in I want to say you're amazing and your amazingness in this world is brought to bear on every decision you make your team makes and your communities make around you so please reach across any divide you see any challenge you find any hard conversation that needs to be had reach across those differences and try to come to some sort of understanding and if not even understanding respect for the individual who is presenting that opinion because we still are humans and human dignity is an important part of our growth through this very difficult year of 2020 and on to the hope and potential of 2021 so my last recommendation for 2021 given the year we've had in the past is to make sure that there is space for fun and novelty because one of the things that we have been most missing in our year 2020 is the serendipity and novelty of random interactions with friends with people on the street with someone in a coffee shop so be silly have a bit of fun go out and do good in the world thanks very much thank you Sarah I definitely couldn't agree more on the fact that open source can bring together folks from all over the world regardless of the political orientation race gender religion or whatever you're coming from and it's largely orthogonal to ongoing relationship within countries so there's definitely still a lot to do there but I'm in violent agreement that open source can be a strong unifying force here so that wraps our today's keynotes so let me thank you and send a shout out to all the amazing speakers we've had today please enjoy the rest of your day I hope you'll be able to follow as many breakout sessions as you can and don't forget to ask the expert sessions which are going to go on later in the day and remember to visit our sponsor showcase connect with other attendees with the Phoenix and Linux foundation team on the Slack workspace that we set up and definitely participate in some of the topic-based chats there's so much going on in our community so I hope you'll find something interesting and useful to connect on finally join us for our keynotes tomorrow Tosha Elison our COO will be leading the conversation and share with you all the progress they were doing in our community in our work with regulators and more so thank you so much for attending this morning or afternoon wherever you are and please enjoy the rest of your day thank you