 Okay, so I think we can start. First of all, thank you everyone for staying for today's talk. Today I'm here to talk about ASPUS in finance, but before starting, I'm here to say that I'm not an expert in finance services, I'm here to talk about what I've learned and give some remarks of the experience that some people in the Tudor community that are OSPO leaders around different sectors, including OSPUS in finance, have been sharing across within these years. So first of all, I will give you some context of what's building an OSPO in finance and some of the challenges some of these OSPUS are having facing so far. Then I will be talking about OSPUS and what really is an OSPO and the main character is an OSPO. Then I would like to serve some financial organizations that already have an OSPO and are engaging in Tudor and in other organizations such as Finals. And finally, the main goal of this is also to bring an open discussions on how can we collaborate both Finals and Tudor Group to help more OSPUS in this sector to be created and also have the existing ones to advance. So I will start with some open source context. Many of you already will know that open source has one. And this is from the last open SSF conference in open source summit where they serve this data of like 90% of modern applications using source code and it's very likely that in your organization even though you're not contributing to open source at some point you are using or your engineers are using open source. So if you're using open source it's also people are starting to realize that it's time to give back and not only using because if you ignore that part vulnerabilities and risks can come of just using and not taking care of the open source. So from the Finals perspective there's been some restrictions and sometimes some barriers from people to actually get into open source and get into an OSPOT that I will later explain better and has also be directly affected to the ability to execute to advance in the open source journey. More of those are regulators, organizational culture of the Finals and Services and technology trends. And broadly speaking the three main goals that I've been hearing across all these financial systems with an OSPOT has been we need to awareness, we need to realize the benefits of open source code and collaboration. We need to enable open source contributions rather than consumption and we need to enable safe and compliant open source collaboration and I've highlighted safe and compliant because that is one of the main focus of the financials OSPOTs legal driven states and then from that once they have that move into more community driven states. So for that for starting the open source journey I wanted also to highlight the work that Finals are doing in the open source readiness project. I think they have great resources on how to invite organizations to start taking care of the open source projects and the open source efforts they're doing. So they have an open source policies focused on the financial systems. They have an open source maturity model. They have a working group to discuss about the status of open source and financial systems. I think those are really great resources to get it started and to actually understand the value of open source for an organization in the financial sector. But sadly, that is not enough. Realizing about that open source matters and starting to interact with open source it's pretty normal nowadays. And if your organization wants to start the journey to become an open source first organizations you can take the long way, the long path starting to do open source ad hoc, that is. Okay, there is a vulnerability here. How can we fix it? Let's start with this team. Okay, let's start to do open source as the issue starts and as the issue happens or you can put a strategy. You can have a dedicated team or a matrix of experts that acts as a central place of this so they can guide better and you can accelerate this journey. Because as I said adopting a strategic posture around open source is no longer optional right now. And that is what an OSPO is actually. Some organizations started to put a strategy on top of all the open source efforts to accelerate this open source adoption and accelerate this innovation. So the short answer is OSPO's are more like a designated place that is where you put all the open source operations and efforts and to visualize better this idea I also like to share this graph where it's like okay where's an OSPO, when is the time to start an OSPO? Well if your organization is starting to think about let's have open source policies. Let's have an open source strategy. Let's build a matrix of experts. Then is when you should be thinking about an OSPO. If your organization on the other hand is doing open source at hoc, there are no coordinated efforts, there is lack of alignment within the organization or even the top level management doesn't really understand the value of open source like yeah they know open source is there but they don't really get it. Stay just wait and keep building this awareness. And once the organization realize that they really need strategy and policies and they start to take care of the strategy it's when an OSPO might be a good opportunity to have. So also to explain better and to define better what is an OSPO. Here are some characteristics that can define an OSPO and can help you understand better. So if your organization has an OSPO it's very likely that your employees are tasked with fostering and nurturing open source usage. You have already employees that are contributing code to open source. There are processes, procedures and tools to facilitate this open source consumption. And as I said the decision makers already recognize that open source software it's important for the innovation of the organization's product or services. Here are some of the characteristics that an OSPO can have. And I highlight an OSPO can have because there are OSPs that only focus on two, three responsibilities. There will be OSPs that only focus it more on the legal side or for instance oversee open source compliance or working on the inner source side. But there will be others that tries to gather all the different responsibilities. So this is just an example. So in a nutshell, starting an open source program office means moving from open source ad hoc to adopting a strategic poster on open source, infusing the whole organization with a clear understanding of open source. So what is this? Communication. Because that is sometimes a really important topic that maybe your organization, you have a team involving open source but it's not aligned with the organization's goals and then it's for nothing because you keep building your goals and the organization have another different goals and you're stuck. So it's a way to also build this matrix of experts around different teams that can communicate that can speak the language of those teams and thus everyone is aligned. Everyone knows the benefits of open source and how to be involved in open source. And finally, it's also a way to celebrate open source adoption and thus innovation. But let's go beyond that. I will also talk about a way where people can better frame OSPOS because OSPOS has a journey. Like there are OSPOS that are just starting and they're really seasonate OSPOS that has been there for almost a decade and they have been advancing. So in Tudu, we work together into a maturity model that works as a framework to understand the different maturity stages that an OSPOS can go through and I really want to serve briefly all these different stages and maybe if your organization has an OSPOS right now or you're thinking about having an OSPOS you can try to map where it is in this model. So this model is composed by four different stages. The first one is the legal driven. You need to take care of the inventory. You need to first assess that. Then community driven, engagement driven and leadership driven. And all this depends on the ability, the OSPOS level will depend on the ability to execute. During the first stage, the legal driven stage, as I said, the organizations are trying to identify all the legal and security risks. So it's about careful licensing, developer education, inventory taken. Once the organization has all that in place and they know which project, they have a list of projects like these projects are green light, these projects are red light, okay, let's go. It's when they can start building this community driven stage and start building ambassadors to build this open source education within the organization and train developers to contribute to open source. And also amplify the message. And once that education is somehow adopted, we can move to a more mature community driven state where the employees can actually take actions, take, have quality contributions to open source. And they can begin to streamline and optimize open source of bound contributions for the developers and even launch open source projects. When you are more mature, when the organization is more mature in the OSPOS, they can move to engagement driven states. So they are actually taking action. So it's when they can support incubating and launching open source projects. And it's the time when the OSPOS developing playbooks, processes checklist to help them help the organization start being open source first citizens. And finally, the leadership driven states. Here is when the OSPOS can become this advisor for the city hall and they have the knowledge and the means to benchmark what constitute a good and acceptable open source projects based on where do they want you to go and the technology stacks. And you might be thinking, okay, this is great, but maybe it's too advanced for financial systems and financial services. So that's why I also wanted to show some examples of real organizations in these sectors that actually has an OSPOS. And not only they just started, but they have been there for decades, some of them. So the first two examples, Bloomberg and Capital One, for instance, they've been like, Bloomberg was one of the first organizations that joined to do some years ago. And now they are, they can call themselves open source first company. They have been doing great efforts to the open source community. They know how to get involved in open source. And then Capital One, they started the open source program office more than five years ago. I also want to give a shout out to Goldman Sachs. I think they have been engaging in open source a long time, but they started the OSPO last year. And since last year, the journey they have been taking has been tremendous. They have been engaging in too, as well. So I've been able to follow the work really closely. And they also even created a webpage for the OSPO where they said like, these are all the open source projects we are contributing. These are the open source projects we are releasing our mission, our vision. I think in the open source summit, they talk about the journey of Goldman Sachs in the OSPO. Really recommend you to take a look if you haven't done so. And also wanted to highlight all the OSPs that are being formed, Fannie Mae, for instance, and more that are yet to come. That they haven't served that publicity, but eventually they will do. So there are, this is a movement that is happening, also in the financial systems. And this is not just organizations in the early states, OSPO, but also organizations that are quite seasonate. So to end up with, I would like to open up discussions here because I think the main goal of this talk is to discuss about these topics on ways how can we work together across communities to increase OSPO adoption within financial services. So here are my three questions. The first one, how can more OSPOers help out financial services firms? I mean, how can other OSPs from other sectors serve their knowledge and can those knowledge be an inspiration for OSPs that are being formed in the financial services? Also, how can OSPs in financial services, the existing ones, collaborate with other OSPs to build and contribute to common tooling and infrastructure? And finally, how can we infuse OSPO learnings into a Finnish readiness program that is focused on help financial services to adopt open source and build this strategy and politics across open source and help its adoption in finance and banking sector? Just two more slides and then we can go through this open discussion. Start the story about Tudu, because I've been talking about Tudu, but I haven't explained what it's to do. It's also a Linux Foundation project. It's an OSPO network in a space, but we also create resources. And the good thing of this is that it's the community builds it. So it's formed by OSPO participants and OSPO leaders worldwide and across different sectors and divisions. In fact, Goldman Sachs is there, Capital One is there, Bloomberg is there. So there are also OSPs in finance working on these resources. And we do these OSPO guidance and support through networks, spaces, education, training, research and tooling. And this is me. You can follow me on Twitter or connect with me on LinkedIn. Happy to do so. And thank you so much. And we can move now to questions and then to the open discussion. Thank you. Okay, so are there any questions or we can maybe try to bring this discussion on how can we, Tudu can collaborate to have this OSPO adoption in the financial system. Yeah, yes, Tudu. So right now we have the, how's it called? Whipple Inter, that I'm not in the project itself, but as far as I know, it's a way to scan, look for issues on every single repository. I don't have a lot of videos on that because as I said, I don't contribute to that, but if you go to Tudu Group GitHub Organization, you will see all the, you can read the redmi file and see the tooling for, that is focused, I know like a lot of OSPOS uses it. And I think Chris is there and he contributes to that. So maybe he can say more details about the project. To start an OSPO. So first I will say, Andrew, I'm gonna go here because I think this is key. First, ask, try to see where is your organization in the open source journey? So are you working on a strategy on policies? Is the top level management aware of this or not? If they are willing to start these policies and strategy around open source, then start thinking about building these metrics of experts. Like where are the right people across teams that can start collaborating in this open source and act as the center of the open source operations? And well, and of course, many OSPOS, what they have started with was doing the legal driven states. So starting with everything related with taking software inventory, building the list and covering all the risk and licensing things and, yes? Sorry, I'm trying, okay. Any other questions? Yeah? Looking to open source projects is a problem. It's demonstrating value to management in consuming from open source projects which is a lot harder to do than making contributions to open source. And in order to consume open source you have to have the policy and everything where it is in place because you're taking code now from the outside and you bring that into your organization. So I guess the question for me is how do you convince management to put through the effort, to go through all the effort of putting the policies together so that you can actually consume to demonstrate the value? So I guess that was the question of high. If you have any thoughts, anyone has any thoughts on that? I mean, I think there are many ways to do that and I can give some suggestions but these are not like rules at all. I think if engaging with communities like, for instance, to do one of the feedback that I usually heard is that I can talk with all the people that have same issues as me and for instance, convince us the top level management of building policies around it's one of them and I can get some inspiration of what others did in the past and apply them. So if you have time to go to this network in spaces, I think it really helps. There are also some articles from people that had an Ospo starting an Ospo and actually it's like how to convince your manager to start an Ospo. One of them is in the Tutu blog but one of the Tutu members is Ivan. So I really recommend to at least take a look. Maybe you can find something interesting there. Yep, good point. Yep. I think it's the financial component of the city. We've all found a great place for anyone who's a large factor to go to see where they're in value. So for those of you who don't know that, that's to do with how we've been up to our construction, which is to find which of the common problems are solved. So there are plenty of opportunities to demonstrate the value of the system and be sure to be at the risk of making it better than how it might be shared away. Just to add something on that, I think like doing from bottom to top to top down, I mean, both approaches needs to be done in this, like not only top to bottom, but also the other way as well. So if there are no any other questions, thank you so much. And if you want to chat or catch up, I'll be happy to do so in the break room, in the hallway. Thank you so much. Thank you. Thank you.