Merge pull request #865 from InnerSourceCommons/Swapping-Yuki-and-Bejamin's-time-slots

Swapping Yuki and Benjamin

Author: CiaraFlanagan

content/en/events/isc-2024.md

@@ -147,14 +147,16 @@ Perhaps the hardest part of making Open Innovation work is overcoming the intern
 In today's rapidly evolving technological landscape, the concept of "empathetic engineering" has emerged as a vital approach for creating more inclusive, user-friendly, and socially responsible products and solutions. InnerSource, the practice of applying open source development principles within an organization, aligns closely with empathetic engineering. Both approaches emphasize collaboration, transparency, and inclusivity. InnerSource fosters a culture where engineers share knowledge, collaborate across teams, and collectively solve problems. This collaborative spirit enhances empathy by exposing engineers to diverse viewpoints and user experiences. In this talk, Brittany Istenes will share how she approaches new projects identified for InnerSource through the empathetic engineering mindset that creates strong, sustainable and secure InnerSource projects.
       </div>
   </td>
-      <td class="author"> <b><a href="#Benjamin_Ihrig">Benjamin Ihrig</a></b> (SAP SE)<br>
-    Repository Linter@SAP 
-   <span onClick="toggleAbstract('Benjamin_Ihrig_abstract')" class="abstract-toggle">(<a id="Benjamin_Ihrig-link">Show Abstract</a>)</span>
-      <div style="display:none" class="abstract" id=Benjamin_Ihrig_abstract>
-
-At SAP, InnerSource practices are increasingly becoming adopted as an essential part of our software development process, promoting collaboration, innovation and efficient code reuse. Ensuring consistency and quality across numerous repositories is challenging. To address this, we built an internal repository linter to standardize configurations and InnerSource-relevant content, while also providing automated fixes for detected issues. This session will share our journey of developing and piloting this tool to enhance repository quality and uniformity. Participants will gain insights into the rationale behind the linter, its implementation and the standards it aims to enforce.    
+      <td class="author"> <b><a href="#yuki_hattori">Yuki Hattori</a></b> (GitHub)<br>
+   The Importance of InnerSource in the AI Era
+    <span onClick="toggleAbstract('yuki_hattori_abstract')" class="abstract-toggle">(<a id="yuki_hattori-link">Show Abstract</a>)</span>
+      <div style="display:none" class="abstract" id="yuki_hattori_abstract">
+            
+In the rapidly evolving landscape of software development, your organization may already be experiencing enhanced developer productivity through AI-powered coding tools like GitHub Copilot. As AI continues to advance, one key trend is personalization. It's natural to desire an AI that intimately understands your codebase. To achieve this, source code for fine-tuning and RAG (Retrieval-Augmented Generation) becomes crucial. When considering the characteristics of code ideal for AI to feed, certain traits emerge: usability at an enterprise scale; openness and accessibility to AI, being well-maintained and easily comprehensible and lastly, being well-documented.
+Upon reflection, you'll realize these are precisely the hallmarks of open-source code. However, code with these open-source-like qualities doesn't naturally arise within corporate environments. Such code isn't merely a "product" but a manifestation of culture. Ask yourself: Is your code confined to specific projects? Is it consistently maintained? Is it written to be universally understandable? If not, now is the time to start cultivating these practices. Waiting to prepare your codebase for AI enhancement three years from now may be too late. 
+This session will provide valuable insights and strategies to prepare your organization for the AI-driven future of software development. We'll explore how adopting InnerSource principles can create a codebase that's not only more efficient and collaborative today but also primed for AI augmentation tomorrow. Join us to learn how to position your organization at the forefront of the AI revolution in software development through the power of InnerSource.   
 </div>
-     </td>
+      </td>
 
   </tr>
 
@@ -223,16 +225,14 @@ This talk will discuss how OpenChain ISO/IEC 5230 (the international standard fo
 
  <tr>
         <td class="time">UTC 17:35 – 18:00</td>
-      <td class="author"> <b><a href="#yuki_hattori">Yuki Hattori</a></b> (GitHub)<br>
-   The Importance of InnerSource in the AI Era
-    <span onClick="toggleAbstract('yuki_hattori_abstract')" class="abstract-toggle">(<a id="yuki_hattori-link">Show Abstract</a>)</span>
-      <div style="display:none" class="abstract" id="yuki_hattori_abstract">
-            
-In the rapidly evolving landscape of software development, your organization may already be experiencing enhanced developer productivity through AI-powered coding tools like GitHub Copilot. As AI continues to advance, one key trend is personalization. It's natural to desire an AI that intimately understands your codebase. To achieve this, source code for fine-tuning and RAG (Retrieval-Augmented Generation) becomes crucial. When considering the characteristics of code ideal for AI to feed, certain traits emerge: usability at an enterprise scale; openness and accessibility to AI, being well-maintained and easily comprehensible and lastly, being well-documented.
-Upon reflection, you'll realize these are precisely the hallmarks of open-source code. However, code with these open-source-like qualities doesn't naturally arise within corporate environments. Such code isn't merely a "product" but a manifestation of culture. Ask yourself: Is your code confined to specific projects? Is it consistently maintained? Is it written to be universally understandable? If not, now is the time to start cultivating these practices. Waiting to prepare your codebase for AI enhancement three years from now may be too late. 
-This session will provide valuable insights and strategies to prepare your organization for the AI-driven future of software development. We'll explore how adopting InnerSource principles can create a codebase that's not only more efficient and collaborative today but also primed for AI augmentation tomorrow. Join us to learn how to position your organization at the forefront of the AI revolution in software development through the power of InnerSource.   
+      <td class="author"> <b><a href="#Benjamin_Ihrig">Benjamin Ihrig</a></b> (SAP SE)<br>
+    Repository Linter@SAP 
+   <span onClick="toggleAbstract('Benjamin_Ihrig_abstract')" class="abstract-toggle">(<a id="Benjamin_Ihrig-link">Show Abstract</a>)</span>
+      <div style="display:none" class="abstract" id=Benjamin_Ihrig_abstract>
+
+At SAP, InnerSource practices are increasingly becoming adopted as an essential part of our software development process, promoting collaboration, innovation and efficient code reuse. Ensuring consistency and quality across numerous repositories is challenging. To address this, we built an internal repository linter to standardize configurations and InnerSource-relevant content, while also providing automated fixes for detected issues. This session will share our journey of developing and piloting this tool to enhance repository quality and uniformity. Participants will gain insights into the rationale behind the linter, its implementation and the standards it aims to enforce.    
 </div>
-      </td>
+     </td>
       <td class="author"> <b><a href="#Joachim_de_Lezardiere">Joachim de Lezardiere</a></b> (Lenstra)& <b>Carole Ciboire Daghfal</b> (Kering)<br>
       Enabling Data Mesh in Large Organizations with InnerSource
     <span onClick="toggleAbstract('Joachim_de_Lezardiere_abstract')" class="abstract-toggle">(<a id="Joachim_de_Lezardiere_link">Show Abstract</a>)</span>