Merge pull request #1115 from InnerSourceCommons/swapping-Clare-and-Wolfgang-in-Berlin

swapping Clare and Wolfgang

Author: andrea-kyurchiev

content/en/events/isc-2025.md

@@ -420,14 +420,12 @@ InnerSource is often seen as a way to improve software development, but its pote
  </tr>
  <tr>
        <td class="time">11:00 - 11:30</td>
-  <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>
-   A Frictionless Inner Source Journey
-  <span onClick="toggleAbstract('Wolfgang_Gehring_abstract')" class="abstract-toggle">(<a id="Wolfgang_Gehring-link">Show Abstract</a>)</span>
-    <div style="display:none" class="abstract" id=Wolfgang_Gehring_abstract>
+   <td class="author w-70"> <b><a href="#Clare_Dillon">Clare Dillon </a></b>- Virtual Session<br>(CURIOSS)<br>
+   State of InnerSource 2025
+  <span onClick="toggleAbstract('Clare_Dillon_abstract')" class="abstract-toggle">(<a id="Clare_Dillon-link">Show Abstract</a>)</span>
+    <div style="display:none" class="abstract" id=Clare_Dillon_abstract>
 
-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.  
-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.  
-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.
+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.
 <td class="UTC">UTC 10:00</td>
      </div>
  </td>
@@ -472,12 +470,14 @@ We will cover how to:
  </tr>
  <tr>
        <td class="time">12:30 - 13:00</td>
-  <td class="author w-70"> <b><a href="#Clare_Dillon">Clare Dillon </a></b><br>(CURIOSS)<br>
-   State of InnerSource 2025
-  <span onClick="toggleAbstract('Clare_Dillon_abstract')" class="abstract-toggle">(<a id="Clare_Dillon-link">Show Abstract</a>)</span>
-    <div style="display:none" class="abstract" id=Clare_Dillon_abstract>
+  <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>
+   A Frictionless Inner Source Journey
+  <span onClick="toggleAbstract('Wolfgang_Gehring_abstract')" class="abstract-toggle">(<a id="Wolfgang_Gehring-link">Show Abstract</a>)</span>
+    <div style="display:none" class="abstract" id=Wolfgang_Gehring_abstract>
 
-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.
+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.  
+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.  
+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.
 <td class="UTC">UTC 11:30</td>
      </div>
  </td>