 Mae genious Rodd Mofits, I'm the senior technical architect for Finos, and thank you all for coming. I hope you're having a great time at OSFF. With me today I've got Vicki Chung, Kay Shonvche and Priya Gupta. Did I get there right? Yes, we're very grateful to be joined by a part of the Goldman Sachs Osbo team. ma sy'n ddweud rwy'n dweud hynny, a gyrm Studiosóa gyntaf ar y dyfodol. A dydych chi'n gweithio, dydwch chi'n rhoi. Rwy'n edrych yn erioedd, angen i'w ffwrdd yn ni'n gobeithio i yw am hynny yn ysgrifun. Rwy'n i ni'n gwneud osbo, rwy'n i ni'n gwneud osbwynt. Rydy raid cyd-gyn wybodau yma yn gweithbos yn ei ddweud, ac mae'r amlwg yn y syniad o'n ysgrifennu. Dyna yw'r cyfnod o'r ffordd yn ymgyndoedd. Mae'r ffordd yn ymgynno'r dyfynod, a'r bydwyr yn ymgyrch ac'r ffordd yn ymgyrch o'r gwasanaeth cyfnod og ymgynno i'r ffordd. Ond, maen nhw'n rhaid i'w ysgolwyddoedd hans? Felly, yw'r cyfnod yw ymgynno'r ffordd yn ymgynno'r ddweud? Yn ymgynno'r ddweud, maen nhw'n ymgynno'r ffordd yn ymgynno'r ddweud? aTY內 i fy ychydig yn ôl o'r osbwyr? Felly, yna ffarnwyr yn yma, cyn 10 o ffarnwyr dan yn dweud, ac bydd arna i'n ddweud yeld yna yn gweithio, hefyd. So, nes yw, fyddwn yn y panel. Yna'n mynd i, Michi, Kay i Pridd. Rydw i'n fydda i bwyl ffordd i'r gwasanaeth iddyn nhw? Mae hynny'n gweithio? Roedd ychydig yn ysgrifennu a Llyfr Eidl, o osbwyr. Hi, mae'r fyddo i'r Llyfr Eidl. I'm a program manager at the open source program office at Goldman Sachs, so I joined around this time last year in late November 2021. It's been a while and I was actually the first non founding member of the Oslo, so it's been really cool to see how we expanded throughout the past year and did a lot of great stuff that we're about to share with you. My prior experience is in consulting and attack industry as well as product management and data analytics and engineering space. So I love working with developers with users, business stakeholders, and this allows me to bring all these relevant skills into my current role. So now I focus on both program management and product management, both focusing on improving the developer experience at Goldman Sachs. Hi everyone, my name is Kay. Can you guys hear me? My name is Kay. I'm also a program manager and the organizational change and development lead for the Oslo at Goldman Sachs. So I saw such questions as how do we integrate an open source culture into the firm and how do we capitalize on opportunities to increase open source participation. I joined the team in February and I actually come from a non traditional background. My background is actually in retail management. I transitioned into tech, graduating from a software engineering book camp early 2021, and my passion lies in the customer experience. I love supporting and developing people and creating a very inclusive culture. Hi everyone, this is Priya. I'm one of the engineer in Oslo and I joined firm 10 months back and my job is to provide standard infrastructure for open source contribution as well as building and monitoring tool for enabling and tracking open source contribution in the firm. Before joining GS, I work in other financial institution and I bring in my skill of building and monitoring robust infrastructure and data warehouses. Awesome, thank you very much. Okay, so I just want to have a quick point of order. So if anyone's got any questions, we'll have a session at the end if you've got any cues and a's you want to do. So please think about some questions as well. We'll be interested to find out what the audience thinks. So, as we saw earlier, there's been there are lots of people in this room who are working for organizations that don't have ospos. So what I wanted to do is take us back to Goldman Sachs as it was before you had the Ospo and maybe hear a bit about that and find out, you know, what what sort of what the circumstances were like to lead that led you to starting one. Yeah, so Goldman Sachs has been involved in the open source community prior to the launch of Ospo. You know, in 2012, we launched a GS collection. It's not formally known as eclipse collections. 2016, we open source Reladomo and some of our more recent open source projects is just quant. We have two projects that we've contributed to fennel so that is catch it and legend. And so without having an Ospo, these projects really needed. They paved their own way. Engineers didn't really have visibility into the process of how to participate in the open source community. And they also probably didn't know that they could. So launching an Ospo was a really big win for the firm. Our engineers are now equipped to really participate in the open source community. So we're really happy about that. Awesome. So this for the eagle eyeed among you, you will notice that there was a fourth person who was supposed to join us on the panel, Bella Wiseman, and unfortunately, Bella was ill today. And that's a shame because Bella actually, along with Ro, who's in the audience here, Rohan, sorry. Sorry, Rohan. They actually put together a memo to try and start the Ospo at Goldman Sachs. And Bella told us about this and it involved collaborating with all the different areas of the business, all the different concerns like legal, different technology departments, trying to get sort of a buy in from the whole firm in order to start the Ospo up. And I think you guys are the result of that really, aren't you? You've been hired in because of that memo and that work that Bella and Rohan did. So I guess the next question I wanted to ask you guys is how is your Ospo structured at Goldman? Because I think so my experience at Finos has shown me that there are lots of different ways you can do this. You can have like you can have an individual who is like just takes on some of the job of an Ospo or you can have like a whole guild of people who kind of come together and be an Ospo comprising different parts of the firm. Or as you guys have done, you've like got an actual dedicated Ospo team. So maybe you can just talk a bit about the structure of that team and what your individual roles are within it. Vicky. Yeah, so as I mentioned when I joined, our team was really small. It was our MD who was going to be giving a talk at 530 years ago. Bella, our engineering lead and our program lead Rob Underwood, who's also here. And then there was me. So four people, very small. I'm coming from a consulting and probably measure background. I was hired because I can bring these like developers and trick mindset to the team. Love working with engineers users and being a bridge between those two translating user requirements to technical. Requirements that was where my passion lied and I still really enjoyed doing that. So on the program management side we do standardizing policies around open source contribution consumption participation guidelines licensing resolution and management. On the engineering side, we also have our internal contribution tooling that we continue to improve revamp and create new features for. So after a while we realize how large the scope actually is and that to run the program efficiently. We actually need to quickly staff our program. So after me, we decided to have one more program manager to take on the participation and community building aspect and K given her nontraditional background is very customer centric and really good addition to our team. And we also started to onboard full time engineers who can dedicate their time and building out our tooling. So maybe K and pre I can talk a bit about that too. Yeah, I joined the team and I think initially I was like what is what is my role going to be here but you quickly find out that it's so important to make sure that your developers understand what journey you want to take them on and communication is so important, especially when you're trying to integrate a new initiative into the firm. So my work really heavily depends on how do we create a sense of community within the firm, but how do we extend ourselves beyond the four walls as well to make sure that we are engaging with external community as well. I think I can talk about why any engineer and my role was important in our sport. So we had a tool for open source contribution, but the tool was pretty old and we wanted to create something new addressing all the issues we had with the previous tool. And also we needed some engineer who can closely work with the tool and understand the pain point of any contributor other than working on tool. I think engineers are important to work on data matrixes and dashboards to quantify and evaluate the contribution growth and to identify how many active contributors we have in years. How many contributors we have which are not associated with years. Also, moreover to that I believe having engineering point of view to understand and tackle any problem is very important for the success of any product. That's great. And Priya, I think one of the interesting things about your job is, is you are an engineer working in an Ospo. Obviously Ospo's are usually there to serve engineers, but you're actually an engineer serving an Ospo serving the engineer. So that's an interesting kind of. Yeah, of course, because being an engineer I have used like tons of libraries and frameworks and I know how difficult it is for any financial institute to onboard any library and it was like next to impossible if you want to contribute to those libraries or you want to fix anything. But that's very interesting that Goldman Sachs is motivating their developers to give back to the community. A nice one. And I'm going to go back to Kay for a second because Kay, you've kind of got a theory about how your Ospo works based on your experiences in retail, right? Yeah, definitely. So as you know, our Ospo is fairly new. So we have a lot of initiatives and a lot of projects that we wanted to accomplish this year. And I say like no matter what we're working on, we always concentrate on three P's and this is something that I took away from retail and that's people, product and presentation. So people concentrating on your developers knowing who they are, knowing what their interest lies in your and your product. So knowing that your product will reflect your people and this can be anything from tooling to open source foundations presentation. Where will this product live and how do you promote this product externally and internally? Lovely, yeah. OK, I'm just sorry. OK, so I think, yes, so I've kind of gone a bit off the track here, haven't I? But I was wondering if my next question is going to be around, you know, how you find working in an Ospo. So as I said at the beginning, other people's experiences that Ospo can be very different in structure and different organisations. And there are probably people in this room who are just embarking on their Ospo journey. You know, it's a really popular thing to start doing. So I think what I'd like to ask you is what have you found? What has come as a surprise in, you know, starting your Ospo? What are the things that people will be surprised to hear happening? Yeah, so having a well rounded Ospo actually entails so many things. The scope is really large. And usually we think of license management. We think of contributor license agreements or actually contributing to open source projects or consuming software packages. But I think what's really cool about our Ospo is that we're super developer centric. And some examples is we have this Ospo ambassadorship that we called. We set up quarterly meetings or irregular meetings with Ospos or relevant teams from other companies. So these can be places from the buy side in the financial industry or just other tech giants in the tech industry in general. And by talking to these people, we share knowledge, resources, the difficulties we have faced, what made we successful and it really helps us to grow and understand what might enable us to achieve more and help our developers more. Kind of related to that, we also have a lot of internal events and awareness promotion workshops. So we started by integrating open source to our onboarding boot camps for all engineers who just joined Goldman Sachs. And now that when everyone on boards to GS, they know that open source program office is there that we're here to help you every step along the way. Anything around open source you can come to us. So there's this one team of subject matter experts who can help you. Everything about open source. Along with that, we also have special workshops where we invite organizations such as Finals to talk about how to participate in working groups and other events or workshops such as how do I start contributing to open source projects. How do I consume which licenses means what or how do I contribute open source projects on the side as my hobby. So a lot of these workshops, the goal is to increase awareness of open source in GS and continue to ship that mindset for people that open source is the way to go. Yeah, so I think that's what unique about our hospital. I mean that is that also speaks to my experience as well of working in open source in banks. What you described there sort of a lot of that is all about changing minds and training and culture. I think those are perhaps not obvious at the outset, but you know, in banking we don't have a strong culture of sharing stuff and working together in with our competitors perhaps. So I think it's really interesting to hear that you say that. And also I've helped out with that. I came along to your Goldman Sachs presentation. You did. Thank you. So OK, so I want to turn to Kay and ask what do you see as the challenges if people here want to build an Ospo in their organization? What are the challenges they're going to face? Yeah, I think one of the challenges that I've seen working with the work that I do is there is kind of this perception or narrative that it's a little bit too hard to participate in the open source community or that you can't do it at all. Especially within the firm that we work in or industry that we work in with so many regulations. And so our goal is to really build a yes you can culture around open source participation and to really establish an open source inclusive experience where no matter what level of experience you have in open source that the door is there and it's welcoming. Becky, did you have any other? Yeah, I think first thing our Ospo is still so new as you might have already gleaned. We formed in August 2021, so we're only one plus years old. A lot of people at GS still don't really know about us. That's why we continue to have these events, have these internal workshops to promote the Ospo and open source in general. Secondly, we do get a lot of questions about software package licenses and this is totally understandable because developers are not lawyers. Sometimes they have questions around non-traditional licenses, dual licenses, and we have set up a process on guiding them throughout legal consultations, IP reviews and with the Ospo in general. So I think I would say overall it's really a cultural shift and shift of mindset to go from proprietary to open source first. And that will take some time, maybe not a year or two, but a longer period of time and the Ospo will be here along the way with our developers. Awesome, yeah. I think the next question I think the audience would like to know is, and this is difficult for Goldman Sachs and probably lots of other banks to share what they're working on and what they're working towards. But Priya, as the engineer in the team, maybe you can kind of give us some insights about what Goldman Sachs are working towards building for, you know, to improve their developer experience in the future for people using the Ospo. Yeah, sure. So I believe engineers make Ospo a better ecosystem. Gears as a firm, like if you want to contribute or open source anything from the firm device, it's just not a simple comment. You have to go through the compliance and regulations where they make sure that you are not putting any sensitive information out, information related to the SSN accounts, information related to the account numbers. You are not leaking any intellectual property in form of proprietary code, like trading algorithms. So engineers can help you to develop an infrastructure which can make sure that your product is healthy. It doesn't have any security flaws and it is not leaking any intellectual properties. I believe engineer can also help you with providing a lot of data metrics and dashboards, which can help you deciding your policies, your goals, your strategies. And data can also help you deciding your, like determining what your position in open source and retaining your resources and hiding new resources, which are open source enthusiast. I believe engineer can better understand the problems and difficulties any contributor is having and they can mitigate it and make the open source contribution part of their everyday life. Awesome. So, I mean, I think that's somewhat elliptical, but it does give us a feeling of what you guys are trying to build. Certainly, there's a huge scope for automation there, isn't there in terms of all of the bureaucracy around running an OSPO and trying to minimize that for your team, right? Because if you're going from hundreds of developers to thousands of developers, all contributing to open source, then you're definitely going to need lots of good tooling in order to try and stop that turning into a huge effort for the team and having to hire an even bigger OSPO group. And I think, yes, so one thing that Fianos does, and I'll just go to the next slide actually, so there's some links on the screen of things you can explore after this talk. But one thing Fianos does is we have their thing called the open source readiness forum, which Goldman Sachs are quite active members of. And yes, and also on here is the Goldman Sachs developer blog, which you can check out. Now, the idea of open source readiness is to really help financial organizations, members of Fianos, to get started in their OSPO journey and continue the sort of thing that you guys have been doing. And obviously getting everybody together at events like the monthly OSR SIG, special interest group meeting, means that you can all share ideas and information and learn, have sessions a bit like this where you're actually learning from each other. So that's super useful and I'm on behalf of Fianos, I'd like to thank Goldman Sachs for all the effort they put into the open source readiness SIG. Let's expand on that, right? Because talking to this group here, what would your advice be on starting an OSPO? Where would you go with that? Who wants to start? So kind of like building a product where we always do usability testing, my advice would be listen to your developers, talk to them, find out what the blockers are, what the pain points are, and prioritize those. Figure out what you want to focus on first, and then you will know who to staff and how to staff your team built from there and what goals you want for your first one to three years of OSPO. So I think that would be my best advice for anyone who's interested in building an open source team in the firm. My advice would be that your OSPO legal team should have the best partnership ever. I think working on projects and initiatives that we've accomplished, it wouldn't have been possible without the legal team total time and total commitment. Basically, we are one team, but that's my advice is to build a team where everyone is on the same page. Everyone understands who's responsible for what so things can be executed. One piece of advice I want to give is having genius. I will emphasize having genius because they can really automate your tools and build the tools which can increase developer efficiency. They can also impose open source security measures and they can connect workflow and firm policy in a very developer friendly manner. So have engineers, yeah? That's one of the key takeaways I think from Priya. Fantastic. All right, well listen, I'm going to throw it open to the audience now. Does anyone want to ask a question of our amazing OSPO people? I'm just curious as we're starting our own OSPO. How staffed are you? How many people are consistent with the OSPO at Goldman right now? I believe there's eight of us. Eight people? Thank you. Anyone else? Okay. You mentioned the involvement of legal. Do you have a dedicated legal person because you probably need a lot of time from them right in your team or do you just work with them and their team? Yeah, they're not actually like a part of like the OSPO team itself. They are an extension, but they are very well versed and knowledgeable about open source. So we're really grateful for that. We lean on them for a lot of advice and I would say they're very developer centric too. They spend a lot of time with their developers. Yes. Sorry, I'll just. So it was the question. Do you have any mainframes? I would say so. Shall I ask Kay if she knows what a mainframe is? Anyone else? Yeah. Yeah. Hi. I was wondering to what degree, I guess if any, is the OSPO engaged directly with open source communities outside of the firm as opposed to enabling people within the firm to work with them? I don't know. I don't know. I don't know what the community is directly. Can you speak a little bit about that? Sorry, can you repeat your question? I just wanted to. Yeah. So it's a question about engagement with external communities. And I'm wondering to what degree the OSPO itself directly engages with communities versus working with people at Goldman Sachs to engage themselves into the communities. Yeah, I think because our, you know, our hospital is fairly brand new, but we are really concentrated on being the bridge to our developers and really extending them again outside of the four walls that they work in. I think it's important for our developers to have personal growth and to work on projects that also we depend on as a firm. So we are very much in touch with that. And it's something that we are still trying to elevate as far as like our developers experience and really working closely with the foundations that we work with as well. I'll do this one first. So I was curious as to, you know, what was the tipping point at Goldman, where they kind of sat around and said, Well, we better form a program office around open source, right? At what point did it become so evident that, you know, the organization would hire people and start spending money in this way, right? What was that tipping point like? And maybe also what was the earliest advent of open source at Goldman? I had a little bit of experience there because I remember trying to implement source forage inside of Goldman. Yeah. Well, we want to hand this off to Rob, who's the leader of the OSPO, so he can kind of share. So repeat the question again. What's the impetus for us? I think it was a couple of things. I think the end impetus was the contribution of legend as well as the other work that we were doing, right? So we were starting to get and continue to get and you've heard some more of that today. There was more and more traction that's happening with the legend contribution. And then as my colleagues alluded to, we had the contributions before of GSQuant now of GSCollections, now EclipseCollections. We had about 18 to 20 discreet projects in our GitHub org. We just were getting to a point where, you know, as they were saying, we just having that be decentralized. It just didn't make much sense. And part of our overall engineering strategy is really to be developer focus and developer centric. And we really wanted to encourage our folks and our developers to be able to get a seat at the table, earn a seat at the table by authentically participating in open source communities. And we wanted a centralized way to really facilitate and organize that across the engineering division. And as we alluded to earlier, we use memos. That's a big part of our organizational culture. And so there was a lot of thought that Rohan and Bella, who unfortunately can't be here, put into really making that business case around how do we build developer centricity around enabling open source. There's also some key elements around developer attraction and developer retention that we felt were really important around enabling open source. I don't think it was either or. Again, as you know, Priya, Vicky and Kay have said, our compliance team, our tech risk team, our legal team, our executive office, all those folks have been really wonderful partners to us. So it's really been about enabling our developers and allowing our developers to all collectively work together and collaborate. And surely, as we all know by DIN of us being here at this conference, open source can be a key source of innovation and we wanted to be part of that innovation party, if you will, a lot of that's happening in open source. Can someone just let me know how long we've got left? Have we got time for another question? Seven minutes. Okay, we're good. Can you talk to me about some of the toolings that you guys built inside to manage this whole open source or the OSS office to help them out? Yeah, so we have a tool which integrates intellectual property review and it just systemized access of GitHub so that once any contributor get the access on any project, he can simply use the GitLab to push any code out. And then we also have dashboard and metrics for tracking and evaluating the growth, like what the percentage of growth we are having in active contributors month over month, week over week, and what the number of PRs and MRs raised by those contributors. Yeah, so these are for the project Goldman has approved for contributions. No, it's not. Yeah, it's internal tool. And why is that? Why is it an open source? Can we not? All right, anyone else got a question? Okay. I'm curious because this is really good citizenship, whether your statistics on your contributions to the open source community are rolling up into your ESG in any way, because that would be really cool if it did. Sorry, can you repeat that question? A lot of firms, you know, obviously they're reporting on different metrics for ESG for, you know, environmental, social and governance. And it seems like open source contribution is a form of great corporate citizenship. And it's also part of the governance of a firm, right? Obviously. And it would be really cool to see these statistics distilled and, you know, even reported up into like the ESG representations of a bank, because then we could start to look at, you know, all of the different firms and their contributions and perhaps encourage more of them. Yeah, so we have been focusing on gathering metrics from our open source contribution and consumption. And of course we have a lot of internal resources and reporting on that that we report to senior leadership. And one of our goals for next year is to better visualize that and then perhaps publish it to the public. Right now we do have this website on developer.gs.com where we published some of our metrics and all of the great things that we've been doing with open source. So if you go on there, you will see some of the data that we have published so far. We're also on the open source index where you can see our numbers of contribution. But next year for sure, one of our main goals would be to better provide and visualize those data. All right. I think we're going to have to leave it there. So can I have a really big round of applause for Vicki, Kay and Priya? Thanks very much, guys. That was lovely.