 Okie dokie, well I think let's go ahead and get started. So hi everyone, I'm Rosalie, I work at Goldman Sachs and today I am super excited to share with you how we started an OSPO. So I'll talk you through sort of how we planned it, how we structured it, what our goals are and sort of where we are today. So a little bit about the agenda, so I'll explain to you who is Goldman Sachs. If you're not familiar, I'll talk about some of the projects that we've open sourced. I'll talk about why after 150 years did we decide now is the time to create an OSPO at Goldman Sachs, what motivated us. I'll talk about how we went about planning, what our goals are, how we structured it, what our learnings are and then what is the progress that we've made so far and then I'm mostly excited about the Q and A portion because that's when I get to hear from you awesome people and you get to ask me really cool questions. So let's get started. So Goldman Sachs, so we have been around since 1869 which means that we have been around for more than 150 years. I will say that that is before my time, I am not that old. So we are headquartered in New York. So we are a leading global investment banking, securities and investment management firm. We have a wide range of financial services. We work with corporations, financial institutions, governments and individuals. So let's talk a little bit about open source. So at Goldman Sachs, we love open source. Our engineers love using open source, we love contributing to it. A couple of the projects that we've actually open sourced, I'll go through them here, but if you haven't explored our GitHub before, we're at GitHub at Goldman Sachs and a couple of the projects that you'll see there are things like GSQuant which is a Python tool kit for quantitative finance. We also have given a project to the Eclipse Foundation called GS Collections which is a collections framework for Java and something that you won't see there that we're super excited about is a project that we actually gave to the FinTech open source foundation. Anybody familiar with FinNOS? There we go, yep, great, great folks. So we actually worked with them and we gave them Legend which is a data management and data governance platform. As you're probably aware, data management and data governance in finance is quite complex. So this is a platform that we would love to have folks in the financial industry take a look at. So those are some of our projects. So now let's talk about motivation. So as already mentioned, we've open sourced projects before, our engineers love open source, they love using it, they love contributing to it. So what are some of the reasons that we now decided to start an OSPO? So as mentioned, really strong open source usage. We really sort of wanted to improve the developer experience. So we wanted to make it really simple for folks to use and contribute to open source. We also wanna give back to the developer community. So we're using a lot of open source, we are open sourcing projects. We also think that we have a lot of learnings and best practices that we've sort of accumulated in our sort of 150 year history that we wanna share with the financial community as well. And we also know that if your company is open source friendly, then developers who love open source will be more likely to wanna come and join your team. And so another thing for us is we really would love to continue attracting incredible talent. So again, some of the reasons are strong usage, wanna improve the developer experience, wanna make it easy to use and contribute to open source, wanna share, wanna be involved in the community. So after today's talk, really wanna encourage you if you think there are ways that we can work together. Definitely come chat with me because we definitely wanna collaborate. And then as mentioned, really wanna attract, continue to attract incredible talent. So with every big initiative, there's a lot of planning. So I wanna talk a little bit now about how did we actually go about planning and creating this OSPO? So the information that I'm gonna share with you now, I wanted to do a little bit of context setting. The timeline is actually quite short. So last year in November, we started gathering feedback from folks. We spoke to like more than 100 plus engineers, engineering leaders, anybody in the company that is using or contributing to open source. So we gathered a lot of feedback and then we created a plan in the form of a memo. And then in April of this year, we presented it to our leadership. Our leadership is really incredible. We have folks, really incredible CTO, CIO, folks that are ex-Yahoo, Amazon who are really passionate about open source and wanna see us more involved in the community. So we presented to them and as you can see, they must have really liked the presentation because it was a yes. So May through July of this year, we formed a team. And then in August of this year, we actually announced the OSPO internally at the company and the response was incredible. Folks were like, this is amazing. And then obviously the JIRA ticket started flowing in because folks were like, I wanna do this and that and this. And so we have, I can tell you we have been just slammed with inquiries and folks wanting to collaborate. And we have thousands and thousands of engineers. So it's really cool that now we have a formal program for them to collaborate on open source. So now let's talk about the planning. So we knew that our ultimate goal is we wanna streamline contribution and consumption. So in order to do this, we had to identify who would lead this initiative. So we landed on someone named Rohan Deshpande. He leads all of open source at Goldman Sachs. He was previously at Amazon and just in general, he is a huge, huge fan of open source and his free time he likes to contribute. So he loves open source, he understands open source. So he was selected to run with this initiative. And I'm not just saying this because he is my boss, but he's also a really great person. So I think, you know, they picked a really great person for this initiative. So what we did was we first said what is the current state of open source at Goldman Sachs? What are we currently doing? What's working? Where is there room for improvement? We also figured out who are our stakeholders. So stakeholders throughout the company, and as mentioned, we have thousands and thousands of engineers. And then we figured out what are the use cases that we are trying to solve for? So what's the current state? Who are the stakeholders? What are the use cases to solve for? We then took a couple months and we created a multi-year strategy in the form of a memo. We reviewed it with engineering leadership. And within that memo, there were several pillars, but they all sort of focus on simplifying, contributing on behalf of the firm and personally. We want to connect and collaborate with the external community, you awesome folks. And then we wanna treat our developers as customers. So when we engage with our developers, we really wanna hear from them, you know, what process, what do you like about the process? Where is there room for improvement? So we have frequent communication with our community to get that feedback. So we treat our developers as customers. So the outcome of all of that was we need to create an OSPO. And this OSPO is gonna be responsible for procedures, policies, community engagement and tooling. And we also acknowledged that with each of those pillars that I shared, that we still need to explore a lot of them a lot more and sort of do a deep dive. But the ultimate ask was for us to get started on this, we need to create a founding team. So we asked for really minimal funding to create a founding team. And so on that team, I get to work with really amazing folks. We have a program manager who has a really strong background in open source policies and procedures. We have an engineering lead who is a senior engineer who has many, many years of experience building software within Goldman Sachs. And he's just really passionate about open source and really had seen how we were doing open source before, so familiar with the process. So was able to dive right in. And then they also happened to hire a developer advocate. I may or may not know her, I think she's okay, who has experience in community and content and events for both internal and external. So as you can see here, a pretty small team that is sort of getting started on this initiative, right? And sort of how do we get started? Where do we wanna go from here? So as mentioned, we spoke to a lot of engineers, more than 100 plus engineers. And in doing so, very quickly, we were able to realize who are our open source champions. So folks, one of our open source champions, he's amazing. He said, here's 100 plus different projects that I wanna bring in. So I'm like, you are very passionate about open source. You are awesome. And basically they started giving us feedback on what they're currently doing with open source, where they would like to see us go. So we have frequent check-ins with our open source champions across the company. So we're always asking them, hey, we're trying to do this. What do you think about that? So really important to figure out who are your champions. And then we also established channels to get feedback. So we have like an internal kind of a chat channel. We have email, we have JIRA. And we're also doing sort of these one-hour sort of community meetings where folks will be able to give us feedback as well, learn more about what we're doing. So with all of this, it's always important to figure out like what are your goals, right? Where are you heading? What are you trying to do? What are you aligned on? So our goals have been and very much are focused on meeting developers where they are. So with all of the processes that we're creating or any policies or anything that we wanna launch, we figure out what is the current developer workflow for that and how can we meet folks where they are versus creating something totally brand new or sort of like bespoke. We wanna eliminate ambiguity. So anything where folks are like, hey, I wanna do this, but I'm not sure sort of how to do that. Can you give me more guidance on that? We actively work with developers on that as well. We want to grow a code and project contributions. So not just like open sourcing projects, bug reports, patches, anything that we can help these projects that we're using internally with, we definitely wanna do that. We wanna give back to the community. So we wanna open source projects. We wanna share learnings on our blog. We really wanna be involved. We wanna engage with the community. We wanna learn from you, right? What are your best practices? How can we start using those? And then we really wanna share our learnings and our experiences. So a little bit about our structure. So we've got our founding team, which is quite small and we are actually hiring. So we've got a program manager, a lead engineer and myself and then Rohan who leads the open source program office. So we've documented and endorsed our strategy and we've converted that into OKRs. So like everything we do is being tracked against these OKRs and we're reporting weekly on those making sure that we're in a good spot. We use JIRA for all of our tracking our progress. We do weekly updates to engineering. And then we also have, which is really fun, our lead engineer, when she first started on the team, she actually created a community newsletter that now has grown significantly where she was just sharing sort of what we were doing in the company with open source, what was coming up. So myself from a community perspective, I thought that I said to her, you're doing an incredible job on this newsletter. Like you should be doing what I'm doing because it was just really, really great. So very much encourage folks. If you don't have an internal newsletter for your community, definitely create one, sort of recap all of these great highlights. So some of our learnings, what have we learned in the past couple months? Always, always focus on the end-to-end developer experience. As mentioned, developers are our customers. We want to give them a really great experience. Also live the experience. So if you put together something like a process or some idea, instead of just rolling it out based on feedback, personally experience that process and see how would you think about that? So live the experience. And whenever you're starting something brand new, there's a lot of moving pieces, right? And like for us, we have an enormous amount of interest from folks within the company. But ultimately you have to identify sort of what is your North Star, right? Where are we today and where do we wanna go? And I'll believe also that relationships are almost basically everything. So build relationships. As you're building out your program office, meet with folks. So collaborate with folks in marketing and sales and training. If someone says to you, hey, like I heard you guys are doing this open source thing, right, what is that? Connect with people, answer their questions because they might not be as familiar with open source right now, but as they learn more, they are always really amazed. Their feedback to me is always, this is incredible. This open source thing is really, really cool. So encourage you to share about your OSPO outside of just the engineering community as well. And then be transparent and visible. So if something is working great, share that. If there's room for improvement, share that. But keep folks updated on sort of the journey, right? Bring folks along. Keep them posted on what you're doing and where you're hoping to go. Communicate, communicate, communicate. Very, very important. So some of the progress that we have made so far. So we have, now we have an inventory of all of these contributors and contributions that we're making. We have a process for folks want to contribute to projects or they wanna be, if they wanna be able to do that, we are able to get them, get that logged. And so we've got an inventory as mentioned. Bring your own device, really cool. So folks are able to contribute to open source on behalf of Goldman Sachs. I'm actually using one of their, like their personal devices, like a personal laptop, which is really cool. But we now also have a blog. So as mentioned, we very much wanna share with folks. So on our blog, we're now sharing, everything that we've learned from sort of building products, scaling them, launching and scaling them. So very much encourage you, if your OSPO is doing really interesting things that could be helpful for others, think about doing a blog. Definitely do social media. We now have a Twitter account as well. If folks wanna pull out their phone and follow, I'll take a second here, no problem, which is GS Developer. And we've also started joining foundations as well. So super excited to announce that we've joined OpenSSF and we've also joined the to-do group. Any folks in here part of those groups? Yeah, there we go, awesome, cool. So in only a couple months, we've made quite a lot of progress. And I'm personally excited about the fact that just we have so many inquiries from folks now wanting to work together, wanting to do things. The enthusiasm is just really, really high. So I'm excited that it's not only internal interest, but now we're able to start doing external things with the community as well. So I think it's just a very, very exciting experience. And at this time, I would love to see if folks have any questions that I can answer and if there's a question that I can't answer, connect with me afterwards and I'll connect you with the right person. Okay, yes. Yes, yes. Yeah, so we have a really... Oh yes, so the question was asked is that this sounds like this is very much, the Ospo is very much driven by developers. So the question is, what is our relationship with legal? How do we work with legal on this? How do we do that? So I'm super excited. So I only joined a couple months ago and I instantly was put in touch with the person who is responsible for legal for the Ospo. And what I said to him was like, this is amazing. You remind me so much of someone that I worked with at a former company because this person and the legal team in general is super excited about what we're trying to do. They understand the value and so it's super collaborative. Like we meet frequently, we'll explain a process that we're trying to drive, we'll answer any questions they have. So that I think goes back to the relationships aspect where it's build relationships with folks, answer any questions they have and then folks see the value of open source and so they're happy to work together. So I would say we're really fortunate in that respect because we do work closely with them but they've been super collaborative. I have to give a quick shout out at my former company. Ashley will actually know this. My former company, one of our legal contacts, there was actually a developer as well. So on the weekends, he would just be coding for fun. So I thought that was quite fun. Yeah, any other questions? That's a great one. Thank you so much, sir, thank you. Okay. All right. Well, no other questions then. Well, thank you very much, folks. And just as a quick note here, we are hiring, that is my link tree. So if you know any great folks that are looking for really great developer roles in finance, we also have an opening on our open source team. Definitely visit that link. And just really wanna thank you all for coming out today. So thank you so much. I wanna clap for you. Thank you.