 Thank you so much for attending to my talk, today I'll be talking about an important topic that has been around at least in the community during this year that is sustainability and how OSPUS can become or are becoming a key lever for open source sustainability. But before they've been diving to the topic, since this is OSPACON brought you back to the group, I'd like to serve some OSPAN news and announcements first. I'll be really, really quick and then we will get into ways organizations are right now addressing open source sustainability, the role of OSPUS in supporting open source sustainability. And at the end of the talk, I'd like to serve some of the community learnings that has been serving in this community and if we have time for Q&A and open discussions on this topic. So Nithya was already mentioning that, but every year we do the open source program office and the status of OSPUS, and this year we are launching the 2023 edition in partnership with great organizations and open source communities. So thank you, thank you so much. So the survey is already live. If you go to 2dgroup.org and in the blog section, you will see an article that people can click on it and take the survey and feel free to serve it with all the organizations that are working on open source initiatives or OSPUS. So the 2dgroup has been hosting a rep or a public rep that has an OSPUS definition since 2020, as far as I know. And we are making a new release updating that definition because Nithya was also mentioning like OSPUS has been evolving so much during the past year that the definition might need to be now like to be updated to be more inclusive and according to the reality that we are facing right now. So this is a call for contributors because everyone is welcome to participate in this community and to contribute to the different projects and initiatives that is going on. So if you're interested there is also another blog article where you can find more information on how to serve your input and your experience to help to define the new OSPUS definition. We are starting an ambassador program in Toodoo and that is really, really exciting. It's something that the 2dgroup committee together with the broader community has been working on. And we are right now open to a call for ambassadors. So if you are participating in the community and engaging in OSPUS or are an OSPUS practitioner feel free to take a look to the guidelines and requirements and responsibilities to become an ambassador of the 2dgroup and OSPUS ambassador. And last but not least this year a group of open source folks from different organizations, foundations, open source communities kick off a new working group and a new initiative in OSPOLOGY that is the broader community that is called there is a book project. So Toodoo has been doing great job on gathering guidelines and knowledge and so on. But there are outside and even within the 2dgroup and outside in all the OSPUS communities great sources. So what we are trying to do here is to build a body of knowledge that gathers all the different perspectives and all the different work that all the communities have been doing. And I think we are like right now very contributors actively engaging in conversations and contributing to the content of this book. And it's a work in progress so if you would like to join also all the documentation in the link. And you have there a QR that links to the Slack channel of the 2dgroup. So if you are not part of the Slack channel I really welcome you to join. We have different working areas so we have the working groups that are the people behind the Toodoo guides working on the Toodoo guides or the OSPOLOG project. Like doing more like the CERN knowledge stuff. We also have local groups like we have the Japanese OSPOLOG community group. We have also like a Netherlands group in Europe. We do also have one in Switzerland. So these are local communities that usually they feel comfortable talking in their native speaking language. Most of them like for instance the one in Switzerland is happening in French in the Netherlands and that's in Japan is in Japanese that got us together to talk about specific issues and problems and came up with CERN solutions for OSPOLOG in that specific country or area or region. So we do also have these local groups and finally we also have network and discussions groups. So this is not more this is something to mix it with working groups like in those discussion groups sometimes there we did there is a new working group that raises like there is a specific need and then the people put gathers together to create a working group to work like for instance so this is what happened with the Outbone open source guide from the to the European chapter they decided to okay this is a need an email organization we have this kind of policies and guidelines and in other organizations they have different ones so why not collaborating together why not open this to the public and serve it so everyone can find inspiration on how different organizations that had an OSPOL did and this is one of the outputs that came from those discussions which I think is great and sometimes there are not outputs sometimes it's just I really want to hang out with peers and and serve my experiences and learn from others which is also great so as I said feel free to scan the QR if you would like to to join the group and there are other other resources out there so we have an open source program office 101 course that course is completely free it's in one of the two to GitHub repos and has different modules on the basic of an OSPOL so if you would like to get it started into us but that can be a good place to at least start and you can also continue with into the group we have the to the guides on different topics on how to get started with the Ospo and continue the Ospo and one of the latest works we did was the business value of the Ospo to try to analyze and explore why organizations were creating sustain and also expanding the open source program offices that is one of the books out there so saying that let's now come back to the topic and to start with I would like to talk about a specific question that was raised yesterday during the Ospo Consummit so Ospo not Ospo Consummit sorry Chaos Consummit so Chaos is another LF project focusing on community analytics health and analyzing the health of the open source communities and the open source projects and we got a really insightful conversation on what does sustainability means to you and also is it different or similar to health and all this came up with the question on okay it looks like many organizations knows or understands the value of why taking care of open source because they are using open source but there might be some organizations that they just stuck into that step and doesn't take care of the contributions so even though open sources said we were and there was a statement that said that the world is built on software and open source is eating some software or something like that and I know like many organizations actually understands that the next step is okay and what about contributing to open source projects because that might be maybe the next questions to ask like does open source contribution scale on the same level as open source usage like I know organizations care about open source because they are using open source but do they care about contributing to open source and that's why the reason of why I submitted this talk and wanted to talk with you and to discuss with you the open source sustainability and how it was can help so to start with let's start dipping dive more into what sustainability means and addressing open source sustainability so when looking in the on the internet on Wikipedia on not different sources there are different ways to define sustainability but I found a really interesting graph that was more related with more like environmental stuff but that I think that can be also applied into open source so they define it to sustain sustainability with three pilars that sustain the sustainability concept oh my god yeah so they they put like environmental pilot economic pilot and social pilot so when I look at that I was like that it's really similar to open source and let me get that straight so when I hear environment I can also understand open source projects when I see social I see open source community and when I see economic I see goals and business so more like for the organization is it making impact for the organization and maybe and this is just my perception maybe we can take this three pilars and think about how can we improve each of those areas to actually talk about and addressing open source sustainability because in in my honest opinion I think like the economic goal for organizations is pretty clear right like okay I know we are using open source and I know like open source can help in my business I don't know how that's why I maybe hire the Ospo but I know like or I want to see profit and and and help my goals to succeed but sometimes they just don't forget about the environmental part like the like okay and how are my open source how are the open source projects I engage with operating and evolving and engaging and what about the open source community because that is also part of what makes something sustainable so right now organizations are doing different activities different initiatives even though they have an Ospo or not to try to help on addressing sustainability the most direct thought that you might think of its funding providing finding there has been great initiatives some examples Spotify Foss Fund released last year the Indeed Ospo in the past lead by Dwayne O'Brien also did the Foss contributor fund that was inspiration for many other organizations including for instance the Spotify Foss Funds and they also have a book that serves more details on why creating the Foss Funds and the details on how to implementing in that organization Bloomberg Alisa is here as well recently released the Bloomberg the Ospo team released the Bloomberg Foss contributor fund a few months ago or I think these months is when that happened and there are also other initiatives outside the organizations like for instance github sponsors that as far as you know all the organizations with Ospo are using to with the aim to provide funding to maintainers independent projects and the open source projects that needs it also I wanted to do a sort out to the maintainer month that is happening this month now that we were talking about funding and how organizations can have also there are other ways so for instance providing contributions and infrastructure that usually people think on yeah funding if I am organization funding it's the direct way to do it but you can also teach employees on how to contribute to open source and also to provide infrastructure to those open source projects that your organization is engaging with this comes from the last Ospo survey that was I thought it was really interesting that says that 65 percent organizations that contributes upstream open source formally structure the Ospo and I think that is really interesting because we will say it in a while but Ospo usually is just a way to is the vehicle to streamline open source operations doesn't it's not that if you don't have an Ospo you don't care about open source but it can help to put order into chaos a third thing that organizations are also doing is adopting open source best practices it's not just about yeah let's contribute sometimes employees within organization doesn't know how to contribute to open source or maybe they need some legal advice and also operational and how to operate within open source dynamics and specific tooling and automation processes to make their lives much easier so organizations are helping with that putting policies and processes to ease that contribution and to understand the open source culture so I think it's also really very important to not just say you need to contribute but contribute in a way that doesn't harm the open source ecosystem that benefits both the organization but also the open source projects and the ecosystem itself so talking about when we see all these different ways organizations can have and address open source sustainability here is a typical problem we face so the open source ecosystem it's really wide thing and there are different actors open source actors outside the organization so we have maintainers we have independent projects and well umbrella projects that are part of foundations we have also contributors we and so on so it's it's open source player is really different and they have their different ways to operate and different communications channels you can get in contact with those people so what do we do what can an organization do and also can happen that so the also can be this entity or group of people because also it's behind the hospital there are people that puts order puts yeah put all the chaos into order yeah and and cleans up all the mess so I think that it's also really important and can connect all the open source projects with the organization and vice versa and get the feedback from the open source community and serve with the organization so that their needs and their questions and their concerns and problems gets also heard in the organization so now that we're talking about open source program offices as a way that might help addressing this open source sustainability I think it's important to understand the Ospo and what an Ospo is but before that so important consideration so we here we are talking about Ospo and looks like yeah this is it this is the final definition and everyone should do it this way it's not and into the group we always said your Ospo is not my Ospo so they might be right in sector in region organizational side and there are people there are Ospos that they don't call it an Ospo they call it open source office or open source strategy center and it's I mean it's the same even though the world is different the goal is going to be the same to manage open source operations and strategy we saw well in in nithya and past nithya presentation we already saw like what is an Ospo as an entity so I'm not going to dive into that in today's talk I wanted to go to see a different perspective and is who is in the Ospo like what is the people what kind of people are behind in an Ospo either virtual or physical either is not officially formed but at some point they're operating like that because I think it's important to also address like what the people behind the Ospo can do in your organization so we have the enabler so these are about and when organization decides to put strategy and streamline this open source operation it needs education it needs a person or a group of people to work on how to establish processes to have to operate in open source and and include workflows and also adopt new tools and technologies that is this contributions we also have the consular and that is related to the metrics of experts I was later serving in the q&a session so it's more about how how these people can solve the problems on the different teams so it's about providing guidance and advice on where are the ladies opens our strengths what happens with this project and there's and their licenses so like is it safe for me to contribute to that is it not so they actually act as these people at this guide to help organizations to advance in the open source journey there are also advocates and I'm seeing more diverse so I came from their background by the way it's there as well so I've seen more and more open source diverse that they work within the hospital because that is also really important task within the hospital to promote the usage and also to encourage the developers and also non-developers depending on the organization to engage in open source projects and also understand their needs like okay why why so these people wanted to contribute to open source or motivate them and and give them these motivations to engage in open source projects and also and I like a lot this little this last role will be the environmentalists so addressing security issues also maintenance taking care of the maintenance of the open source projects understanding how well these open source are and saying the health of those open source projects that can give us some ideas on this sustain and how these open source projects are sustainable and so on so this is all about establishing policies and procedures for core review security vulnerability tax ongoing maintenance and so on and and maybe also like some analysis on what open source projects to fund and what are the best ways to to provide that funding to those open source projects and maintainers that made it so okay we've been talking a lot about auspice but actually where do open source and auspice converge and and that is I ask this question because sometimes it's difficult for organizations to actually understand because even when the organization realize that they they need to do something with open source there might be not ready to start an auspice and that's totally fine I think it's more important to start asking previous questions first and know what is the status of your open source within the organization and once you know all that you might think of okay let's put a a team or a dedicated group of people to work on that to work on on on open source because organizations might have you know might be on different stages in their auspice in the open source journey and that is gonna also be the starting point on how to start the auspice and how the auspice will be structured that's it will it be lending to engineering to marketing or to legal which that also is gonna let you understand where so be the auspice and how so be the auspice structure so here are some assessment guidelines that in the for instance in the auspice book we were discussing a lot that can help you to to get us started to first evaluate the culture with your organization so it is the organization ready to open source operations there are like for instance the technology big tech companies might say yes I mean we have been using open source forever my employees knows how to operate in open source but maybe there are for instance in in Europe I've seen more and more organizations getting into open source while there doesn't have enough tools and culture to start with open source so maybe that might be the starting point to to ask like okay is there a culture of collaboration and sharing in the first place in my organization is it too traditional or is it actually getting ready to to operate in open source I wanted to do also sought out to in case you want to dive more into this topic of the inner source commons communities that actually works on that is a community to work on open source culture within the organizations not going fully open source but to start to to think about the how to implement this culture within their organizations and the different teams so they have the inner source patterns which are a set of guidelines to to get us started and you can go to their page to to learn more about the other question it's about knowledge and understanding so that's my organizations understand open source and what about on the different teams also the how how what is the level of open source usage like nithya was for instance saying well in an amazon in between 80 90 percent of the code we're we developed has open source components so well I think it's important and also in your organization try to understand that like what is the level of usage and what open source products do you rely on do you depend on until some processes so are there processes in place to to ease these contributions because you might be motivating your developers and non-developers a lot on yes you need to contribute to open source and this is how this is how open source can have you in your career and your whatever but if there are if if there's a lot of procedures in your organizations and bureaucracy maybe you kill that contributions even though people there are persons that really want to contribute to open source they cannot do that in your organizations that is not good so how can and in the hospital how can these people ease employees to contribute to open source so in and also it's about addressing the gap so to adopt open source and to advance in the open source journey what is this needed and what problems does my organization have and what solutions can it provide what support can this hospital do to into the different teams of the organizations that engage in open source and also even though you think that an hospital might be a tedious thing to implement and probably during the first months years you might not see like direct output impact in the organization in the long term is going to trip and I think this graph it's really a sad start like when organizations start to just put patches into okay we got an open source vulnerable we got a vulnerability from an open source project how can we fix it okay it's fix it okay yeah that's forget about open source that's that's cool you might not scale but if you start to think about including a strategy around open source and taking care of the open source operations with the team or a group of people or a matrix of experts there might be in the long term see the value of of investing on that and we have been talking about like how how an hospital or how organizations can engage in open source but sometimes that's some sometimes we forget about the anti patterns that organizations might start when they hear the word hospital and even like today for instance this year that I see a lot of organizations saying let's start at the hospital because everyone is doing that so why won't we do that and I think it's important for those organizations that are thinking about starting an hospital or are already starting an hospital to look at the anti patterns things that an hospital shouldn't be doing because it's it will harm the open source ecosystem and it might cause the organizations to don't want to continue the hospital program so for instance there are some examples like establishing an hospital without proper alignment within organizational schools you the hospital shouldn't be acting as silo the hospital should be talking with the different teams understand their needs understand the problems and try to say well how as an hospital can solve the problems of those of those of for instance the business team through open source also treating an hospital as a legal or compliance functionality so that is great risk mitigation is important but it's not the only thing and if we can if hospitals get stuck in that they are missing the important part of innovation on well open source is not just about taking care of if I'm using open source how can mitigate risk it's about I need to come like how the organizations can contribute to that who to help also their businesses and also their goals and help the different teams to treat and also believing that the hospital gives solution in the long term so this is a long term commitment this is an investment that might that will take forever or at least that is the the point of everything so open source is here to stay so an hospital should be here to stay as well the same way not handling correcting open source harms the open source environment is the same as if you don't handle correctly the hospital so to end up with I'm going to check if I we're already on time okay yeah we're still having time I also wanted to serve a set of community learnings and best practices that has been served in the Tudor community in the shape of discussions community discussions and also in the hospital discussions in the GitHub repo happening and so on so the first is assess open source readiness when starting the hospital asking these questions can be a good starting point for instance like what does open source mean for the organization and is there an open source culture within the organization in the first place and where are the key legal and compliance consideration of using open source software within the organization once you have addressed open source readiness you might also want to think about assess hospital readiness okay so an hospital at the beginning is an investment like you need to put money in that so what are the challenges and opportunities of implementing an hospital within the organization and what resources and support will be needed to implement that hospital and that is really important because that is what if for instance you are the hospital leader or an organization hires you as an open source leader in the organization you need to know these questions really well the answers to these questions really well to transmit and communicate what resources do you need and why and and the support that will be needed to grow the hospital in the first months or years also focus on third knowledge the as I mentioned earlier the hospital student act as a silo but it's something it's an ally a supporter that communicates and engage into the different teams so for instance the hospital or the people behind the hospital so be communicating with the executives and the and the stakeholders and understand like okay how can I provide value and where are their needs what does my supervision expect expect also if you have a team behind like below so what's my team doing and also there might be other teams like for instance if your hospital is an engineering and you need to communicate with the security team with the legal team does the other teams understand the message of open source how those teams see open source and how and how can I say I find them value and communicate all that and all this will be inside the organization but of course these are knowledge will also happen outside so how can we communicate with the different open source actors what is the matter of it of integration that serves the organization that connects the organization and the open source actors into different ways and I also wanted to point out and I'm very involved in chaos community so that's why I said a lot of what I've learned from chaos one of the discussions we serve regarding this knowledge like how can we communicate with different teams we we talk about that about well sometimes it's hard to communicate because of the language used is super different you cannot talk the same way you talk to engineering teams and the same way you talk with marketing team because the needs are different the wording is different but data data is a lot it's a global language so of course it's not just about focusing on data and quantitative data it's also qualitative information is super important but it can help and we've seen there was a discussion where we saw that some auspices are starting to include data scientist role that works on data gene open source analysis and open source data engineering so I think that's really cool and four look at sustainability from all angles so remember the first slide that I said of the sustainability and the pillars so I think that is also important to sharing the organization that is not just about I mean of course it's important to be aligned with the organization's goals that is super important but also take care of the other two angles that is the open source communities and the open source projects so to end up with some takeaways so we've seen that auspices are responsible for representing the organization and connecting the organization with the open source ecosystem so maybe a good questions to ask if you right now have the Ospo an Ospo or are part of an Ospo is well at this point at this moment does the open source actors know who to contact in my organization also foster self-discovery so it's in this way I wanted to explain more so it's more open assess open source to identify the the areas where there are problems and the different teams and use open source and let the Ospo people to work on those problems to find solutions so we were I remember Nithya were talking about the like Ospo sometimes are considered cost centers and really focus more on an added value I've seen also that kind of discussion like for instance the the recent layoffs that has been happening in organizations and Ospo's I've seen of course we cannot drive into conclusions with that like I'm going to say this is because of that but from past conversations what I've seen is that there are sometimes Ospo's are seen as an added value of the organization and when there are restrictions and we are in our there is a recession period all these added values are the first thing that goes out so why not start in thinking on Ospo's as a support a like like actually a team or a group of people that actually supports and gives support to the different teams so just something to think about finally remember about this knowledge don't act as a silo but find ways to communicate and transmit the value of open source and speak the language on the different teams to teach them that open source is important not only for using but also to contributing to open source we are done but I also wanted to reserve some time to introduce myself I'm Anna Jimenez I'm Ospo program manager at Cheetah Group previously I was in a company called Vitergia that is a software development analytics firm and in there is where I got a lot in contact with other Ospo's and also with organizations doing inner source in the part of the metrics and analytics right now I'm in the Cheetah Group I finished my masters in data science a few years ago now and apart from to do I'm also involved in other open source communities such as Chaos, Open Chain, DevRel Collective or Inner Source Commons and there is my master done account in case you want to follow me and connect and that's all I don't know if we have time for Q&A yeah so if Q&A or open discussion feel free to to share your thoughts I would love to to know like what do you think on open source sustainability what do you think on the world of Ospo's there based on your personal experience or would you have hair from other people so yeah yes I could have disagreed and I imagine you would also but then they asked okay but what is an Ospo going to do in 10 years from now the organization knows everything about open source what are the tasks of the Ospo in 10 years yeah and do you have any thoughts on that that is indeed a really interesting question I think since Ospo it's a dynamic environment the statement that usually make on well open source we reach to a maturity level and then open source is not going to change I think that is not completely right since like open source is going to be evolving from one year to the other year even in between months so assuming making that assumption that yeah that's on and that's all I don't think that's right and I think it's important the organizations understands that that open source is a dynamic environment and if you see the Ospo as this support team that has the different teams to navigate open source politics and open open source processes and and trends and advice on that you should need it in in the long term and I would say like in forever like you don't get rid of an engineering team so you shouldn't get rid of an Ospo any other questions or comments any other questions yeah okay so thank you so much for saying until the end