Skip to content

Commit 45a8bff

Browse files
authored
Merge pull request #1252 from InnerSourceCommons/summit-2026-panel-hour
Summit 2026: make the Border Is Porous panel an hour and drop the 20-hour wording
2 parents 1920c9e + bb65031 commit 45a8bff

1 file changed

Lines changed: 15 additions & 15 deletions

File tree

‎content/en/events/isc-2026.md‎

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ JavaScript is disabled. Please
2828
</div>
2929
<br />
3030

31-
On Thursday, November 12th, InnerSource Summit 2026 will unite the global InnerSource community online for a 20-hour, around-the-world event spanning every timezone! We will be featuring the industry's top speakers, inspiring stories, and cutting-edge ideas shaping the future of collaborative software development.
31+
On Thursday, November 12th, InnerSource Summit 2026 will unite the global InnerSource community online for an around-the-world event spanning every timezone! We will be featuring the industry's top speakers, inspiring stories, and cutting-edge ideas shaping the future of collaborative software development.
3232
<br />
3333
<br />
3434
Discover the Power of InnerSource!
@@ -658,7 +658,7 @@ The discussion will also tackle the difficult questions: When should an organiza
658658

659659

660660
<tr>
661-
<td class="time">14:00 EST</td>
661+
<td class="time">14:30 EST</td>
662662
<td class="author w-70"> <b><a href="#Guilherme_Dellagustin">Guilherme Dellagustin </a></b><br>(SAP SE)<br>
663663
InnerSource in the age of AI: Challenges and Opportunities
664664
<span onClick="toggleAbstract('Guilherme_Dellagustin_abstract')" class="abstract-toggle">(<a id="Guilherme_Dellagustin-link">Show Abstract</a>)</span>
@@ -671,15 +671,15 @@ Everyone can "vibe-code/create" their own solutions now, does this mean reuse is
671671
The bar for contributing to other projects has been lowered, but what does this mean for maintainers?
672672

673673
In this talk a seasoned InnerSource Officer will bring food for thought on how AI can impact the collaboration style prescribed by InnerSource, for the best of for the worst, and share ideas on how to navigate this ever-changing terrain. We will also look into intrinsic benefits we expect to have with AI, but also, where a human push is still needed.
674-
<td class="UTC">UTC 18:00</td>
674+
<td class="UTC">UTC 18:30</td>
675675
</div>
676676
</td>
677677

678678

679679
</tr>
680680

681681
<tr>
682-
<td class="time">14:30 EST</td>
682+
<td class="time">15:00 EST</td>
683683
<td class="author w-70"> <b><a href="#Brittany_Istenes">Brittany Istenes </a></b><br>(Independent)<br>
684684
Don't Just Adopt AI. InnerSource It
685685
<span onClick="toggleAbstract('Brittany_Istenes_abstract')" class="abstract-toggle">(<a id="Brittany_Istenes-link">Show Abstract</a>)</span>
@@ -688,15 +688,15 @@ In this talk a seasoned InnerSource Officer will bring food for thought on how A
688688
What if scaling AI isn't really about adoption, but about what a community creates once people start using it together? Within a large U.S.-based financial services firm, 94% GitHub Copilot adoption and 78% agent-written code were only part of the story. The bigger outcome was turning individual experimentation into repeatable, discoverable patterns through shared skills, prompt, and harness libraries.
689689

690690
By applying InnerSource principles alongside grassroots engagement, storytelling, and community building, teams could contribute what worked, learn from one another, and build on proven approaches instead of continually starting from scratch. This session explores how AI adoption became a catalyst for a shared collective of knowledge—and how measuring reuse, contribution, and impact can tell a much more meaningful story than adoption alone.
691-
<td class="UTC">UTC 18:30</td>
691+
<td class="UTC">UTC 19:00</td>
692692
</div>
693693
</td>
694694

695695

696696
</tr>
697697

698698
<tr>
699-
<td class="time">15:00 EST</td>
699+
<td class="time">15:30 EST</td>
700700
<td class="author w-70"> <b><a href="#Isaac_Johnson">Isaac Johnson </a></b><br>(Abbott)<br>
701701
Democratizing GenAI with Skills and MCP
702702
<span onClick="toggleAbstract('Isaac_Johnson_abstract')" class="abstract-toggle">(<a id="Isaac_Johnson-link">Show Abstract</a>)</span>
@@ -709,14 +709,14 @@ We'll cover what Skills and MCP servers are. How to create them (with some simpl
709709
Attendees should walk away with a good handle on how to make a skill and MCP server, and when. More importantly, how we can reliably share with easy to maintain repositories in GIT.
710710

711711
The sharing aspect of skills truly leads to democratization of Gen AI improvements and drives at the core of Inner Sourcing.
712-
<td class="UTC">UTC 19:00</td>
712+
<td class="UTC">UTC 19:30</td>
713713
</div>
714714
</td>
715715

716716

717717
</tr>
718718
<tr>
719-
<td class="time">15:30 EST</td>
719+
<td class="time">16:00 EST</td>
720720
<td class="author w-70"> <b><a href="#Dave_Nielsen">Dave Nielsen </a></b><br>(Cognee)<br>
721721
Introduction to Company Brain
722722
<span onClick="toggleAbstract('Dave_Nielsen_abstract')" class="abstract-toggle">(<a id="Dave_Nielsen-link">Show Abstract</a>)</span>
@@ -734,13 +734,13 @@ Preliminary session outline:
734734
3. How do you get started? Choose one measurable use case, connect a small set of authoritative information sources, define access and ownership rules, launch a simple question-and-answer experience, and create a feedback loop that turns unanswered questions into durable organizational knowledge.
735735
4. How do you measure success? Track faster answers, increased project reuse, greater contributor participation, fewer repeated questions, and less time spent locating information or experts.
736736

737-
<td class="UTC">UTC 19:30</td>
737+
<td class="UTC">UTC 20:00</td>
738738
</div>
739739
</td>
740740

741741
</tr>
742742
<tr>
743-
<td class="time">16:00 EST/td>
743+
<td class="time">16:30 EST</td>
744744
<td class="author w-70"> <b><a href="#Fei_Wan">Fei Wan</a></b><br>(Comcast)<br>
745745
The Next Wave of InnerSource: From Code Reuse to Agent Reuse
746746
<span onClick="toggleAbstract('Fei_Wan_abstract')" class="abstract-toggle">(<a id="Fei_Wan-link">Show Abstract</a>)</span>
@@ -755,14 +755,14 @@ This talk explores the next frontier of InnerSource: the shift from sharing code
755755
What happens when expertise can be discovered, reused, improved, and composed like software?
756756

757757
The next wave of InnerSource isn't about code reuse. It's about agent reuse.
758-
<td class="UTC">UTC 20:00</td>
758+
<td class="UTC">UTC 20:30</td>
759759
</div>
760760
</td>
761761

762762

763763
</tr>
764764
<tr>
765-
<td class="time">16:30 EST</td>
765+
<td class="time">17:00 EST</td>
766766
<td class="author w-70"> <b><a href="#Shruti_Bist">Shruti Bist </a></b><br>(Independent)<br>
767767
Beyond Code: Applying InnerSource Principles to Privacy Compliance
768768
<span onClick="toggleAbstract('Shruti_Bist_abstract')" class="abstract-toggle">(<a id="Shruti_Bist-link">Show Abstract</a>)</span>
@@ -771,13 +771,13 @@ The next wave of InnerSource isn't about code reuse. It's about agent reuse.
771771
InnerSource is often associated with opening source code internally so that teams can discover, reuse and contribute to each other's work. But in enterprise software, source code is only one part of what teams need to build and operate a product. There is also a lot of knowledge around privacy, security, compliance, architecture and operational practices that can be difficult for other teams to discover and reuse.
772772

773773
I have seen this challenge firsthand in privacy engineering. A product may be considered compliant with a privacy requirement, but when a customer, auditor or internal stakeholder asks, "How?", finding the answer can be much harder. The information may be spread across product documentation, architecture decisions, privacy assessments and the people who have worked on the product. This talk explores whether we can apply InnerSource principles such as transparency, discoverability, reuse and contribution to this problem. What if contributors were expected not only to contribute code, but also to make the privacy implications of their work and the "how" behind compliance understandable and discoverable? I will share some ideas for what an InnerSource approach to privacy compliance could look like and invite the community to think about where else InnerSource can go beyond code.
774-
<td class="UTC">UTC 20:30</td>
774+
<td class="UTC">UTC 21:00</td>
775775
</div>
776776
</td>
777777
</tr>
778778

779779
<tr>
780-
<td class="time">17:00 EST</td>
780+
<td class="time">17:30 EST</td>
781781
<td class="author w-70"> <b><a href="#Scott_Hanselman">Scott Hanselman</a></b><br>(Microsoft/GitHub)<br>
782782
What do you build when you can build anything?
783783
<span onClick="toggleAbstract('Scott_Hanselman_abstract')" class="abstract-toggle">(<a id="Scott_Hanselman-link">Show Abstract</a>)</span>
@@ -788,7 +788,7 @@ For most of computing history, building software meant negotiating with scarcity
788788
But when you can build almost anything, the hardest question is no longer *how*. It is *what...and why*.
789789

790790
In this keynote, Scott Hanselman explores what happens when creation becomes abundant. Through stories, code, and practical examples, he examines the new skills that matter: judgment, taste, curiosity, empathy, and the discipline to understand the problem before generating the solution. The future will not belong simply to those who can build the most. It will belong to those who choose carefully, build responsibly, and create things genuinely worth having together.
791-
<td class="UTC">UTC 21:00</td>
791+
<td class="UTC">UTC 21:30</td>
792792
</div>
793793
</td>
794794

0 commit comments

Comments
 (0)