 Thank you so much everyone for attending. Today's talk is going to be about a deep dive into the Ospo five states model personas that for those who doesn't know it's part of a bigger study that to the group in collaboration with other research and also other organizations such as Comcast, Bloomberg and more released a few months ago and today's topic is to try to better understand all these stages and how can it help these resources in your Ospo journey. First of all also I would like to say that this talk is not for people that doesn't know why an Ospo and what is the value of an Ospo. If you're in that journey yet I really recommend to check like previous Ospo contracts and talks especially my previous keynote I gave because I can dive into like why an open source program of it is important what it's an Ospo and so on but in this talk everyone that is here is already aware that it is important to have a strategy on top of all the open source efforts and that adopting a strategy poster around open source is no longer optional. Okay so when people are already aware of that and is in that point there are some questions that comes to people's mind right so for instance where is the organization in terms of the open source involvement like what place of the journey is this organization also like how is my organization interacting with the open source ecosystem at this moment and or what kind of open source efforts so the organization be aware and prioritized in the first place and then in the long term and these questions can help to streamline this Ospo adoption and there are some tutor resources that can help to do this streamline to answer the where question the Ospo materiality model can help to answer the how question Ospo archetypes might be useful since it shows some kind of identifies patterns of the different Ospos on how Ospos can be built and the what questions maybe the Ospo main man can help you identify all the different responsibilities and try to identify which ones are the most important ones for your company based on the organization on your organization schools so we're gonna go one by one first is gonna be the Ospo maturity model so what is this basically a framework to understand the different maturity stages and this is based on the insights collected from past Ospo service we have been doing every single year and also testimonials for thousands of organizations that they have been as they have been moving through their open source journeys and you will see the model in a while but there will be they're gonna be the two variables so one the ability to execute of that organization and then the level of involvement in open source but before starting with that maybe some of you here will be thinking Ospo okay how do I know if my organization has an Ospo if it uses a different name because maybe we can I call the organizations that call it open source technology center or there's open source center or there's open source software committee you know there are really different ways to call the Ospo and Ospo and I think this can help to actually identify if your organization is doing some kind of Ospo work or not so if your organization when you you're thinking in your organization is applying open source strategy and policies good you're in the right path you your organization is being more mature and they understand that they need a strategic posture around open source and they're working to build a matrix of experts to communicate the the Ospo people with the rest of the teams in your organization if on the other hand your organization is doing open source at hug there are no coordinating efforts even though you're you're using open source and open source is part of your organization but there is no strategy and policies maybe you need to think about this adding a strategy on top of the open source efforts just start building what it's called an Ospo or different names but same same concept okay so let's continue with the Ospo model so the Ospo model defines this path from open source at hug to strategic decision making partners there is a initial states that is not really a stages like the zero states that is the adopting open source at hug there you can see like there is not Ospo level at the very beginning and then once the organization is aware of that moves to some legal driven states then to the community driven states to the engagement driven state and to the leadership and they how fast is this transition going depends on the ability of execute of the organization because some organizations might have really strong barriers industry barriers that doesn't allow them to go as fast as they can and others goes really well and it looks like oh and just one year I just develop a really amazing open source strategy and policies and your organization is aware of the open source efforts and and understands open source um so we're going to go states by states to try to identify uh like the main character like what characterize those stages and then um when uh it's when when that transition from the legal to the community the community to the engagement and engagement to the leadership happens also um also to let you know that this is not like isolated stages like once you cover the legal part you move to the community part while keeping all the efforts in the legal part so it's accumulative um stages so in the legal driven states um the organization already recognized that open source software is a key part of their business and the technology strategy and there are the tasks that usually follow is identify all the legal and security risk try to see ways of how to do risk mitigation strategies like for instance as I said there are like inventory taking developer education from the legal concepts and careful licensing um the next step uh moves more to a community driven state that has two phases so in that part uh your your organization is already have already policies around all the legal and security issues in place and um they allow them to start creating this internal ambassadors to promote the usage of open source products and approve open source products that deliver the team say yeah you're good to go this is the set of open source product you you're good to to contribute to so these ambassadors are promoting this community education and try to educate developers within the organization into open source um we're still in the community driven states but part two so as they keep learning and and having more knowledge of the open source and how open source benefits the organization uh the hospitals start to optimize all the open source contributions is that is the time when the out bone open source contributions are increased the quality and they are more meaningful because they actually know how to engage in the open source ecosystem and it's also sometimes with the Ospo create and launch open source projects and to start this broad credibility in the open source community and once the organization is educated into this part like community and legal education it's when we really put can can start to make actions and have an impact in open source ecosystems and it's when the engagement driven states start so it's when these leaders uh that has been being formed in the organizations starts to launch open source projects in the public sphere and um they understand that these projects are benefiting the organization so this is in this state there are a lot of let's create playbooks let's create checklist and tooling and uh other mechanisms that allows to organize and operate in open source projects like open source uh best best practices and also ways to keep training these leaders that will fuel the organization with and will act as the link between the organization efforts and the open source ecosystem and finally uh if the organization uh it's able to have all this is when we can start talking about a leadership driven state so it's when this Ospo can become this advisor of the organization and drive guidance uh for instance advise the CDO and the uh technology leadership on what open source technologies are the best ones to use or um uh see what is decide what constitutes an acceptable open source project or interested open source project for the organizations to contribute and to participate and also to help organizations understand and navigate project politics so um we have now covered the where like a way to know better like where is my organization at in the Ospo journey now let's move to um how uh to how how how is my Ospo operating in the open source ecosystem because their Ospos are so different and there are many ways they can behave so we can identify patterns um that uh we can relate our organization with those patterns uh to help better understand what what my Ospo is for um also I have to say that an Ospo might have different hats and um we're gonna see like a some some sort of different um archetypes here I'm not gonna cover all of them because there are like six we're gonna cover like just three examples but uh once I go through all these um archetypes maybe you might say oh my Ospo does all of them like I can relate to all of those or maybe another person say well my Ospo I can relate to with two of them instead uh because that is what the patterns are it's tried to identify patterns and that is what your Ospo is so let's let's put examples I think it's gonna be better um so one Ospo archetype um for instance this happens a lot in the automotive companies from the European Union um can see open source as a way to improve uh to make better uh all the industry infrastructure for them so they built an open source consumption uh to contribute to key open source initiatives uh that it's that benefits the industry as a whole like for instance in this case the automotive industry uh but there are all the kinds of Ospo's that sees value in um okay I want to um better create tooling that could automate uh deconsumption and thus uh have better contributions and contribute better to their community so for instance this is an example uh that Bloomberg worked with Microsoft to make contributions to TypeScript so this was like create better a better tooling to help them contribute back in a more efficient way so these are sorry these are called the cross industry collaborative and the other ones were called the industry collaborative um and then another example and I think that this is a common one is um this Ospo's um that are trying to facilitate this incubation of open source projects within the organization and then launch them so for instance Comcast uh incubated the Apache traffic control project and that is another example for instance and as I was mentioning there are several ones you can try to find out your Ospo personas I uh added there the dvpog where you can take a deep dive on all the different archives and also to say so these archives are really corporate focused um but they are not an a closed list so this can be wider and wider and there are maybe other organizations can add value and find other patterns and add more archives to the list so other component other Ospo's when looking at this looking at these archetypes can relate to themselves right so finally um let's now move to what so uh what are the different Ospo responsibilities uh that a call an Ospo can accomplish and uh and how can I know which ones are the best ones to focus at uh depending on uh in based based on my organization's goals so uh there's another resource at the uh to the group that is the Ospo mind map in fact like one month ago we just released the uh second the 2.0 version of this mind map so it has improved a lot with a lot of uh contributions for the community and from season it as far as as well so thank you so much um I know some people from the to the group community here um that are helping to grow this community and I just want to say that I'm really grateful to be part of this because I see so many efforts and so many um yeah um excitement excitement to build this uh Ospo adoption and help other Ospo's to grow so as I was saying the Ospo mind map can help to frame these Ospo responsibilities so uh these are the set of different responsibilities that we can find in an Ospo some Ospo's are more are smaller than others some Ospo's are just starting and other Ospo's have a really big team so uh the amount of responsibilities the Ospo can take depends on the size of the Ospo and where is the Ospo located and and the uh and the journey and and and and the states where the Ospo is uh some of the responsibilities for instance in our source like I know some organizations uh has inner source outside the Ospo but we're still we're seeing more and more organizations having implemented inner source practices and have it there as an Ospo responsibility in order to infuse the organization with open source knowledge on the different uh teams for instance also in the Ospo mind map uh you can see the different roles that an Ospo can have because Ospo is not just like a team with the same people and trying to do open source I mean no like Ospo's will be the center that can communicate with the different departments and the different teams of an organization and because of that because it's so diverse and has a lot of different domain knowledge from different expertise they need to build a matrix of experts so take the time if you're building an Ospo or willing to build an Ospo take the time to build this matrix of experts in licensing in security in marketing in developer education in engineering uh to uh is this communication across teams to talk the same language of the different teams um to end up with I would like to serve some key learnings uh this this learnings comes from um the past panel discussion we had at the linux foundation uh two weeks ago where ports come cast uh bloom birth well and v and were were talking about the value of the Ospo's and I think it's uh I took like some learnings from there and I wanted to serve with you so the first one it's I think I mentioned at the very beginning uh starting an open source program office uh means moving from uh doing accidental um taking accidental decisions in terms of open source like oh there is a vulnerability here so I need to take care of this open source but you're not thinking far away from that so from that for to adopt a strategic posture around open source it's put a strategy and that's accelerate this open source and the innovation um second um build your matrix of experts so make sure you're infusing the organization with a clear understanding of open source because that is going to be the baseline to actually take actions and start uh having engagement with the open source community because sometimes there are a lot of problems that I've heard in the to the growth from from organizations saying uh it's so difficult to make my employees contribute at bound in a with quality in quality with quality contributions at that usually is because this education of the open source hasn't come yet but it takes time and uh finally um some of the hospitals mentioned that it's really important for them to um lead by example uh because if uh their hospitals if the organizations see that that hospital is engaging uh with open source and the employees are contributing to open source are releasing open source uh that builds makes them believe on that and so lead by example as a best practice of when building the hospital I think it's a really important uh topic to take into consideration um once you figure out uh like where is your hospital is how to engage uh in the hospital system and what are the responsibilities uh you should be taking care of I really um encourage you to take a look to the to the guides that explains how to start the hospital and uh deep dive into these processes and more resources that you can find at to the group.org slash guides also if you would like to collaborate if you're an hospital willing to collaborate with this community and building more resources to help hospital adoption and education worldwide uh please say hi to slack or on slack or get up and uh follow us on twitter on linkedin for more updates and finally something about me um I'm Anna Jimenez currently the hospital program manager at to the group uh formerly I I was at viteria where I spent more than three years helping organizations in their inner source and open source metrics uh strategy um finally I uh end up my master's degree in data science and I'm involved in all the open source communities such as chaos several collective several Spain open chain and um of course uh inner source and of course to the group thank you so much do we have time for questions yep okay are there any questions hello uh the first thing that I have to say uh the guides from the to do group are really awesome two years ago we were doing open source but we didn't know that so we started a journey to to establish an open source at Comet uh this is the best part where if if anyone is interested to establish an an ospo you should start there so thanks for that guys and in the first place do you think that innovation is an ospo responsibility so what do you mean by innovation learning innovation processes yeah so the way I see so open source drives innovation and I think uh if you've been able attending to the talks here uh I think that it's a phrase that has been in every single place so um the way I see it is ospo since you are putting a strategy on the on the open source efforts you're accelerating the open source adoption in your organization and since you're accelerating this open source adoption you're at some point accelerating innovation so I don't know if that was the question or my question is focus and in another part because at Comet we have to split both both concepts because we were losing the focus on open source we were just trying to run innovation process try to think what we should do instead of trying to give it back to the community oh yeah yeah I could do yeah so uh establishing an ospo I'm gonna go back to the slides really quick okay uh it's a way to take conscious of open source and not just like how can we drive innovation no it's about uh starting to be a good open source citizen and how to engage with the community because open source is a community of communities and sometimes uh that it's difficult for an organization that doesn't know anything about open source because the way they interact is completely different uh if you want to have some um presence in a in a community and in a project you can not you can just you cannot just uh oh let's pay developers and um let's take the project like you cannot do that in open source so it's really important uh to um the ospo can infuse the organization of this uh how to be an open so a good open source citizen how to um how to how to participate in open source communities so at that point of course I think it can accelerate this innovation and and how to um how to in uh evolve and and be part of the open source community okay thank you um okay thank you how much do you think um the you know I know for a follow's function into some of the advice in here seems to say indicate not get caught up in whether it's an ospo or resource center or whatever um you know part of my organization and a lot of other organizations have adopted with the scaled agile kind of Spotify and they have all kinds of fancy terms for things like tribe squads chapters guilds and whatnot um in an organization that maybe potentially has is moving away from the notion of a program office or has an aversion to the term program office right have you seen any um organizations kind of fitting it into the chapter tribe squad model or something along those lines so uh can you give an example of what it's like a squad model uh it's just the scaled agile agile at scale okay right so they move away from kind of individual certain it's just a fancy new thing where and I believe in it and when you actually go through the training it certainly makes sense of just pushing power to the edges giving product teams and teams built around features a little bit more autonomy right um but um I guess the the idea that um you know tribes and squads around organize around features and instead of the traditional kind of functional mapping that they have now this notion of chapters and guilds right communities of practice communities of interest or just kind of you know where the the the functional alignments are so I'm not an agile expert so sorry about that but um I know like there are ospos that are doing agile and they're implementing um agile best practices within the ospo that's all I can say um you can also I think that that is an interesting question and uh in the community in this black channel and ospo forum that is something that maybe you can ask and other ospos will be more than happy to to discuss about this thank you I'll take it up in there hi thanks for the talk it was really great um I was wondering so with your experience with open source and with inner source um can you talk about any migrations you've had to do from inner source into the open source setting and how what the experience is like um so when I was in my former company I held organizations that had inner source and open like my organization didn't have inner source and ospos but we were helping organizations with that uh so based on my experience I've seen so many different profiles like I've seen organizations starting with an inner source and then from that um they use inner sources as a way to uh develop to educate developers internally and once they got that they say let's build an ospo let's go to open source um as a way to help them uh other organizations they just say let's do inner source and open source at the same time because um it makes sense like we see inner source as a way to educate developers and the ospo must be the ones in charge of educated developers so it has many phases to be honest but it's true that now that ospo is having like this momentum and and having like like this keyword it's it's um in the top of mind of many people there uh I'm seeing organizations say let's let's merge it together or at least collaborate together even though it's some different teams thank you very much but really quick then too just to kind of add on to what joe is asking too so actually having an inner source project like a single standalone inner source project and then moving it out into the open have you had any experience with that and any like key lessons learned about that um I will say that um I don't I guess you're aware of the inner source commons community of course uh they have great resources on that and they're also like some um I see people from the to the group also engaging in inner source commons because uh and most of the community are like the same people um so either you asking the to the group or in the inner source I'm sure they have good experience to start there so the talks I've been to and looking at the list of case studies are all large companies we're 100 people the developers are we use open source in our product individually we're giving back when we can but do you have any examples or or resources for smaller companies and getting something in place that that helps the company be more obviously part of the community um let me give you some quick context of that because the cases study so Osprey has been there for more than a decade right now and initially started with big software companies so that's why like when you take a look of the Osprey use cases most of them are like huge companies what it's happening what has been happening over the past two years or so is that Osprey's are being formed also in the small organizations and in medium ones as well actually well I'm from Europe I'm from Madrid Spain and in Europe we don't have so many big organizations like most of the organizations are small and medium and they are they are creating Ospes we don't have like we haven't created Osprey use case for small organizations yet but there I know I know they are there like they're interacting in the community and they're asking questions maybe they don't have these resources to promote like hey we have an Ospo and look how cool we are they are like go they're going step by step and maybe they are taking more way in the legal side so that's why they don't have it they don't ruin a lot of impact I wanted to mention uh this is not a small company like it's more medium one but um there is one company that started the Ospo one year ago that is called Avian have you ever heard about them so they're like they're a medium company they they have an Ospo like not not so many people are in the Ospo but they are there they are doing incredible work in just one year so yeah I just said Pratt so um I will say it um to learn more about experiences I really recommend to engage with the community and I know I'm I'm always telling that you this but it's um I know that is what works like uh being in the in the channel being in the network in the spaces and the calls and engage with these people and and share learnings together is what actually will let you know that okay um first of all thanks thanks for the presentation um if I record correctly the Ospo archetypes are a set of um patterns so I'm just wondering if you have also developed anti-patterns things like the companies shouldn't do like or perform or things like that um actually we don't have it uh but as I said this is the archetype is something that started this year um and it's pretty new uh we want to open contributions for that like this kind of ideas will be really useful for instance so we welcome the community to contribute to that and to expand this this vision because this this is a really reduced vision as I said these archetypes uh are corporate archetypes only right now we would like to spend this and maybe with adding the archetype like this is what you shouldn't do um so yeah thanks for the feedback and the advice um later today there's actually a talk called Ospo's you're doing it wrong which is sort of like anti-patterns and the person who's doing that is van Lindberg and he used to be counsel for the python software foundation and uh partner at like but anyway he's also started something to your question gentlemen in the purple suit who's texting you um the Ospo is a service Ospo co I don't know if you've looked at that at all but for a smaller company that's a really awesome way to have uh resource anyway two plugs for van wow I should go collect money from him thank you any other questions okay so I think we can we can end the talk um and the q and a thank you so much