Internal Open Source
[[3. Resources/Readwise/Full Document Contents/Articles/Internal Open Source|Full Document Contents]]
## Document Notes
1. What are the benefits of using Internal Open Source?
2. How can teams join forces and work fearlessly while still maintaining their own priorities?
3. What challenges have been faced by teams when attempting to collaborate on projects?
Internal Open Source (Inner Source) is a technique that can be used to enhance collaboration between teams within a company. It follows an Open Source contributor focused approach, allowing teams to join forces during their work and pursue their goals without the need for full alignment in priorities with other teams. This can help prevent duplication of efforts and frustration caused by cross-team dependencies.
> [!note]+ Document Notes
> 1. What are the benefits of using Internal Open Source?
> 2. How can teams join forces and work fearlessly while still maintaining their own priorities?
> 3. What challenges have been faced by teams when attempting to collaborate on projects?
>
> Internal Open Source (Inner Source) is a technique that can be used to enhance collaboration between teams within a company. It follows an Open Source contributor focused approach, allowing teams to join forces during their work and pursue their goals without the need for full alignment in priorities with other teams. This can help prevent duplication of efforts and frustration caused by cross-team dependencies.
## Highlights
- • 00:05
Great. Good morning,
Discard Save
• 00:07
good afternoon, good night.
Discard Save
• 00:08
Depending where you are and
Discard Save
• 00:10
what time you're watching this,
Discard Save
• 00:11
my name is stable and I'm
Discard Save
• 00:14
here today with as of now,
Discard Save
• 00:16
121 of you and Stephen Feltner.
Discard Save
• 00:18
And the main idea for this session
Discard Save
• 00:20
is that the tech radar Tuesdays
Discard Save
• 00:22
is for us to go over some of the
Discard Save
• 00:24
adopt items on the tech radar.
Discard Save
• 00:26
And today we're going to discuss about
Discard Save
• 00:28
a technique that's very close to my
Discard Save
• 00:30
heart and that's internal open source.
Discard Save
• 00:32
So they structure for these
Discard Save
• 00:34
calls are fairly simple.
Discard Save
• 00:35
The presenter has about 10 to 15
Discard Save
• 00:38
minutes to go over the subject and
Discard Save
• 00:40
then we open up for questions.
Discard Save
• 00:42
The questions will be taken here on zoom via. ([View Highlight](https://read.readwise.io/read/01grrrtdk73bgnk0y5813hs5m7))
- • 30:39
but you're probably going to get a lot
Discard Save
• 30:41
faster if you contribute it into them then
Discard Save
• 30:44
waiting on them to deliver it for you.
Discard Save
• 30:46
And unfortunately it's a balancing
Discard Save
• 30:48
act and it's we just haven't
Discard Save
• 30:51
found that balance point yet.
Discard Save
• 30:53
Excellent.
Discard Save
• 30:53
We over time thank you everyone
Discard Save
• 30:56
for your questions.
Discard Save
• 30:57
And we're going to be meeting February 14,
Discard Save
• 30:59
so in seven days from now to talk
Discard Save
• 31:02
about data platform with Ankit.
Discard Save
• 31:04
By all means, help us contribute to their
Discard Save
• 31:06
creator and all contributors are welcome.
Discard Save
• 31:08
Steven, thank you very much.
Discard Save
• 31:10
This is a very engaging discussion.
Discard Save
• 31:12
Thank you all for attending and
Discard Save
• 31:14
see you next week.
Discard Save
• 31:16
Thank you, Steven.
Discard Save
• 31:17
Thanks all. ([View Highlight](https://read.readwise.io/read/01grrrvwz8v79hyky4hr7azrwz))
- As a growing company with a myriad of teams, we have grown a massive repository of code projects. In many cases, these projects have been created by individual teams, solely for their own consumption. Because of this, there have been many cases of duplicated efforts, where multiple teams build their own tools to be used toward the same purpose. In other cases, when there are cross-team dependencies, a sense of frustration can arise when priorities are not aligned between teams. One team may request a new feature from another, but because the feature is not a high priority on the other team’s roadmap, it will not get implemented as quickly as the first team would like.
Internal Open Source, also known as Inner Source, is a technique by which we can enhance collaboration between groups and teams in the company. By approaching strategic internal projects with the same contributor focused methodology we apply to Open Source projects, teams can more effectively Join Forces during the normal course of their work. They can continue to Work Fearlessly in the pursuit of their team goals, without the concern of their own priorities having to be fully aligned with those of another team. ([View Highlight](https://read.readwise.io/read/01grrsgfx661c8nnp861pgg002))