Open Source Program Offices (OSPO) and their role in OSS ecosystems
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Lopez, Manrique
Open source is becoming the main ingredient for companies to success. To achieve it, companies need to manage efficiently their relationship with open source projects. And that’s the main goal for companies’ Open Source Program Office (OSPO). So, they are key for companies success. But, additionally, they could be very important for open source projects sustainability. During this talk, you will learn about the responsibilities and benefits of having an OSPO in your organization, why should companies adapt to open source and adopt an OSPO, how it makes a difference to have a team responsible for viewing, managing, making critical decisions, contributions back to open source projects, and providing oversight for open source initiatives on their company and where they should start. Also, we will give real examples of how companies are doing this today and their impact for the community. Additionally, you will learn about communities and initiatives to help you having a successful OSPO, like OpenChain Project, TODO Group and CHAOSS, the importance of CHAOSS to give actual data and insights about open source projects and a bigger perspective with analytics and how data and metrics from the OSPO can help companies tackle their corporate strategy.
 Okay, good afternoon everybody. I think you are seeing this probably in the afternoon in Port Fosden. That sign says the code, you can see whatever you want. Thank you very much for joining us today in this online conference that we used to be all together in Brussels. We are going to miss the waffles a lot. I will probably cook a song of them for later. My talk today I would like to talk about open source, I don't know if you have heard about this concept but I will also talk about other topics. I am going to minimize myself in the video so you don't need to see me that big anymore. I would like to focus on at least four key topics. The people that we do develop, maintain, contribute to open source at some point. I will talk of organizations, open source ecosystems. I think it is a concept I would like to highlight during this talk. Also about open source pro-anophysis, the important role to help sustainability. One of the key points here about this, how to help on sustainability, is the way of the maintainer. So let's start. The motivation for this talk started like, I think it was a couple of months ago, I was preparing a talk for OpenCore Summit and I was analyzing, I work in Vitergia, we provide analytics about open source development and how companies develop software in general. But I was analyzing the commercial open source software company index. I don't know if you know about this but basically like 45, 50 software companies, companies that develop software and they say it will provide it as a service. These are the companies that have like $100 million revenue per year at least. So that's very amount of money, so that's significant amount of money. That means that you can do money doing open source software development and even providing service on top of that. So those companies are around in total like 70,000 employees and the numbers from these indexes are generating revenue around $80 billion per year in revenue. So that's in total for these 45, 50 companies, that's huge I would say. But okay, going to what were the people that are maintaining this code, how much active they are, what's the level of dependency these companies have on the maintainers. It was interesting to say, okay, these are the top 50 and you can compare that there is like a people that is doing a lot of identities or identities I would say that are doing all this amazing work on top of everything that are mostly bots actually. They are bots, but, but, but there is one human there and you see the amount of work this person has done is above any average of the rest of the project. So compared to around again 50 companies and these are people that are getting more than 100 or even more millions of dollars in revenue. So they are depending on probably the work of this person that I would say don't bother him on Thursday. I know it's him because I know him also who is the company and the working on but it's not the matter of the of the conference for me was the key point. Open source is depending that much in and this company is depending that much in the in the work of a person that okay companies software development at the end of the day is out people and that's that's very important and actually if we look at how software is developing in general we have development activities like writing code we have also deployment like we have more nowadays automatic ways to deploy things but at the end of the day you have some people involved there also and maintenance like people checking issues solving issues reporting, bad sets all this stuff also done by people but also in all these steps you need some kind of collaboration in one sense of the other of course in open source it's one of the key points for developing open source at all. So again people from my point of view and I think also Toby said this last year in also in the community there from here is said that people are the limited resources in software development ecosystem not only in open source but in software development ecosystem in general. So we if we are managers in a company or we as community members or we as companies that are willing to keep developing software we should be aware of the people we are involved with or we are working with. So coming to this idea of ecosystem when I was thinking about okay what's an organization open source ecosystem if I need to look at organizations open source software ecosystem is not just the software they develop and actually I've seen at least three kinds of layers of how companies or how this ecosystem could be defined. First of all all these projects that the organization is consuming there is a bunch of projects and I would say that nowadays I don't know any single company that doesn't consume or use or whatever at some level have implications of using open source at some point to build their own stack to check what's going on there I don't know they are consuming open source even because they are actually some developers could be using any packages out there but they are also buying other companies support for using open source so it's not only a matter of I'm taking and not giving back I'm also paying for it at some point. But in addition to this there are also companies that are releasing their own open source projects because they want to attract talent because they want to drive awareness about the things they are doing they want to improve their technical staff many many reasons and you can ask many companies what are the benefits of releasing open source and contributing to open source because the last level of the ecosystem are all these companies are all these projects that the company contributes to basically all the projects that you are participating as a company because you want to drive them you want to I don't know to force them to work in a certain way because you want to retain talent of your company there are have been said that for by allowing people to contribute open source the people in your organization is more willing to keep working in your organization so you know how important it is to retain talent nowadays but also to increase the company tech footprint into open source ecosystem or even to be seen as a with open source citizen so all these projects are your open source ecosystem and you could say that okay that's that's a bunch of projects and how complexity this ecosystem could become this is a very rough analysis we did about the Mozilla I think is already written and you can see it online the Mozilla and the Rebel Alliance and this is only the open source prologue Mozilla organization release and what you're seeing there is is all these big projects like five four you need a lot of you see a lot of stars just closing to them actually those start out people and depending on the color you are seeing how active they are in the project so they are the core contributors the people that are doing 80% of the contributions or yes regular contributors doing 15% of the contributions or even the castle contributors doing 5% of the contributions and I think the most challenging thing that you should be aware of is that there are a lot of people that are not just working on a single project but they are working on several and even they are moving from one project to another so again your ecosystem start to be seen as more complex because all these relationships matter because probably you can decide okay this project is not relevant for me anymore so I'm going to stop any contributions to them or any support to this project and actually the people there could be involved in other projects and they would think okay if the company is not supporting this project I'm not going to be interested on keep working on this or even good key company that has been working in very important projects in the company has started contributing to other projects and you as a company should be aware of why these key people for me is contributing to this other technology perhaps because this is something that could be interesting for us so at some point we should be taking care of that also and last but not least when we are talking about consumer releasing and contributing to open source software okay that could be very funny but if you are doing that without any care it can be very risky like as I said in the picture like just jumping in the air and let's go for the fun thing but if you're not taking the good measures or means with you probably you could be facing risky things and I'm going to talk about just three specific topics I think they are very important the first thing is our legal of course if you're not taking a we're not going not being aware about awareness sorry about licensing IP things or stuff like that probably you could be facing some some important programs I'm not going to talk here about also security that could be somehow related with this legal compliance about it and using projects that are secure or mature enough on similar level are things related with people management like okay if I would like to keep my people engaged with the projects engaged with the company probably allowing them to contribute open source has been said that is good but also to attract talent is good to have open source projects I need to identify all these people and again this this putting into the all this management thing about okay we need a people management thing also involved in this open source relationship with my sorry in this relationship with my open source ecosystem and last but not least that usually this is the first thing that people think about when they are talking about open source is they are talking about engineering about developing things about contributing and improving the the tonal legal stuff and of course that's that's one of the key points but I have led that to the end because for me all these three layers are very important and you need to manage from the legal point of view your relationship with your ecosystem from the people point of view your relationship with your open source ecosystem and from the engineering point of view your relationship with this ecosystem and you can imagine these are very three different skills and very different mindsets that you need to put all together to make this so how we can we can make that and this is where open source program office or open source program office programs office or however you want to call them I usually call them Ospo has become an important role in several organizations and if you know I will recommend you to read them to the group guides you can read there like open source program offices central open source is just a designated place where open source is supported, nurtured, shared, explained and grown inside that company in other words from from my point of view in my humble opinion I think Ospo can play an important role to ensure ecosystem sustainability because actually you at some level because you are consuming because you are contributing as I said before legal people an engineering point of view you are depending on that ecosystem and having some kind of office or set of people in the company that is ensuring that everything is aligned with the ecosystem you are surrounded by I think is where you both your you and your ecosystem ecosystem and your all the environment is secure and growth in a very natural way. So the first thing for me is key from the Ospo point of view you need to understand your open source software ecosystem first you need to know which projects I am contributing to I've been talking with companies that they don't they don't even know where of I don't know where my people are contributing to I don't know even how many open source projects or how many open source is being used in my company and probably because it's not key probably some of you might be just thinking about okay you are a software company you should be aware of that but nowadays companies I would say all companies and I'm not talking about 2020 and all these digital transformation hype but all the companies are becoming software companies at some point so if they are a software company for sure they are using open source somewhere and of course if there is not there if that's not their main business like developing software some people might not be aware in the company that how important open source is for them so they don't even know how much open source they are using and then cannot be even aware of all the risk of using open source without care right of course you can you need to understand who are the key contributors who are the key maintainers of these projects who I need to talk with if there is an issue if I need to hire someone or if I need to identify the talent inside my company that is contributing to these projects name means I need to understand all of these things and it's been said that without data you are just a person with an opinion and we have been seeing all these big data thing for all time about marketing sales and all the stuff why not analyzing also open source and you know this is what Viterlja does and there are more and more people nowadays doing it and you have a bunch of open source and free software tools to use I will just mention a few of them the software 3c stiff by mainly developed by Siemens and a bunch of European companies that is now part of the eclipse foundation set of projects it used to be up and have you probably you call that years ago all that you can check projects activity now you have also called on the diet that we presented here in in Brussels one year ago that is a such tool that you can go there and analyze open source projects quite easily you have grimoire lab that also is one of the projects that Viterlja has been participating in and it's also now in the chaos community that community chaos you know stands from community health analytics for open source software so you have there also definitions of metrics to define the health of an open source project but also open source tools to measure that help so basically you have already a bunch of tools to deal with all of these things another way that you might think okay now I know what how my ecosystem looks like and there are a bunch of place and depending on so basically one of the first thing that people think okay let's find a fund or sponsor these projects to ensure that they have some kind of financial sustainability and that's good that does a good idea I recommend you to check out the options there that are out there to for doing that but I would like to highlight please be aware of tip yards because tip yards doesn't create don't create a sustainable way of living for maintainers for contributors if you are doing that imagine that usually you have another salary income somewhere so tip yard is nice but think about other ways to support this and there are other ways one that I would like to comment today or to highlight is this idea of the promote the way of the maintainer I know I am a Mandalorian fan so I usually use this as this is the way most company most of the people in your company start like active users like why not start in as active user not just users just just using the software now if you find an issue you find something that you don't understand feel free to go to the forums to the jithub issues is tracking system or whatever issues system they are using like jithub jitlab jit whatever for this project and ask questions make yourself okay and here I am using this I don't know how it works I have this issues or I found this interesting start by asking because once you get comfortable with the product and you start doing this path probably there are people even in your organization that is able to contribute back like contributors becoming a contributor like okay I enable also to solve some issues that I've seen in the in this forum by going there probably you realize oh I know also how to solve this probably I don't know all the answers but if you already know any answer please provide that reply to questions even if you have some kind of technical knowledge you can even send path checks to try to fix some of those issues or try to improve the project somehow of course that needs some core review and probably some people will discuss you should be doing this in other way you need to test things and you will learn to solve this process and if you continue this process and probably there is not all the people in your company are gonna do all this but you can achieve the point of okay you can become a maintainer because you are able to review and accept patches and the community also will recognize you are one of these people and your organization one of these organizations involved from this like I can we can even code in the main branch like okay and just driving the players as I would like and even participate in the roadmap of governments and I think that's the whole path that also helps to the sustainability of the projects because it's not a matter of just keep the maintainers like they are I keep also renewing the maintainers or even to have new blood in the maintainer people right but one of the points and also related with this idea of sponsoring projects one of the things I've seen a lot is this idea oh I can do this thing I can take the project I can customize by myself I don't need anyone help because I am a big corporation and like the empire I can do this by myself okay feel free to tell what's going on your ecosystem because there might be companies and individuals providing consulting, customization and even support services on those projects and hiding these bounty people bounty hunters I would say that's an option and it's very nice option because there are already people thinking okay what could be my business model for living or how I can do a living on this over development I basically by tip yards are not going to be made a living of this but if people are hiring me for specific things or like I said consulting and customization this is a way to live and that's what that's that's what's it everything from my side I'm more than welcome to your questions so please let me know you have any question and I will respond that answer that thank you.
 Okay, good afternoon everybody. I think you are seeing this probably in the afternoon  in Port Fosden. That sign says the code, you can see whatever you want. Thank you very  much for joining us today in this online conference that we used to be all together  in Brussels. We are going to miss the waffles a lot. I will probably cook a song of them  for later. My talk today I would like to talk about open source, I don't know if you have  heard about this concept but I will also talk about other topics. I am going to minimize  myself in the video so you don't need to see me that big anymore. I would like to focus  on at least four key topics. The people that we do develop, maintain, contribute to open  source at some point. I will talk of organizations, open source ecosystems. I think it is a concept  I would like to highlight during this talk. Also about open source pro-anophysis, the  important role to help sustainability. One of the key points here about this, how to  help on sustainability, is the way of the maintainer. So let's start. The motivation  for this talk started like, I think it was a couple of months ago, I was preparing a talk  for OpenCore Summit and I was analyzing, I work in Vitergia, we provide analytics about  open source development and how companies develop software in general. But I was analyzing  the commercial open source software company index. I don't know if you know about this  but basically like 45, 50 software companies, companies that develop software and they say  it will provide it as a service. These are the companies that have like $100 million revenue  per year at least. So that's very amount of money, so that's significant amount of money.  That means that you can do money doing open source software development and even providing  service on top of that. So those companies are around in total like 70,000 employees  and the numbers from these indexes are generating revenue around $80 billion per year in revenue.  So that's in total for these 45, 50 companies, that's huge I would say. But okay, going to  what were the people that are maintaining this code, how much active they are, what's  the level of dependency these companies have on the maintainers. It was interesting to  say, okay, these are the top 50 and you can compare that there is like a people that is  doing a lot of identities or identities I would say that are doing all this amazing  work on top of everything that are mostly bots actually. They are bots, but, but, but  there is one human there and you see the amount of work this person has done is above any  average of the rest of the project. So compared to around again 50 companies and these are  people that are getting more than 100 or even more millions of dollars in revenue. So they  are depending on probably the work of this person that I would say don't bother him on  Thursday. I know it's him because I know him also who is the company and the working on  but it's not the matter of the of the conference for me was the key point. Open source is depending  that much in and this company is depending that much in the in the work of a person that  okay companies software development at the end of the day is out people and that's that's  very important and actually if we look at how software is developing in general we have  development activities like writing code we have also deployment like we have more nowadays  automatic ways to deploy things but at the end of the day you have some people involved  there also and maintenance like people checking issues solving issues reporting, bad sets all  this stuff also done by people but also in all these steps you need some kind of collaboration  in one sense of the other of course in open source it's one of the key points for developing  open source at all. So again people from my point of view and I think also Toby said this  last year in also in the community there from here is said that people are the limited resources  in software development ecosystem not only in open source but in software development  ecosystem in general. So we if we are managers in a company or we as community members or  we as companies that are willing to keep developing software we should be aware of the people  we are involved with or we are working with. So coming to this idea of ecosystem when I  was thinking about okay what's an organization open source ecosystem if I need to look at  organizations open source software ecosystem is not just the software they develop and  actually I've seen at least three kinds of layers of how companies or how this ecosystem  could be defined. First of all all these projects that the organization is consuming there is  a bunch of projects and I would say that nowadays I don't know any single company that doesn't  consume or use or whatever at some level have implications of using open source at some  point to build their own stack to check what's going on there I don't know they are consuming  open source even because they are actually some developers could be using any packages  out there but they are also buying other companies support for using open source so it's not  only a matter of I'm taking and not giving back I'm also paying for it at some point.  But in addition to this there are also companies that are releasing their own open source projects  because they want to attract talent because they want to drive awareness about the things  they are doing they want to improve their technical staff many many reasons and you can ask many  companies what are the benefits of releasing open source and contributing to open source  because the last level of the ecosystem are all these companies are all these projects  that the company contributes to basically all the projects that you are participating  as a company because you want to drive them you want to I don't know to force them to  work in a certain way because you want to retain talent of your company there are have  been said that for by allowing people to contribute open source the people in your organization  is more willing to keep working in your organization so you know how important it is to retain  talent nowadays but also to increase the company tech footprint into open source ecosystem  or even to be seen as a with open source citizen so all these projects are your open source  ecosystem and you could say that okay that's that's a bunch of projects and how complexity  this ecosystem could become this is a very rough analysis we did about the Mozilla I  think is already written and you can see it online the Mozilla and the Rebel Alliance  and this is only the open source prologue Mozilla organization release and what you're seeing  there is is all these big projects like five four you need a lot of you see a lot of stars  just closing to them actually those start out people and depending on the color you are  seeing how active they are in the project so they are the core contributors the people  that are doing 80% of the contributions or yes regular contributors doing 15% of the  contributions or even the castle contributors doing 5% of the contributions and I think  the most challenging thing that you should be aware of is that there are a lot of people  that are not just working on a single project but they are working on several and even they  are moving from one project to another so again your ecosystem start to be seen as more  complex because all these relationships matter because probably you can decide okay this  project is not relevant for me anymore so I'm going to stop any contributions to them  or any support to this project and actually the people there could be involved in other  projects and they would think okay if the company is not supporting this project I'm not going  to be interested on keep working on this or even good key company that has been working  in very important projects in the company has started contributing to other projects  and you as a company should be aware of why these key people for me is contributing to  this other technology perhaps because this is something that could be interesting for  us so at some point we should be taking care of that also and last but not least when we  are talking about consumer releasing and contributing to open source software okay that could be  very funny but if you are doing that without any care it can be very risky like as I said  in the picture like just jumping in the air and let's go for the fun thing but if you're  not taking the good measures or means with you probably you could be facing risky things  and I'm going to talk about just three specific topics I think they are very important the  first thing is our legal of course if you're not taking a we're not going not being aware  about awareness sorry about licensing IP things or stuff like that probably you could be facing  some some important programs I'm not going to talk here about also security that could  be somehow related with this legal compliance about it and using projects that are secure  or mature enough on similar level are things related with people management like okay  if I would like to keep my people engaged with the projects engaged with the company  probably allowing them to contribute open source has been said that is good but also to attract  talent is good to have open source projects I need to identify all these people and again  this this putting into the all this management thing about okay we need a people management  thing also involved in this open source relationship with my sorry in this relationship with my  open source ecosystem and last but not least that usually this is the first thing that people  think about when they are talking about open source is they are talking about engineering  about developing things about contributing and improving the the tonal legal stuff and of  course that's that's one of the key points but I have led that to the end because for  me all these three layers are very important and you need to manage from the legal point  of view your relationship with your ecosystem from the people point of view your relationship  with your open source ecosystem and from the engineering point of view your relationship  with this ecosystem and you can imagine these are very three different skills and very different  mindsets that you need to put all together to make this so how we can we can make that  and this is where open source program office or open source program office programs office  or however you want to call them I usually call them Ospo has become an important role  in several organizations and if you know I will recommend you to read them to the group  guides you can read there like open source program offices central open source is just  a designated place where open source is supported, nurtured, shared, explained and grown inside  that company in other words from from my point of view in my humble opinion I think Ospo  can play an important role to ensure ecosystem sustainability because actually you at some  level because you are consuming because you are contributing as I said before legal people  an engineering point of view you are depending on that ecosystem and having some kind of  office or set of people in the company that is ensuring that everything is aligned with  the ecosystem you are surrounded by I think is where you both your you and your ecosystem  ecosystem and your all the environment is secure and growth in a very natural way.  So the first thing for me is key from the Ospo point of view you need to understand  your open source software ecosystem first you need to know which projects I am contributing  to I've been talking with companies that they don't they don't even know where of I don't  know where my people are contributing to I don't know even how many open source projects  or how many open source is being used in my company and probably because it's not key  probably some of you might be just thinking about okay you are a software company you  should be aware of that but nowadays companies I would say all companies and I'm not talking  about 2020 and all these digital transformation hype but all the companies are becoming software  companies at some point so if they are a software company for sure they are using open source  somewhere and of course if there is not there if that's not their main business like developing  software some people might not be aware in the company that how important open source  is for them so they don't even know how much open source they are using and then cannot  be even aware of all the risk of using open source without care right of course you can  you need to understand who are the key contributors who are the key maintainers of these projects  who I need to talk with if there is an issue if I need to hire someone or if I need to  identify the talent inside my company that is contributing to these projects name means  I need to understand all of these things and it's been said that without data you are just  a person with an opinion and we have been seeing all these big data thing for all time about  marketing sales and all the stuff why not analyzing also open source and you know this  is what Viterlja does and there are more and more people nowadays doing it and you have  a bunch of open source and free software tools to use I will just mention a few of them the  software 3c stiff by mainly developed by Siemens and a bunch of European companies that is  now part of the eclipse foundation set of projects it used to be up and have you probably  you call that years ago all that you can check projects activity now you have also called  on the diet that we presented here in in Brussels one year ago that is a such tool that you  can go there and analyze open source projects quite easily you have grimoire lab that also  is one of the projects that Viterlja has been participating in and it's also now in the chaos  community that community chaos you know stands from community health analytics for open source  software so you have there also definitions of metrics to define the health of an open  source project but also open source tools to measure that help so basically you have  already a bunch of tools to deal with all of these things another way that you might  think okay now I know what how my ecosystem looks like and there are a bunch of place  and depending on so basically one of the first thing that people think okay let's find a  fund or sponsor these projects to ensure that they have some kind of financial sustainability  and that's good that does a good idea I recommend you to check out the options there that are  out there to for doing that but I would like to highlight please be aware of tip yards  because tip yards doesn't create don't create a sustainable way of living for maintainers  for contributors if you are doing that imagine that usually you have another salary income  somewhere so tip yard is nice but think about other ways to support this and there are other  ways one that I would like to comment today or to highlight is this idea of the promote  the way of the maintainer I know I am a Mandalorian fan so I usually use this as this is the way  most company most of the people in your company start like active users like why not start  in as active user not just users just just using the software now if you find an issue  you find something that you don't understand feel free to go to the forums to the jithub  issues is tracking system or whatever issues system they are using like jithub jitlab jit  whatever for this project and ask questions make yourself okay and here I am using this  I don't know how it works I have this issues or I found this interesting start by asking  because once you get comfortable with the product and you start doing this path probably  there are people even in your organization that is able to contribute back like contributors  becoming a contributor like okay I enable also to solve some issues that I've seen in  the in this forum by going there probably you realize oh I know also how to solve this  probably I don't know all the answers but if you already know any answer please provide  that reply to questions even if you have some kind of technical knowledge you can even send  path checks to try to fix some of those issues or try to improve the project somehow of course  that needs some core review and probably some people will discuss you should be doing this  in other way you need to test things and you will learn to solve this process and if you  continue this process and probably there is not all the people in your company are gonna  do all this but you can achieve the point of okay you can become a maintainer because  you are able to review and accept patches and the community also will recognize you are  one of these people and your organization one of these organizations involved from this  like I can we can even code in the main branch like okay and just driving the players as  I would like and even participate in the roadmap of governments and I think that's the whole  path that also helps to the sustainability of the projects because it's not a matter  of just keep the maintainers like they are I keep also renewing the maintainers or even  to have new blood in the maintainer people right but one of the points and also related  with this idea of sponsoring projects one of the things I've seen a lot is this idea  oh I can do this thing I can take the project I can customize by myself I don't need anyone  help because I am a big corporation and like the empire I can do this by myself okay feel  free to tell what's going on your ecosystem because there might be companies and individuals  providing consulting, customization and even support services on those projects and hiding  these bounty people bounty hunters I would say that's an option and it's very nice option  because there are already people thinking okay what could be my business model for living  or how I can do a living on this over development I basically by tip yards are not going to  be made a living of this but if people are hiring me for specific things or like I said  consulting and customization this is a way to live and that's what that's that's what's  it everything from my side I'm more than welcome to your questions so please let me know you  have any question and I will respond that answer that thank you.
community_devroom_ospo_oss_ecosystems_0_179.png community_devroom_ospo_oss_ecosystems_180_791.png community_devroom_ospo_oss_ecosystems_792_947.png community_devroom_ospo_oss_ecosystems_948_1043.png community_devroom_ospo_oss_ecosystems_1044_1127.png community_devroom_ospo_oss_ecosystems_1128_1295.png community_devroom_ospo_oss_ecosystems_1296_1451.png community_devroom_ospo_oss_ecosystems_1452_1979.png community_devroom_ospo_oss_ecosystems_1980_3179.png community_devroom_ospo_oss_ecosystems_3180_3323.png community_devroom_ospo_oss_ecosystems_3324_3671.png community_devroom_ospo_oss_ecosystems_3672_4403.png community_devroom_ospo_oss_ecosystems_4404_5459.png community_devroom_ospo_oss_ecosystems_5460_6311.png community_devroom_ospo_oss_ecosystems_6312_6959.png community_devroom_ospo_oss_ecosystems_6960_7271.png community_devroom_ospo_oss_ecosystems_7272_8783.png community_devroom_ospo_oss_ecosystems_8784_9779.png community_devroom_ospo_oss_ecosystems_9780_12239.png community_devroom_ospo_oss_ecosystems_12240_12827.png community_devroom_ospo_oss_ecosystems_12828_15119.png community_devroom_ospo_oss_ecosystems_15120_16919.png community_devroom_ospo_oss_ecosystems_16920_18935.png community_devroom_ospo_oss_ecosystems_18936_19379.png community_devroom_ospo_oss_ecosystems_19380_20807.png community_devroom_ospo_oss_ecosystems_20808_22019.png community_devroom_ospo_oss_ecosystems_22020_23363.png community_devroom_ospo_oss_ecosystems_23364_24419.png community_devroom_ospo_oss_ecosystems_24420_25379.png community_devroom_ospo_oss_ecosystems_25380_26795.png community_devroom_ospo_oss_ecosystems_26796_27143.png community_devroom_ospo_oss_ecosystems_27144_27419.png community_devroom_ospo_oss_ecosystems_27420_27543.png