Demystifying OSPOs: What InnerSource can bring to emerging Open Source Initiatives
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 39 | |
| Author | ||
| License | CC Attribution 3.0 Unported: 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. | |
| Identifiers | 10.5446/67227 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
FOSS Backstage 202219 / 39
2
9
11
15
26
30
36
37
00:00
Open sourcePattern languageOpen sourceLecture/ConferenceMeeting/InterviewComputer animation
00:30
Standard deviationSoftwareSpacetimeOpen sourceSoftware developerSelf-organizationBuildingMachine codeComponent-based software engineeringProcess (computing)Mathematical analysisDigital signal processingCodecSelf-organizationCollaborationismCartesian coordinate systemStrategy gamePoint (geometry)Different (Kate Ryan album)Open sourceSoftwareMathematicsCASE <Informatik>Term (mathematics)Interior (topology)TwitterEvolutePattern languageSimilarity (geometry)PasswordStandard deviationMultiplication signBit ratePower (physics)Office suiteLine (geometry)Computer programmingComputer animation
05:19
Computer programmingGroup actionDifferent (Kate Ryan album)Characteristic polynomialLevel (video gaming)Pattern languageSoftware frameworkLimit (category theory)Term (mathematics)Right angleOpen sourceOpen setOffice suiteMultiplication sign
06:45
Characteristic polynomialExplosionContent (media)Open sourceSet (mathematics)Formal grammarNumberStreaming mediaLinear mapSelf-organizationOpen sourceCodeProcess (computing)Characteristic polynomialLink (knot theory)Observational studyData conversionGroup actionCollaborationismData managementProjective planeNumberProcedural programmingInternet forumTurtle graphicsLevel (video gaming)
08:41
Characteristic polynomialCollaborationismBitMixed realityFrame problemTemplate (C++)Observational studyDivision (mathematics)Open sourcePoint (geometry)Self-organizationPerspective (visual)Right angleComputer animation
10:32
Open sourceLocal GroupLevel (video gaming)Decision theorySoftwareSoftware developerLevel (video gaming)Open sourceSelf-organizationDifferent (Kate Ryan album)Endliche ModelltheorieProjective planeTerm (mathematics)Observational studyPoint (geometry)Context awarenessStrategy gameLaptopRight angleState of matter1 (number)Group actionData managementInstance (computer science)Process (computing)Computer animation
12:43
Open sourceLocal GroupLevel (video gaming)WebsiteRight anglePlanningForcing (mathematics)Level (video gaming)Open sourceSelf-organizationMereologySoftware developerPower (physics)Projective planeDecision theoryArithmetic mean1 (number)State of matterComputer animation
14:27
Open sourceProcess (computing)Interior (topology)SoftwareOpen sourceCodeProcess (computing)Descriptive statisticsCollaborationismDependent and independent variablesComputer programmingReal numberObservational studySelf-organizationTerm (mathematics)Formal grammarComputer animation
15:56
Programmer (hardware)Open sourceLocal GroupComputer programSeries (mathematics)MathematicsLevel (video gaming)Machine codeMechatronicsSoftwareAsynchronous Transfer ModeEntire functionTask (computing)Strategy gameCore dumpAnalogyDisk read-and-write headOpen sourceOffice suiteBlogProcess (computing)Level (video gaming)Position operatorEvent horizonInterior (topology)TwitterData managementVirtualizationSystem programmingShared memoryFood energySoftware developerStreaming mediaArithmetic progressionSelf-organizationReal numberComputer programmingDifferent (Kate Ryan album)CASE <Informatik>Product (business)Application service providerEvoluteDecision theoryMathematicsState of matterSession Initiation ProtocolStructured programmingEntire functionForm (programming)1 (number)Computer animationXML
20:57
Stack (abstract data type)RootService (economics)Product (business)Strategy gameOpen sourceMachine codeDependent and independent variablesOpen setComputer programmingOpen sourceObservational studySelf-organization2 (number)Integrated development environmentPersonal identification numberOrder (biology)Perspective (visual)
22:05
Local GroupLevel (video gaming)Capability Maturity ModelSelf-organizationRight angleComputer animation
22:32
SpacetimeMereologyOffice suiteFood energyOpen sourcePower (physics)Level (video gaming)Source codeSoftwareInstance (computer science)Perspective (visual)Interior (topology)Computer animation
24:59
OvalStandard deviationOffice suiteInstance (computer science)Interior (topology)Electronic program guideLevel (video gaming)Mixed realityOpen sourceOpen setGroup actionMetric systemScaling (geometry)MathematicsSource codeSheaf (mathematics)Self-organizationComputer programmingChaos (cosmogony)
26:42
Software developerSoftware developerOpen sourceInterior (topology)Strategy game2 (number)Reduction of order
27:22
Division (mathematics)Open sourceComputer programData managementImplementationComputer networkEmailLocal GroupChaos (cosmogony)Software developerDegree (graph theory)Theory of relativityTwitterSlide ruleComputer programmingMetric systemLevel (video gaming)Data managementOpen sourceHypothesisLink (knot theory)Projective planeSheaf (mathematics)Software repositoryWeb pageElectronic program guideBitAnalytic setOffice suiteInterior (topology)Group actionHypermediaWave packetMultiplication signChaos (cosmogony)SoftwareComputer animation
29:55
Open sourceComputer animation
Transcript: English(auto-generated)
00:04
Hi everyone. Thank you so much for attending today's talk. Today I'm here to talk about OSPOs, try to demystify what is an OSPO and some of the patterns of an OSPO.
00:21
And also get the chance to talk about what inner source can bring to emerging open source initiatives or OSPOs. So I will be following this agenda. The first topic will be more related with what do we mean with OSPOs.
00:40
Why is this starting to pop everywhere around the world? Is that a vast world? Is it actually a real thing? How can we define an OSPO and so on? Then we will move to the evolution of the OSPO case. It hasn't been a new term. It has been here for a while, but it has evolved along these years.
01:05
Then we'll move to some inner source trends in OSPO, how other organizations and companies are dealing with that. And some inner source patterns we are seeing in actual established OSPOs or similar open source initiatives.
01:24
And finally, if I have time, I would like to share with you some idea I have about cross community collaboration and how cross community can excel these OSPOs and open source initiatives.
01:41
Alright, so let's start with the first topic. Here I would like first to focus on the topic around innovation and how organizations right now are trying to face digital transformation with trying to implement so many different approaches and so on.
02:03
And we see when we talk about the innovation race, we see that software is always there, right? So software is in any organization nowadays. And what is powering software in many cases, in fact, almost the 80% of the software components for modern applications are running on open source.
02:28
So if we are talking about how to foster innovation and how to face digital transformation within organizations, at some point we need to think about software and we need to then think about open source.
02:47
So we are no longer talking about the innovation race, we are talking about an open source race. And here is the trick, because open source has so many different paths, activities, and things an organization needs to be focused on.
03:07
So here are some of the examples, like when the organization needs to adopt open source, they need to think about what infrastructure should be they adopting, create new policies, new standards,
03:21
try to embrace cultural change within the organization, set up the tooling, and take care of the software competition analysis and more and more activities. So some organizations, what they have been doing so far is say, okay, let's build a strategy on top of all this activity.
03:44
Let's bring alignment to all these activities and bring a strategic place for all the open source activities that the organization should be focused on. And actually, that is what an OSPO is.
04:02
It doesn't matter if you call it an OSPO, open source office, or open source program, or open source strategic center, there are several ways to call an OSPO, but the essence of the OSPO is to put a strategy on top of open source activities.
04:25
Because with a strategy, you will have more alignment, and if you have alignment, you will ease the open source adoption at some point. It's not just contributing or using open source ad hoc, it's having a strategy to accelerate this open source process adoption.
04:49
And that will increase innovation. So the way I like to see OSPOs are like the open source accelerators for organizations.
05:05
And just to be also more specific, the OSPO, what it lands, it's more like the linspin between the organization and the open source ecosystem.
05:20
Okay, that's all. That is what an OSPO is. It's easy, right? It seems like, okay, it's clear. It's a strategy. Okay, but sometimes I come from the tutor group that it's an open group of organizations focused on open source program offices. And sometimes, many times, that is not enough.
05:41
Like, organizations need sometimes to see some kind of pattern of how to start, how to evolve, and have a better framework of where are the limits of the OSPO and how is it structured. So I'd also like now to share three main questions and three main issues that I've been hearing a lot from other organizations
06:09
that are what is exactly an OSPO, like what characteristics does an OSPO have. Also, in terms of what are the different stages that an OSPO can adopt and some of the different OSPO behaviors that we can find.
06:29
Again, this is not just a fixed place to do this. This is more like some examples of how other organizations are structuring their OSPO.
06:47
Okay, so first step is what defines an OSPO. This comes from the latest study from the tutor group in collaboration with the Linux research that were defining some OSPO personas and five characteristics that can help people to better understand what is an OSPO.
07:10
So according to this research, what defines an OSPO is the first, employees are tasked with fostering and nurturing open source usage.
07:20
Second, the organization has a formal policy around the consumption of open source. Third, the top level managers and the executive recognize open source as a strategic asset. Fourth, there are some numbers of employees that are tasked to contributing code to open source projects.
07:48
And the last one, all procedures, processes, and tooling are set to facilitate open source consumption and participation.
08:02
So with these five characteristics, if your organization is working on that or doing that, you can perfectly think, okay, this is kind of what an OSPO is like. And again, it doesn't matter about the branding you tell them, it's more about if these characteristics are met.
08:26
Also, I've left you the link to the study and there is a great conversation we had about other ways to call an OSPO in the OSPO forum that people can also take a look at.
08:41
The next point is there was some questions about people saying, hey, but an OSPO is not just a template, right? A broad template that everyone can take and apply. It depends on the goals the organization has and the industry where the organization came from.
09:05
If it's a private organization or a public organization, there have many different ways to behave. And that is something we also bring in the study that we bring some OSPO personas that again, these OSPO personas are not just, okay, you have this and that's all.
09:24
This is a dynamic study. We would love the community to contribute to more perspective, more OSPO personas to bring more value to this kind of division.
09:41
But so far, you can see like if you go to the study, you will see like the six personas we develop. And might be organizations that just look at this segmentation and say, hey, but I'm kind of open source first and cross industry collaborative. I have both. Well, it's because they are not siloed, but you can have a little bit of mix of some characteristics.
10:09
But it might help you to better frame what's the kind of your OSPO. And if you see other OSPOs with the similar behavior, it might be easier for
10:21
you to go and check that kind of resources and how those OSPOs are doing. And it will help you to advance in your open source journey. And last, there was another discussion about, well, what are the different stages if
10:42
I'm building an open source initiative, the different stages that an OSPO can take. Cornelius did a great talk previously in stage two, talking about this model and other models more focused not only in OSPOs, but in open source adoption.
11:04
And he served several ones. This is the one that is related with Tutor Group and OSPOs and the study that I was mentioning earlier. So in this study, you can see that at the very beginning, there is not even an OSPO.
11:21
There is some open source ad hoc, like organizations notice that their developers are using open source at some point to do their job. And that is a reality. And then the organization starts to have awareness of that and say, hey, we should maybe take care of that about that.
11:41
That usually happens in the legal side. And when that happens, when there is awareness in that organization that we should seriously be taking open source seriously, put on a strategy on top of that, it starts the legal education usually. Is that what happens?
12:02
And it's everything around providing open source software compliance, inventory, and developer education to legal things. So there are policies and everything related with risk managers, what open source projects will they
12:21
be contributing at, what is CLA, for instance, like even basic stuff in terms of legal education. Once that is covered, move to community education. So that is more about evangelizing open source use and ecosystem participation.
12:42
As you can see, these stages are cumulative. So if you move to the community education, it doesn't mean that you stop doing legal education.
13:03
I mean, you're still working on the legal side, but then you have more ability to execute, and you are able to also invest in community education. And these three stages are really, really important because those are the first ones.
13:23
And when the early stages, OSPOs start usually are in these three first stages. And then once they have covered this, once they have this developer education in place, they move to the engagement stage.
13:40
So that is more like the visible part of the OSPO. It's when the OSPO has that power to say, okay, let's contribute outbound to open source. Let's start hosting open source projects. Let's start growing communities. So this is more like the visible side, right? And finally, the most major OSPOs might be thinking about, okay, we have covered all these stages.
14:06
Let's see how can we become a strategic decision-making partner within the organization, and how the OSPO can be this strategic partner for the IT or for the CTO, or for strategic places within the organization to help them make decisions.
14:30
Okay, so now we can move. Now we have seen what an OSPO is and how these OSPOs can be structured, at least some examples.
14:41
So let's go now to some story of the OSPO. And if this is actually a real thing or it's just a buzzword that people are starting to talk about nowadays. So to explain you this, I would like to share this recent study we did in collaboration with Aleph Research.
15:04
That basically shares some insights about how OSPOs are getting bigger and bigger in terms of there is, it seems to be more increase in funding for open source initiatives.
15:21
Established, OSPO have already highlighted improved code quality. More than 77% of respondents says that open source program had a positive impact in their organization. And we are seeing more OSPO jobs, like actually jobs that says OSPO or open source initiatives
15:46
within the job description. So that is great news for the OSPO ecosystem because it seems that it's getting more formalized. And also to see like how big is this OSPO system going.
16:03
This comes from the OSPO landscape where we try to map all the OSPO adopters that in a public way they say they have an OSPO. And you can see there are a lot of organizations from all over the world or over the industries, public and private.
16:22
But also take into account that these are the OSPOs that share that. That share that hey we are doing an open source initiative and here is the work we have done. But we also have to think about the work in progress OSPOs. So those OSPOs, they are not official yet.
16:41
Maybe they are doing open source ad hoc and trying to learn from others how to go to one step to another. And also the early stage OSPOs that yes we have an OSPO but we still don't want to make that public yet. We say it but we don't want to have a lot of presence until we start to do some work.
17:06
So that is something that must take into account. And these are some real examples, some real news about different organization from different sectors, public and private that officially share they have an OSPO.
17:22
Port, Goldman Sachs, the European Commission and the last new, the World Health Organization is launching its open source program office which is amazing. And they are looking for a job position on OSPO manager and I think they are asking it for Berlin, so to be based in Berlin just in case.
17:46
Okay, so now that we have shared some of the OSP evolution, let's move to the next topic that are inner source trends in OSPOs.
18:02
And before starting, just to let you know that yesterday during the virtual event at Fosbach State we did a really interesting topic about this, about inner source and OSPOs and institutionalizing open source cultural trends with Isabel, with Tim, with Claire and I.
18:24
And it was a panel discussion and we bring really interesting topics there so I really recommend you to go and check that. And also I would like to start with some examples where you can see that how inner source is being implemented within the OSPOs.
18:48
The first example is from the World Health Organization. So these are like a nice chart saying like where the World Health Organization team thinks an OSPO should initially focus.
19:04
And as you can see, one of the columns, it's entire internal culture. Like try to bring an open source culture within organization that for those who doesn't know, that it's inner source basically. Then this comes from one of our to-do ospology sessions where we invited Aliander from the Netherlands energy sector.
19:29
And they were sharing like their OSPO journey, which it was great. And in that chart, in that OSPO journey, they highlighted the launch of Aliander's inner source portal.
19:41
So they even call it inner source and the publicity said that they are having an OSPO. But within the OSPO, they have an inner source team. Also from SIP, that is, I think it was like some months ago, they shared like how their OSPO is structured in one of their recent blog posts.
20:05
And here you can see like it's also the entire OSPOs are clustered in work streams, okay. So in one of those work streams is inner source. And this is the long one, I think Nearform was the one that served this use case that is lessons from a journey to inner source at Comcast.
20:29
But that inner source practices are also within the OSPOs and they don't call it inner source. They said growing open source culture inside of Comcast. So you can see, even though they don't call it inner source, the need for developer education on how to engage with open source, it's a reality.
20:53
It's something that in OSPOs needs to happen. Also in our recent studies, there was a question that was what are the primary responsibilities of the open source programs?
21:05
And the majority of respondents, the first one was fostering an open source culture within our organization that is inner source. And what is happening in that? Why is this happening?
21:22
If you remember this chart I shared with you earlier, that is, OSPO is the linspin between the organization and the open source ecosystem. You need to take care a lot of the organization side first, right? In fact, you need to meet your criteria internally in order to move forward.
21:45
From my perspective, it will be build a safe environment, so legal education. And second, build a supportive environment that is community education. But all that, it's happening within the walls of the organization.
22:05
And surprise, that it's also in the maturity model where the first stages, once the organization starts to develop an OSPOs, needs to take care about.
22:23
Right before starting with engagement and leadership, they need to focus on legal and community education. And okay, now let's move to the last part. And this is more like some ideas I wanted to share with you.
22:43
And right after this talk, I would like to share your feed to see what do you think about this, if it makes sense or not, and also bring some discussions with the community. Okay, so if you remember, I said that OSPOs are the open source accelerators because it can drive innovation.
23:08
But how can we accelerate OSPOs? Are there any ways to do that? Well, I think there are, and that is due to the power of communities. I think communities are really, really important, and network spaces and resources together can help a lot to accelerate those OSPOs.
23:29
But when organizations start to engage with communities in the open source, it's sometimes really overwhelming. Like how many different communities are out there and how they engage and
23:44
the different foundations and the different players, they take part in those communities, right? So from the OSPO perspective, and also for the OSPO that comes from in our source program office perspective, I think that maybe a great idea or a good idea could be to try to differentiate these kind of communities.
24:08
Because we have communities that has an expertise in an industry. Like for instance, Finos from FinTech, it's really focused on driving open source adoption to the banking sector and finance sector.
24:24
They're really specialized in that industry. Or also LF Energy, for instance, they are specialized in bringing open source adoption for the energy sector. So those are communities that can be the enablers when starting in open source.
24:49
Then we have the facilitators. So facilitators have the expertise in a specific subject. So for instance, if you take a look to the stages that I served with you before, you can see that, for instance,
25:08
if our organization is focused on first having legal education and having open source compliance standards, maybe there are certain communities out there where they can rely on.
25:22
For instance, OpenChange, or xVDx, or OSSF, and many, many more. Not only in the Linux Foundation, also in other foundations, of course, but they are the expertise of certain topics. Or for instance, if you're thinking about metrics and open source sustainability, maybe looking at things such as chaos for that section.
25:49
And finally, we have the guide communities. So those communities that have expertise in open source program offices, or in-source program offices, adoption, and growth. And it's more like an overview of all this.
26:06
So for instance, from the in-source side, InnerSource Commons is a great community to start at. Studio group, OSSF, I mean, there are so many different organizations there that are doing this guide efforts
26:22
to help organizations to excel in their open source journey. And I will say also that you might find communities that are a mix between two or like between both. Maybe there are communities that are enabled and also a guide.
26:42
And just to finish with today's talk, some remarks for this talk. So first one, OSPOs are a way to bring strategy to open source efforts. Second, InnerSource teams can become the expertise team for OSPO, for the OSPO engineering or developer education.
27:13
And third, OSPOs can reduce InnerSource resources for their practices to avoid duplicated effort.
27:23
Just third story about what is Studio Group. So we are an open community of more than 70 organizations all around the world and more than 1000 OSPOs because Studio Group is not just about the general members, it's about its great community that are contributing to the open project itself
27:46
and working together to drive OSPOs to the next level. And we were founded in, it's been now a long time, and working to run open source program setup. And we have great resources here. This is just an overview of all the different sections.
28:07
You can, as a community, can start joining these resources. We have great OSPO network, education, training, research, and OSPO tools. You can go to the Tudo GitHub repo and also if you check the Tudogroup.org page slash community,
28:29
there is a great onboarding guide for new people, newcomers that wants to join the community. And last but not least, a little bit about myself.
28:41
I started with open source in Vitaria. For those who doesn't know, it's an software development analytics firm, especially I see it in open source program offices in our source and software development metrics. Currently, I'm the OSPO program manager at TudoGroup.
29:00
I also, last year, I finished my thesis for my last master's degree in data science, where I was focusing more on developer and open source development relations metrics. I'm also involved in other communities such as CHAOS, TudoGroup of course,
29:20
Inner Source Commons, DevRel Collective, or DevRel Spain. That is my Twitter. If you want to follow me on LinkedIn, it's Ana Jimenez, Santa Maria. And yeah, thank you. I've also let you know that I will share these slides in my social media, so if you want to follow me to be up to date of these resources,
29:43
you're welcome to follow me. And there I also share the link to join the Tudo community and the link to join the Inner Source Commons community. And thank you so much.