Merge branch 'main' into promote-governance-levels

Author: spier

README.md

@@ -92,6 +92,7 @@ Our mission
 * [InnerSource Ambassadors](/patterns/1-initial/innersource-ambassador.md) - *When driving InnerSource adoption through a large, decentralized organization it is hard to understand and address the local challenges that come up in different departments and regions. Local volunteers, called InnerSource Ambassadors, provide localized support by promoting InnerSource principles and acting as a communication bridge between their teams and the ISPO.*
 * [Circle Communities](/patterns/1-initial/circle-communities.md) - *InnerSource adoption is slow in organizations due to limited understanding, engagement, and contextual relevance. Circle Communities address this by fostering synchronous conversations that build connections, close knowledge gaps, and cultivate collaboration and continuous learning.*
 * [Internal Developer Platform](/patterns/1-initial/internal-developer-platform.md) - *As InnerSource adoption increases throughout an organisation, it is not unusual that project teams start to face inefficiencies in scaling their efforts due to fragmented tooling, environments, and workflows. An Internal Developer Platform (IDP) provides a way to tackle this type of challenges through a centralized, self-service system that standardizes development environments and integrates tools to enhance consistency, collaboration, and developer productivity.*
+* [Document Architecture Decisions](/patterns/1-initial/document-architecture-decisions.md) - *InnerSource contributors often face challenges in grasping the system's design rationale, which can result in misalignment between maintainers, contributors, and stakeholders — potentially discouraging participation. To enhance decision-making and transparency, we recommend capturing architecture decisions and their consequences in a lightweight, accessible format to streamline onboarding, clarify decisions, and support long-term project sustainability.*
 
 <!--
 NOTE: The 'Initial' Patterns below don't have a Patlet yet, which is essential for readers to quickly browse our patterns.

meta/boardreports/2025-02.md

@@ -0,0 +1,70 @@
+# InnerSource Patterns WG - Report for Board Meeting 2025-02
+
+## Meta
+
+* Reporting Period: 2024-11..2025-01
+* [merged PRs](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls?q=is%3Apr+closed%3A2024-11..2025-01+is%3Amerged)
+* [opened issues](https://github.com/InnerSourceCommons/InnerSourcePatterns/issues?q=is%3Aissue+created%3A2024-11..2025-01+is%3Aopen)
+
+## Engagement
+
+The [patterns book][] is the way InnerSource practices are captured and shared. Recent web analytics:
+
+* total traffic on the patterns book (tracking_id: `G-QL1S8MW5D9`)
+  * 14,592 views total (prev 14,308)
+  * 1,784 users (prev 1,908)
+* Most popular patterns:
+  * InnerSource Portal
+  * 30 Day Warranty
+  * Maturity Model
+  * Standard Base Documentation
+  * Core Team
+* traffic for translations (btw the URLs here have changed at some point. used to be /v/ja etc):
+  * Japanese (/ja) - 2163 (prev 1300)
+  * Chinese (/zh) - 597 (prev 305)
+  * Brazilian Portuguese (/pt-br) - 418 (prev 332)
+  * Galician (/gl) - 101 (prev 46)
+  * English (/) - roughly 11,313
+* interpretations
+  * Of our translated content, the Japanese patterns are consumed the most. Great to see that the content provides value to users in that geo/language.
+  * Year over year the total views are down quite a bit. not sure why. (see reports from 2023)
+
+## Changes
+
+Changes are contributed via the [InnerSourcePatterns][] repository:
+
+* new patterns:
+  * [Internal Developer Platform](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/internal-developer-platform.md)
+  * [InnerSource Ambassadors](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/innersource-ambassador.md)
+  * [Governance Level Guided Project Setup](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/governance-based-project-setup.md)
+  * [Circle Communities](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/circle-communities.md)
+  * [Managing Capacity for Reviewing Contributions](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/capacity-for-contributions.md)
+* translations
+  * none
+* additions of Known Instances (applications of our patterns in the wild)
+  * SAP added to [Transparent Cross-Team Decision Making using RFCs](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/2-structured/transparent-cross-team-decision-making-using-rfcs.md)
+  * IKEA added to [InnerSource Hackathon](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/innersource-hackathon.md)
+  * BBC added to [Governance Level Guided Project Setup](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/governance-based-project-setup.md)
+  * WellSky added to [InnerSource Ambassadors](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/1-initial/innersource-ambassador.md)
+* other
+  * some UI improves (just using some of the newer features of our hosting provider gitbook)
+
+## Things to come
+
+* I (@spier) used a [Kanban style board](https://github.com/orgs/InnerSourceCommons/projects/32) more rigurously in the last few months. It did help me figure out where I should invest my time to move patterns/issues/prs through the process. It shows in the number of patterns that were added to the repo.
+* [Creating a plan](https://github.com/InnerSourceCommons/InnerSourcePatterns/issues/772) to get more patterns published in the book
+  * spoiler: we have 6 patterns that could do that in the medium term.
+  * Need more hands though to make this happen.
+  * Fun fact: this activity was triggered by the ISPO WG asking about patterns were not published in the book yet, but somehow they knew existed :)
+* Micaela Eller (from the ISPO WG) offered to help with leveling up further patterns. Will onboard her in the coming weeks.
+* [A proposal](https://github.com/InnerSourceCommons/InnerSourcePatterns/issues/777) was made to translate the patterns to Spanish. yay!
+
+## Trusted Committers (Community)
+
+* Last [Trusted Committer][] added was [@yuhattor](https://github.com/yuhattor) (added 2022-07-21)
+* Trusted Committer candidates in the pipeline: No
+* Finding new contributors and further trusted committers continues to be the main challenge of the InnerSource Patterns project
+
+[patterns book]: https://patterns.innersourcecommons.org/
+[InnerSourcePatterns]: https://github.com/InnerSourceCommons/InnerSourcePatterns/
+[Trusted Committer]: https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/TRUSTED-COMMITTERS.md

meta/scripts/find_upgradeable_patterns.rb

@@ -22,6 +22,7 @@
 def count_known_instances(file)
   section_nodes = collect_section_nodes(file, "Known Instances")
   list_nodes = []
+  
   # pick the first list in the "Known Instances" section, and return the number of elements in that list.
   # CAUTION: this assumes a certain structure across all patterns. Therefore fairly brittle.
   list_nodes = section_nodes.select {|n| n.type == :list}
@@ -32,15 +33,16 @@ def count_known_instances(file)
   return known_instances_count
 end
 
+# Extract all nodes below a given headline
 def collect_section_nodes(file, section_title)
   markdown = open(file).readlines().join
-  doc = CommonMarker.render_doc(markdown)
+  doc = Commonmarker.parse(markdown)
 
   title_found = false
   section_nodes = []
 
   doc.walk do |node|
-    if node.type == :header
+    if node.type == :heading
       if title_found == false
         node.each do |subnode|
           if subnode.type == :text and subnode.string_content == section_title
@@ -70,7 +72,10 @@ def collect_section_nodes(file, section_title)
 
 l1_patterns.each do |file|
   known_instances_count = count_known_instances(file)
-  puts "#{known_instances_count} | #{file}" if known_instances_count >= 1
+  file_display = file.gsub("../../patterns/1-initial/","")
+  file_link = file.gsub("../../","https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/")
+
+  puts "#{known_instances_count} | [#{file_display}](#{file_link})"
 end
 
 puts "\n"
@@ -80,5 +85,8 @@ def collect_section_nodes(file, section_title)
 
 l2_patterns.each do |file|
   known_instances_count = count_known_instances(file)
-  puts "#{known_instances_count} | #{file}" if known_instances_count >= 3
+  file_display = file.gsub("../../patterns/2-structured/","")
+  file_link = file.gsub("../../","https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/")
+
+  puts "#{known_instances_count} | [#{file_display}](#{file_link})" 
 end

patterns/1-initial/code-of-conduct.md

@@ -50,7 +50,7 @@ However, adopt the following life cycle can improve the implementation and adopt
 
 1. Collaboratively draft the Code of Conduct, involving input from community members representing diverse perspectives.
 2. Seek feedback and consensus from the community to ensure buy-in and ownership of the guidelines.
-3. Publish the finalized documents in a prominent location accessible to all community members, such as the [InnerSource portal](https://patterns.innersourcecommons.org/p/innersource-portal) or communication channels.
+3. Publish the finalized documents in a prominent location accessible to all community members, such as the [InnerSource portal](../2-structured/innersource-portal.md) or communication channels.
 4. Regularly review and update the Code of Conduct as needed to reflect evolving community norms and values.
 
 A good practice for the third point is to share the Code of Conduct in each InnerSource community repository as a file named `CODE_OF_CONDUCT.md`.
@@ -60,7 +60,7 @@ This file can be part of the [Standard Base Documentation](../2-structured/base-
 ![CODE_OF_CONDUCT.md](../../assets/img/code-of-conduct/CODE_OF_CONDUCT-for-the-community.png)
 
 It is important to understand that simply adopting a Code of Conduct will not prevent conflict or toxicity in the InnerSource project.
-The [Core Team](https://patterns.innersourcecommons.org/p/core-team) and [Dedicated Community Leader](https://patterns.innersourcecommons.org/p/dedicated-community-leader) are responsible for the safe, fair, and transparent enforcement of the community's code of conduct.
+The [Core Team](../2-structured/core-team.md) and [Dedicated Community Leader](../2-structured/dedicated-community-leader.md) are responsible for the safe, fair, and transparent enforcement of the community's code of conduct.
 That responsibility will imply provide a reporting process, a gathering information process and the consequences of any unacceptable behavior.
 These references must be part of the Code of Conduct to encourage the behavior expected in the InnerSource project.