WEBVTT

00:00.000 --> 00:08.000
Okay, that's the one.

00:30.000 --> 00:37.000
Okay, so my name is Glenn Erksson.

00:37.000 --> 00:43.000
I'm going to present a study that we have done.

00:43.000 --> 00:47.000
I started in 2023.

00:47.000 --> 00:54.000
I'm just working for a non-profit research organization.

00:54.000 --> 01:01.000
I focused on applied research in development established in 2011 in Sweden.

01:01.000 --> 01:04.000
And our project, generally focused on open source,

01:04.000 --> 01:09.000
Open Data Research within the transport sector.

01:09.000 --> 01:15.000
In case there are open source ecosystems studies from 2012,

01:15.000 --> 01:21.000
suggest that participation in open source development can reshape

01:21.000 --> 01:25.000
organization practice includes software development methodologies,

01:25.000 --> 01:30.000
knowledge management approach and innovation processes.

01:30.000 --> 01:34.000
And a few studies on how open source participation

01:34.000 --> 01:37.000
contribute to organization transformation,

01:37.000 --> 01:39.000
especially traditional organization,

01:39.000 --> 01:46.000
lacking pre-existing digital transformation capabilities.

01:46.000 --> 01:48.000
So that's if this work.

01:48.000 --> 01:50.000
Okay.

01:50.000 --> 01:55.000
Yeah, so our study centers around digital transformation

01:55.000 --> 01:57.000
in the public organization,

01:57.000 --> 02:01.000
especially in public transportation organization.

02:01.000 --> 02:08.000
And this is a study literature review from 2021,

02:08.000 --> 02:13.000
where digital transformation is seen as a top-down initiative

02:13.000 --> 02:16.000
consisting of two main themes.

02:16.000 --> 02:22.000
It's a maleable organization design to adopt to constant change,

02:22.000 --> 02:27.000
changing environment and embeddedness in the digital business ecosystem,

02:27.000 --> 02:31.000
which characterized by their ever evolving turbulent nature.

02:31.000 --> 02:33.000
I won't go into more details,

02:33.000 --> 02:38.000
but this is another study done on from 2019

02:38.000 --> 02:43.000
on traditional organization in several different sectors.

02:43.000 --> 02:46.000
And they came out to this different capabilities

02:46.000 --> 02:50.000
that organization needs to be digital transformed

02:50.000 --> 02:53.000
and engage in the digital ecosystem.

02:58.000 --> 03:02.000
So transformation challenges.

03:02.000 --> 03:03.000
Public organization,

03:03.000 --> 03:06.000
generally determined by cost focus,

03:06.000 --> 03:09.000
outsourcing, contractual relationship,

03:09.000 --> 03:13.000
function-based procurement and fixed-time frame,

03:13.000 --> 03:17.000
which impedes digital innovation and transformation.

03:17.000 --> 03:21.000
Studies from the mid-2000 established that contractual relationship

03:21.000 --> 03:25.000
impedes innovation and responds to market change.

03:25.000 --> 03:28.000
So this is all news.

03:28.000 --> 03:32.000
But I don't know how many of you work in the public sector

03:32.000 --> 03:34.000
or transportation sector.

03:34.000 --> 03:36.000
Okay.

03:36.000 --> 03:38.000
Is that new to you?

03:38.000 --> 03:40.000
You are totally...

03:40.000 --> 03:41.000
Huh?

03:41.000 --> 03:43.000
It's not really new, but must I have a side again?

03:43.000 --> 03:44.000
Exactly.

03:44.000 --> 03:45.000
I'm going through this quite quick,

03:45.000 --> 03:47.000
so we can go to the core of the presentation,

03:47.000 --> 03:50.000
but I just need to get everybody on board.

03:50.000 --> 03:53.000
And rigid and silo-based organization

03:53.000 --> 03:57.000
can lead to development creates ad hoc IT solution,

03:57.000 --> 03:59.000
called shadow IT,

03:59.000 --> 04:02.000
to fix or solve immediate problems.

04:02.000 --> 04:05.000
This can further fragment the overall IT system environment,

04:05.000 --> 04:09.000
and create overlap and lead to resource waste.

04:09.000 --> 04:13.000
So yeah, let's speed up.

04:13.000 --> 04:17.000
So now we come to the topic for this presentation.

04:17.000 --> 04:21.000
Study on community engagement.

04:21.000 --> 04:26.000
So the idea for the study started in, as a report in 2023,

04:26.000 --> 04:30.000
on how open source was used to digital digital disrupt

04:30.000 --> 04:34.000
the public transportation sector in Norway.

04:35.000 --> 04:38.000
To see if other organizations,

04:38.000 --> 04:41.000
you're only resemblance to one from Norway.

04:41.000 --> 04:46.000
Finding one in session to interview in the community took one year,

04:46.000 --> 04:49.000
and was concluded in October 2025.

04:49.000 --> 04:51.000
So quite recently.

04:51.000 --> 04:54.000
It's quite hard to interact with open source community,

04:54.000 --> 04:55.000
because it's quite opaque,

04:55.000 --> 04:58.000
which people engage in, which organization,

04:58.000 --> 05:01.000
maybe there is only a GitHub account or that's what you see.

05:01.000 --> 05:04.000
It's quite hard to find number of organizations.

05:04.000 --> 05:09.000
But to finally make it, we find 13 of them.

05:09.000 --> 05:11.000
So how much time do I have?

05:11.000 --> 05:14.000
Seven minutes, I'm up there, okay.

05:14.000 --> 05:18.000
So the result of the study, which I will present soon,

05:18.000 --> 05:21.000
is submitted as a full conference paper by me

05:21.000 --> 05:25.000
and Professor Yuho Linman from University of Gothenburg,

05:25.000 --> 05:28.000
to the European Conference on Information System,

05:28.000 --> 05:32.000
which is in Milan, in 2006.

05:32.000 --> 05:34.000
And their announcement for submitted papers

05:34.000 --> 05:38.000
will be in the end of February, I think, so we don't know yet.

05:38.000 --> 05:43.000
So the things I will show you now, it's important to notice

05:43.000 --> 05:48.000
that the model I will present applies to developer communities,

05:48.000 --> 05:50.000
open source communities.

05:50.000 --> 05:53.000
The community, in the study, is quite small,

05:53.000 --> 05:57.000
but the narrow focus have a meritocratic governance model,

05:57.000 --> 06:02.000
dedicated member organization, and have very few hobby programmers.

06:02.000 --> 06:05.000
The relevance for other types of communities,

06:05.000 --> 06:10.000
such as vendors, sponsored, user and phone nation communities,

06:10.000 --> 06:13.000
with other governance model needs to be studied further.

06:13.000 --> 06:17.000
So this doesn't apply to everything, or we hope maybe

06:17.000 --> 06:24.000
some of them or findings will address also other communities.

06:24.000 --> 06:27.000
So let's see, this is, I won't go through everything,

06:27.000 --> 06:33.000
because it's quite, a lot of things in the model,

06:33.000 --> 06:38.000
but I will start with, let's see if I see all the text.

06:38.000 --> 06:42.000
So to start your present, an open source community engagement model,

06:42.000 --> 06:46.000
consist of three main elements, organization, community,

06:46.000 --> 06:48.000
and digital transformation.

06:48.000 --> 06:52.000
I've great up everything here else, so you don't have to focus on that now.

06:53.000 --> 06:57.000
Organizational element represent the internal incentives and activity,

06:57.000 --> 07:00.000
perform to align the organization to the community.

07:00.000 --> 07:05.000
The more involved they get in the community, the more aligned they become,

07:05.000 --> 07:08.000
and the process iterative, and continuous.

07:08.000 --> 07:11.000
That's the back and forth arrow there.

07:11.000 --> 07:14.000
So nine minutes.

07:14.000 --> 07:19.000
Organizational activity sub-aliment consists of evaluating community viability.

07:19.000 --> 07:25.000
This is an activity prior to taking the decision to engage in a community.

07:25.000 --> 07:30.000
This entails assessing the open resources, such as documentation, code base,

07:30.000 --> 07:35.000
repository interactions, frequency, number of maintainers, et cetera.

07:35.000 --> 07:43.000
But the most time-consuming event is activity to determine if the software

07:43.000 --> 07:46.000
design and architecture is sound and viable.

07:47.000 --> 07:54.000
This you need developer competence and next element, maybe the main one.

07:54.000 --> 07:57.000
This is more massive.

07:57.000 --> 07:59.000
This is the community.

07:59.000 --> 08:03.000
The community element represent the mechanisms.

08:03.000 --> 08:08.000
The organization can potentially access when they align themselves to the goal,

08:08.000 --> 08:11.000
culture, and process to the community.

08:12.000 --> 08:19.000
The element is divided into sub-part culture, process, and capabilities.

08:19.000 --> 08:25.000
So the culture, sub-aliment is part of the, is the part that holds the community together.

08:25.000 --> 08:29.000
And it's determined by the number of agreed upon principles.

08:29.000 --> 08:31.000
So, yeah, you can see it here.

08:31.000 --> 08:40.000
Maricrocratic, trust-based governance, and altruistic environment.

08:40.000 --> 08:42.000
Probably not going into that.

08:42.000 --> 08:45.000
So you can ask me later if you want to know more about that.

08:45.000 --> 08:51.000
And the processes, sub-aliment represents a collaborative and distributed development.

08:51.000 --> 08:54.000
And of course, in that occurs in the community.

08:54.000 --> 08:58.000
And there you have a collaborative development.

08:58.000 --> 09:04.000
It illustrates how organization either by taking terms of joint coordinate development

09:04.000 --> 09:06.000
initiative in the community.

09:06.000 --> 09:12.000
So for initiative to occur, one or more members have to take responsibility to push the

09:12.000 --> 09:16.000
change request through the community.

09:16.000 --> 09:18.000
And then we have knowledge creation.

09:18.000 --> 09:22.000
That was another theme we found.

09:22.000 --> 09:28.000
It's a process depicts co-creation and sharing of experience and insights between

09:28.000 --> 09:31.000
members.

09:31.000 --> 09:35.000
The creation of and sharing knowledge can happen in both developer and product

09:35.000 --> 09:37.000
product on the level.

09:37.000 --> 09:39.000
That's what we've seen in this case.

09:39.000 --> 09:43.000
And then you have the software quality insurance and assessment,

09:43.000 --> 09:49.000
which stems from the fact that co-groups the repository is public and open to everyone

09:49.000 --> 09:53.000
and programmer take responsibility professional pride in their work.

09:53.000 --> 09:57.000
So, yeah, that's part of the community engagement.

09:57.000 --> 10:00.000
And let's see if I can see the last one.

10:00.000 --> 10:04.000
And then we have the capability sub element,

10:04.000 --> 10:09.000
which epitomize the technical competence and proficiency in the community,

10:09.000 --> 10:11.000
which you can access.

10:11.000 --> 10:15.000
The talent that the community attracts are related to the personal motivation

10:15.000 --> 10:19.000
and technical problems the community tries to solve.

10:19.000 --> 10:23.000
So this is more, I'm talking about general things here.

10:24.000 --> 10:29.000
So the state of the art technology, the digital technology,

10:29.000 --> 10:33.000
portrays the interest in finding the best possible solution to one

10:33.000 --> 10:35.000
or a set of problems.

10:35.000 --> 10:38.000
And then we have modular and deptable system design.

10:38.000 --> 10:41.000
It's a capability that is too folded.

10:41.000 --> 10:46.000
The first is that open source solutions are made to be more adaptable

10:46.000 --> 10:49.000
and comfortable to suit different use cases.

10:49.000 --> 10:55.000
And the second one is that adaptability comes at an increased

10:55.000 --> 10:58.000
developer cost due to its more flexible design.

10:58.000 --> 11:03.000
And a holistic use case perspective entails a variety of ways

11:03.000 --> 11:06.000
to solve domain business domain problems.

11:06.000 --> 11:09.000
For the members in the community,

11:09.000 --> 11:13.000
this translates to new insights or alternative perspective

11:13.000 --> 11:17.000
on solutions that are both scalable and adoptable.

11:17.000 --> 11:21.000
And then we have the partnership and synergy opportunity,

11:21.000 --> 11:25.000
which portray the possibility to find other members

11:25.000 --> 11:30.000
with similar requirements and form partnership based on trust.

11:30.000 --> 11:35.000
For example, members can form different clusters depending on the region

11:35.000 --> 11:39.000
or continent if it's a global open source community.

11:39.000 --> 11:45.000
And access to global competence pool, which members can utilize here.

11:45.000 --> 11:49.000
And a cumulative competence and experience is access

11:49.000 --> 11:52.000
through documentation, communication channels,

11:52.000 --> 11:56.000
and also prevent members from repeating common mistakes

11:56.000 --> 11:58.000
when they engage in the community.

11:58.000 --> 12:01.000
So that's the model.

12:01.000 --> 12:04.000
So let's see what this implies.

12:04.000 --> 12:06.000
Model implications.

12:16.000 --> 12:20.000
So the model aims to describe the dynamic integration

12:20.000 --> 12:25.000
where organization and community mutually shape each other.

12:25.000 --> 12:30.000
So for organization, adapting their structure,

12:30.000 --> 12:33.000
process, and practice over time to align to the community,

12:33.000 --> 12:36.000
norms, and governance mechanism.

12:36.000 --> 12:42.000
And also the community evolves through a diverse organization interaction

12:42.000 --> 12:46.000
by incorporating different use cases, perspectives,

12:46.000 --> 12:50.000
and expanding its pool of capabilities and resources.

12:50.000 --> 12:59.000
And the engagement opens up for access to state-of-the-art technology

12:59.000 --> 13:02.000
and model design that I showed before,

13:02.000 --> 13:05.000
to fit a wide range of use case scenarios.

13:05.000 --> 13:09.000
And organization that invest sustain resources

13:09.000 --> 13:13.000
and demonstrate loyalty to community objectives,

13:13.000 --> 13:19.000
gain influence, and access to deeper collaboration opportunities.

13:19.000 --> 13:25.000
And let's see, the last exhale, maybe that engagement enables

13:25.000 --> 13:28.000
those access to pool of developer competence,

13:28.000 --> 13:32.000
either within the organization or individual individuals

13:32.000 --> 13:36.000
that can be contracted or funded through community initiatives.

13:37.000 --> 13:42.000
And important here that these talents are probably not easily hired

13:42.000 --> 13:46.000
or recruited nationally, and are not access easily access

13:46.000 --> 13:50.000
if organization is part of the organization.

13:50.000 --> 13:56.000
So this is resources that you can use when you are a member.

13:56.000 --> 14:03.000
So for the next one, let's see, yeah, organization implications.

14:04.000 --> 14:08.000
Yeah, engagement in community can through core involvement,

14:08.000 --> 14:12.000
build the transformative organizational capabilities.

14:12.000 --> 14:16.000
So this pathway requires investment in the developer competence,

14:16.000 --> 14:20.000
allocating sustained resources, and demonstrating commitment

14:20.000 --> 14:24.000
to the community principles.

14:24.000 --> 14:30.000
Let's see, the time, 19 minutes, let's move the evaluation

14:30.000 --> 14:35.000
of the community is a critical preliminary activity,

14:35.000 --> 14:40.000
or organization need to assess not only technical factors,

14:40.000 --> 14:43.000
but also other things such as governance,

14:43.000 --> 14:46.000
maturity, contributor diversity, and alignment

14:46.000 --> 14:51.000
between community objectives and their organization.

14:51.000 --> 14:56.000
And engagement in open source community may manifest as a partial

14:56.000 --> 14:59.000
or department transformation.

14:59.000 --> 15:03.000
This is attractive opportunity for maybe strict structural

15:03.000 --> 15:10.000
rigid organization or traditional organizations.

15:10.000 --> 15:15.000
And yeah, this maybe leads to the road of the digital transformation.

15:15.000 --> 15:23.000
If you're a traditional rigid organization or a pathway to it.

15:23.000 --> 15:28.000
So that we've seen that procuring of the shelf standardized solution.

15:29.000 --> 15:33.000
Does not facilitate knowledge transfer or trigger change in its

15:33.000 --> 15:36.000
to international organizations.

15:36.000 --> 15:40.000
So we see that engagement in the open source community is a

15:40.000 --> 15:45.000
bottom up approach to engage or transform organizations.

15:45.000 --> 15:49.000
Normally a digital transformation is geared from the top,

15:49.000 --> 15:54.000
top down initiative, but we've seen that several organization

15:54.000 --> 15:59.000
that interacts with the community starts to change the

15:59.000 --> 16:03.000
transformation starts in the department and maybe

16:03.000 --> 16:07.000
radiates the other part of the organization.

16:07.000 --> 16:10.000
And let's see, we'll have one more.

16:10.000 --> 16:18.000
Yeah.

16:18.000 --> 16:23.000
So back again, organization need developer competence.

16:23.000 --> 16:26.000
Either they have it in house or they procure it.

16:26.000 --> 16:30.000
You see everything from organization have all the developer teams in

16:30.000 --> 16:36.000
house to other organization, recruiting teams of developers as

16:36.000 --> 16:41.000
call something working either locally or in other locations.

16:41.000 --> 16:46.000
But the minimum was that the organization in this study at least

16:46.000 --> 16:51.000
have project leader or product owner inside in house competence.

16:51.000 --> 16:57.000
And this was seen as important for the industry transfer and

16:57.000 --> 17:03.000
the long-term commitment to the open source community.

17:03.000 --> 17:07.000
And the longer and deeper the better opportunity becomes for

17:07.000 --> 17:12.000
knowledge transfer use case perspective and etc.

17:12.000 --> 17:16.000
And tied to the long-term investment resources is a loyalty

17:16.000 --> 17:19.000
also to the community, which increase influence and access to

17:19.000 --> 17:24.000
deeper collaboration opportunities.

17:24.000 --> 17:26.000
Yeah, and also loyalty culture.

17:26.000 --> 17:28.000
Maybe that doesn't fit all organizations.

17:28.000 --> 17:29.000
Time up.

17:29.000 --> 17:30.000
Okay.

17:30.000 --> 17:31.000
Good.

17:31.000 --> 17:33.000
Okay.

17:33.000 --> 17:36.000
The research project has ended.

17:36.000 --> 17:40.000
So I'm open for questions.

17:40.000 --> 17:45.000
And if somebody has, yeah, if they want to see this study

17:45.000 --> 17:48.000
continues, maybe they can talk to me afterwards.

17:48.000 --> 17:51.000
If they have national funds or European funds because we're

17:51.000 --> 17:54.000
on profit and we're searching for new research projects.

17:54.000 --> 17:55.000
Thank you.