Skip to content

Commit 2c6882d

Browse files
deploy: 9ab9266
1 parent b913837 commit 2c6882d

4 files changed

Lines changed: 48 additions & 48 deletions

File tree

events/isc-2025/index.html

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1416,13 +1416,11 @@ <h3>Berlin</h3>
14161416
</tr>
14171417
<tr>
14181418
<td class="time">11:00 - 11:30</td>
1419-
<td class="author w-70"> <b><a href="#Wolfgang_Gehring">Dr. Wolfgang Gehring </a>and </a><a href="#Sim_Kolamkanni">Sim Daniel Kolamkanni </a></b>- Virtual Session<br>(Mercedes-Benz Tech Innovation GmbH / Mercedes-Benz Research and Development India)<br>
1420-
A Frictionless Inner Source Journey
1421-
<span onClick="toggleAbstract('Wolfgang_Gehring_abstract')" class="abstract-toggle">(<a id="Wolfgang_Gehring-link">Show Abstract</a>)</span>
1422-
<div style="display:none" class="abstract" id=Wolfgang_Gehring_abstract>
1423-
<p>For Inner Source to thrive and gain contributors, we need to make the experience as frictionless as possible. Often, we have built large frameworks around Inner Source with the intention of maximizing safety and governance, but these frameworks can inadvertently create unintended obstacles for potential contributors.<br>
1424-
Let me share with you how we can address this challenge. We assessed the full process for contributing to Inner Source within our company, including all requirements and necessary actions. We analyzed and measured where people spend time in the process, and then came up with suggestions for cutting the red tape and for automating compliance topics.<br>
1425-
Finally, for a smooth Inner Source journey, also from an individual project perspective, we need to make it as easy as possible to contribute. I’ll share some examples and suggestions here which can serve as a model for achieving this.</p>
1419+
<td class="author w-70"> <b><a href="#Clare_Dillon">Clare Dillon </a></b>- Virtual Session<br>(CURIOSS)<br>
1420+
State of InnerSource 2025
1421+
<span onClick="toggleAbstract('Clare_Dillon_abstract')" class="abstract-toggle">(<a id="Clare_Dillon-link">Show Abstract</a>)</span>
1422+
<div style="display:none" class="abstract" id=Clare_Dillon_abstract>
1423+
<p>Each year InnerSource Commons releases a State of InnerSource report. Come along to this talk to be the first to hear about the latest status and trends in the InnerSource world. This year we will have an even more global representation in the dataset, with the survey localized for our Japanese and Brazilian communities. For 2025, we have also dug a little deeper into the benefits and blockers InnerSource teams are experiencing, and will share more details about what open source practices they are engaged in. Come along and be part of the conversation shaping the future of InnerSource and see how our global community is learning and growing together.</p>
14261424
<td class="UTC">UTC 10:00</td>
14271425
</div>
14281426
</td>
@@ -1459,11 +1457,13 @@ <h3>Berlin</h3>
14591457
</tr>
14601458
<tr>
14611459
<td class="time">12:30 - 13:00</td>
1462-
<td class="author w-70"> <b><a href="#Clare_Dillon">Clare Dillon </a></b><br>(CURIOSS)<br>
1463-
State of InnerSource 2025
1464-
<span onClick="toggleAbstract('Clare_Dillon_abstract')" class="abstract-toggle">(<a id="Clare_Dillon-link">Show Abstract</a>)</span>
1465-
<div style="display:none" class="abstract" id=Clare_Dillon_abstract>
1466-
<p>Each year InnerSource Commons releases a State of InnerSource report. Come along to this talk to be the first to hear about the latest status and trends in the InnerSource world. This year we will have an even more global representation in the dataset, with the survey localized for our Japanese and Brazilian communities. For 2025, we have also dug a little deeper into the benefits and blockers InnerSource teams are experiencing, and will share more details about what open source practices they are engaged in. Come along and be part of the conversation shaping the future of InnerSource and see how our global community is learning and growing together.</p>
1460+
<td class="author w-70"> <b><a href="#Wolfgang_Gehring">Dr. Wolfgang Gehring </a>and </a><a href="#Sim_Kolamkanni">Sim Daniel Kolamkanni </a></b><br>(Mercedes-Benz Tech Innovation GmbH / Mercedes-Benz Research and Development India)<br>
1461+
A Frictionless Inner Source Journey
1462+
<span onClick="toggleAbstract('Wolfgang_Gehring_abstract')" class="abstract-toggle">(<a id="Wolfgang_Gehring-link">Show Abstract</a>)</span>
1463+
<div style="display:none" class="abstract" id=Wolfgang_Gehring_abstract>
1464+
<p>For Inner Source to thrive and gain contributors, we need to make the experience as frictionless as possible. Often, we have built large frameworks around Inner Source with the intention of maximizing safety and governance, but these frameworks can inadvertently create unintended obstacles for potential contributors.<br>
1465+
Let me share with you how we can address this challenge. We assessed the full process for contributing to Inner Source within our company, including all requirements and necessary actions. We analyzed and measured where people spend time in the process, and then came up with suggestions for cutting the red tape and for automating compliance topics.<br>
1466+
Finally, for a smooth Inner Source journey, also from an individual project perspective, we need to make it as easy as possible to contribute. I’ll share some examples and suggestions here which can serve as a model for achieving this.</p>
14671467
<td class="UTC">UTC 11:30</td>
14681468
</div>
14691469
</td>

fr/events/isc-2025/index.html

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1405,13 +1405,11 @@ <h3>Berlin</h3>
14051405
</tr>
14061406
<tr>
14071407
<td class="time">11:00 - 11:30</td>
1408-
<td class="author w-70"> <b><a href="#Wolfgang_Gehring">Dr. Wolfgang Gehring </a>and </a><a href="#Sim_Kolamkanni">Sim Daniel Kolamkanni </a></b>- Virtual Session<br>(Mercedes-Benz Tech Innovation GmbH / Mercedes-Benz Research and Development India)<br>
1409-
A Frictionless Inner Source Journey
1410-
<span onClick="toggleAbstract('Wolfgang_Gehring_abstract')" class="abstract-toggle">(<a id="Wolfgang_Gehring-link">Show Abstract</a>)</span>
1411-
<div style="display:none" class="abstract" id=Wolfgang_Gehring_abstract>
1412-
<p>For Inner Source to thrive and gain contributors, we need to make the experience as frictionless as possible. Often, we have built large frameworks around Inner Source with the intention of maximizing safety and governance, but these frameworks can inadvertently create unintended obstacles for potential contributors.<br>
1413-
Let me share with you how we can address this challenge. We assessed the full process for contributing to Inner Source within our company, including all requirements and necessary actions. We analyzed and measured where people spend time in the process, and then came up with suggestions for cutting the red tape and for automating compliance topics.<br>
1414-
Finally, for a smooth Inner Source journey, also from an individual project perspective, we need to make it as easy as possible to contribute. I’ll share some examples and suggestions here which can serve as a model for achieving this.</p>
1408+
<td class="author w-70"> <b><a href="#Clare_Dillon">Clare Dillon </a></b>- Virtual Session<br>(CURIOSS)<br>
1409+
State of InnerSource 2025
1410+
<span onClick="toggleAbstract('Clare_Dillon_abstract')" class="abstract-toggle">(<a id="Clare_Dillon-link">Show Abstract</a>)</span>
1411+
<div style="display:none" class="abstract" id=Clare_Dillon_abstract>
1412+
<p>Each year InnerSource Commons releases a State of InnerSource report. Come along to this talk to be the first to hear about the latest status and trends in the InnerSource world. This year we will have an even more global representation in the dataset, with the survey localized for our Japanese and Brazilian communities. For 2025, we have also dug a little deeper into the benefits and blockers InnerSource teams are experiencing, and will share more details about what open source practices they are engaged in. Come along and be part of the conversation shaping the future of InnerSource and see how our global community is learning and growing together.</p>
14151413
<td class="UTC">UTC 10:00</td>
14161414
</div>
14171415
</td>
@@ -1448,11 +1446,13 @@ <h3>Berlin</h3>
14481446
</tr>
14491447
<tr>
14501448
<td class="time">12:30 - 13:00</td>
1451-
<td class="author w-70"> <b><a href="#Clare_Dillon">Clare Dillon </a></b><br>(CURIOSS)<br>
1452-
State of InnerSource 2025
1453-
<span onClick="toggleAbstract('Clare_Dillon_abstract')" class="abstract-toggle">(<a id="Clare_Dillon-link">Show Abstract</a>)</span>
1454-
<div style="display:none" class="abstract" id=Clare_Dillon_abstract>
1455-
<p>Each year InnerSource Commons releases a State of InnerSource report. Come along to this talk to be the first to hear about the latest status and trends in the InnerSource world. This year we will have an even more global representation in the dataset, with the survey localized for our Japanese and Brazilian communities. For 2025, we have also dug a little deeper into the benefits and blockers InnerSource teams are experiencing, and will share more details about what open source practices they are engaged in. Come along and be part of the conversation shaping the future of InnerSource and see how our global community is learning and growing together.</p>
1449+
<td class="author w-70"> <b><a href="#Wolfgang_Gehring">Dr. Wolfgang Gehring </a>and </a><a href="#Sim_Kolamkanni">Sim Daniel Kolamkanni </a></b><br>(Mercedes-Benz Tech Innovation GmbH / Mercedes-Benz Research and Development India)<br>
1450+
A Frictionless Inner Source Journey
1451+
<span onClick="toggleAbstract('Wolfgang_Gehring_abstract')" class="abstract-toggle">(<a id="Wolfgang_Gehring-link">Show Abstract</a>)</span>
1452+
<div style="display:none" class="abstract" id=Wolfgang_Gehring_abstract>
1453+
<p>For Inner Source to thrive and gain contributors, we need to make the experience as frictionless as possible. Often, we have built large frameworks around Inner Source with the intention of maximizing safety and governance, but these frameworks can inadvertently create unintended obstacles for potential contributors.<br>
1454+
Let me share with you how we can address this challenge. We assessed the full process for contributing to Inner Source within our company, including all requirements and necessary actions. We analyzed and measured where people spend time in the process, and then came up with suggestions for cutting the red tape and for automating compliance topics.<br>
1455+
Finally, for a smooth Inner Source journey, also from an individual project perspective, we need to make it as easy as possible to contribute. I’ll share some examples and suggestions here which can serve as a model for achieving this.</p>
14561456
<td class="UTC">UTC 11:30</td>
14571457
</div>
14581458
</td>

ja/events/isc-2025/index.html

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1405,13 +1405,11 @@ <h3>Berlin</h3>
14051405
</tr>
14061406
<tr>
14071407
<td class="time">11:00 - 11:30</td>
1408-
<td class="author w-70"> <b><a href="#Wolfgang_Gehring">Dr. Wolfgang Gehring </a>and </a><a href="#Sim_Kolamkanni">Sim Daniel Kolamkanni </a></b>- Virtual Session<br>(Mercedes-Benz Tech Innovation GmbH / Mercedes-Benz Research and Development India)<br>
1409-
A Frictionless Inner Source Journey
1410-
<span onClick="toggleAbstract('Wolfgang_Gehring_abstract')" class="abstract-toggle">(<a id="Wolfgang_Gehring-link">Show Abstract</a>)</span>
1411-
<div style="display:none" class="abstract" id=Wolfgang_Gehring_abstract>
1412-
<p>For Inner Source to thrive and gain contributors, we need to make the experience as frictionless as possible. Often, we have built large frameworks around Inner Source with the intention of maximizing safety and governance, but these frameworks can inadvertently create unintended obstacles for potential contributors.<br>
1413-
Let me share with you how we can address this challenge. We assessed the full process for contributing to Inner Source within our company, including all requirements and necessary actions. We analyzed and measured where people spend time in the process, and then came up with suggestions for cutting the red tape and for automating compliance topics.<br>
1414-
Finally, for a smooth Inner Source journey, also from an individual project perspective, we need to make it as easy as possible to contribute. I’ll share some examples and suggestions here which can serve as a model for achieving this.</p>
1408+
<td class="author w-70"> <b><a href="#Clare_Dillon">Clare Dillon </a></b>- Virtual Session<br>(CURIOSS)<br>
1409+
State of InnerSource 2025
1410+
<span onClick="toggleAbstract('Clare_Dillon_abstract')" class="abstract-toggle">(<a id="Clare_Dillon-link">Show Abstract</a>)</span>
1411+
<div style="display:none" class="abstract" id=Clare_Dillon_abstract>
1412+
<p>Each year InnerSource Commons releases a State of InnerSource report. Come along to this talk to be the first to hear about the latest status and trends in the InnerSource world. This year we will have an even more global representation in the dataset, with the survey localized for our Japanese and Brazilian communities. For 2025, we have also dug a little deeper into the benefits and blockers InnerSource teams are experiencing, and will share more details about what open source practices they are engaged in. Come along and be part of the conversation shaping the future of InnerSource and see how our global community is learning and growing together.</p>
14151413
<td class="UTC">UTC 10:00</td>
14161414
</div>
14171415
</td>
@@ -1448,11 +1446,13 @@ <h3>Berlin</h3>
14481446
</tr>
14491447
<tr>
14501448
<td class="time">12:30 - 13:00</td>
1451-
<td class="author w-70"> <b><a href="#Clare_Dillon">Clare Dillon </a></b><br>(CURIOSS)<br>
1452-
State of InnerSource 2025
1453-
<span onClick="toggleAbstract('Clare_Dillon_abstract')" class="abstract-toggle">(<a id="Clare_Dillon-link">Show Abstract</a>)</span>
1454-
<div style="display:none" class="abstract" id=Clare_Dillon_abstract>
1455-
<p>Each year InnerSource Commons releases a State of InnerSource report. Come along to this talk to be the first to hear about the latest status and trends in the InnerSource world. This year we will have an even more global representation in the dataset, with the survey localized for our Japanese and Brazilian communities. For 2025, we have also dug a little deeper into the benefits and blockers InnerSource teams are experiencing, and will share more details about what open source practices they are engaged in. Come along and be part of the conversation shaping the future of InnerSource and see how our global community is learning and growing together.</p>
1449+
<td class="author w-70"> <b><a href="#Wolfgang_Gehring">Dr. Wolfgang Gehring </a>and </a><a href="#Sim_Kolamkanni">Sim Daniel Kolamkanni </a></b><br>(Mercedes-Benz Tech Innovation GmbH / Mercedes-Benz Research and Development India)<br>
1450+
A Frictionless Inner Source Journey
1451+
<span onClick="toggleAbstract('Wolfgang_Gehring_abstract')" class="abstract-toggle">(<a id="Wolfgang_Gehring-link">Show Abstract</a>)</span>
1452+
<div style="display:none" class="abstract" id=Wolfgang_Gehring_abstract>
1453+
<p>For Inner Source to thrive and gain contributors, we need to make the experience as frictionless as possible. Often, we have built large frameworks around Inner Source with the intention of maximizing safety and governance, but these frameworks can inadvertently create unintended obstacles for potential contributors.<br>
1454+
Let me share with you how we can address this challenge. We assessed the full process for contributing to Inner Source within our company, including all requirements and necessary actions. We analyzed and measured where people spend time in the process, and then came up with suggestions for cutting the red tape and for automating compliance topics.<br>
1455+
Finally, for a smooth Inner Source journey, also from an individual project perspective, we need to make it as easy as possible to contribute. I’ll share some examples and suggestions here which can serve as a model for achieving this.</p>
14561456
<td class="UTC">UTC 11:30</td>
14571457
</div>
14581458
</td>

0 commit comments

Comments
 (0)