Merge branch 'main' into innersource-ambassadors

Author: spier

.github/dependabot.yml

@@ -0,0 +1,6 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/contributor-report.yaml

@@ -37,7 +37,7 @@ jobs:
         SPONSOR_INFO: "true"
 
     - name: Create issue
-      uses: peter-evans/create-issue-from-file@v4
+      uses: peter-evans/create-issue-from-file@v5
       with:
         title: "Monthly Metrics: Contributors ${{ env.START_DATE }}..${{ env.END_DATE }}"
         token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/generate-mindmap.yml

@@ -21,6 +21,10 @@ jobs:
   generate-mindmap:
     runs-on: ubuntu-latest
 
+    permissions:
+      # Give the default GITHUB_TOKEN write permission to commit and push the changed files back to the repository.
+      contents: write
+
     strategy:
       matrix:
         folder: [".", "./gl", "./pt-br"]

.github/workflows/link-checker-prs.yml

@@ -21,7 +21,7 @@ jobs:
 
       - name: Get changed files
         id: changed-files
-        uses: tj-actions/changed-files@v44
+        uses: tj-actions/changed-files@v45
 
       - name: Filter markdown files only
         run: |
@@ -37,7 +37,7 @@ jobs:
 
       - if: ${{ env.MARKDOWN_FILES != '' }}
         name: Link Checker
-        uses: lycheeverse/lychee-action@v1.5.2
+        uses: lycheeverse/lychee-action@v2
         with:
           args: --verbose --no-progress --exclude-mail --cache --max-cache-age 1d $MARKDOWN_FILES
           fail: true

.github/workflows/link-checker.yml

@@ -9,6 +9,7 @@ on:
   schedule:
     # * is a special character in YAML so you have to quote this string
     - cron:  '30 8 * * 5'
+  workflow_dispatch:
 
 jobs:
   linkChecker:
@@ -24,7 +25,7 @@ jobs:
           restore-keys: cache-lychee-
 
       - name: Link Checker
-        uses: lycheeverse/lychee-action@v1.5.2
+        uses: lycheeverse/lychee-action@v2
         with:
           args: --verbose --no-progress --exclude-mail --cache --max-cache-age 1d README.md patterns/ book/ translation/
           fail: true

.github/workflows/pattern-metrics.yaml

@@ -80,7 +80,7 @@ jobs:
         cat ready_to_merge_issues_report.md hr.md issue_metrics.md > all.md
 
     - name: Create issue
-      uses: peter-evans/create-issue-from-file@v4
+      uses: peter-evans/create-issue-from-file@v5
       with:
         title: "Monthly Metrics: New Issues + New Pull Requests ${{ env.last_month }}"
         token: ${{ secrets.GITHUB_TOKEN }}

.lycheeignore

@@ -9,4 +9,7 @@ fearlesschangepatterns.com
 https://ulir.ul.ie/bitstream/handle/10344/4443/Stol_2014_inner.pdf
 .*@andrew.clegg.*
 https://m.dotdev.co/how-to-write-a-readme-that-rocks-bc29f279611a
-https://www.chathamhouse.org/about-us/chatham-house-rule
+https://www.chathamhouse.org/about-us/chatham-house-rule
+
+# from source-code-inventory.md / no longer reachable but we want to keep the link in the pattern in case we find it again.
+https://github.com/trieshard/source-strategy-assessment/blob/master/framework.md

README.md

@@ -87,6 +87,7 @@ Our mission
 * [Code of Conduct](/patterns/1-initial/code-of-conduct.md) - *Communications and interactions between collaborators are rude, not inclusive or offensive, harming and increasing the discussions without any value added. A Code of Conduct provides guidelines for establishing rules and expectations regarding behavior and interactions within the community to build stronger levels of collaboration.*
 * [Trusted Committer and Contributor Retrospectives](/patterns/1-initial/cross-team-retrospectives.md) - *A host team working with contributors outside of their own line of management constantly runs into misunderstandings. As a result collaboration becomes brittle and frustrating. Setting aside time for regular retrospectives for the InnerSource team consisting of trusted committers and contributors can help make communication smooth.*
 * [InnerSource Hackathon](/patterns/1-initial/innersource-hackathon.md) - *In a company, initially only InnerSource enthusiasts are interested and practicing InnerSource during the early stages of InnerSource adoption; not all engineering teams are willing or have enough time and resources to adopt InnerSource. In this scenario, it is good to provide a safe space to try and adopt InnerSource through an InnerSource Hackathon event within the company.*
+* [Managing Capacity for Reviewing Contributions](/patterns/1-initial/capacity-for-contributions.md) - *Reviewing InnerSource contributions takes time and effort. This should be reflected in capacity planning, especially for larger contributions. Expectations and available capacity should be transparent so that contributors understand when their contributions will be reviewed and, if accepted, released.*
 * [InnerSource Ambassadors](/patterns/1-initial/innersource-hackathon.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.*
 
 <!--

meta/boardreports/2024-11.md

@@ -0,0 +1,64 @@
+# InnerSource Patterns WG - Report for Board Meeting 2024-11
+
+## Meta
+
+* Reporting Period: 2024-08..2024-10
+* [merged PRs](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls?q=is%3Apr+closed%3A2024-08..2024-10+is%3Amerged)
+* [opened issues](https://github.com/InnerSourceCommons/InnerSourcePatterns/issues?q=is%3Aissue+created%3A2024-08..2024-10+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,308 views total (prev 15,021)
+  * 1,908 users (prev 1,897)
+* Most popular patterns:
+  * 30 Day Warranty
+  * Core Team
+  * Maturity Model
+  * Standard Base Documentation
+  * InnerSource Portal
+* traffic for translations:
+  * Japanese (/v/ja) - 1300 (prev no data in Google Analytics)
+  * Chinese (/v/zh) - 305 (prev 545)
+  * Brazilian Portuguese (/v/pt-br) - 332 (prev 358)
+  * Galician (/v/gl) - 46 (prev 68)
+  * English (/) - roughly 12,300 (14,308 - sum of translation views above)
+* interpretations
+  * Of our translated content, the Japanese patterns are consumed the most (almost 10% of our total views). 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:
+  * none
+* translations
+  * [fixes](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/722) to the Chinese translations / thanks @node
+* additions of Known Instances (applications of our patterns in the wild)
+  * none
+* other
+  * [great review](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/710) / thanks @semioticrobotic
+  * [fixed link to bazaar plugin](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/711) / thanks @khola
+
+## Things to come
+
+* We would like to do one round of cleanup of old PRs/issues that are unlikely to still be implemented as they are stale for too long.
+* (still) Toying with the idea to add [Adopters pages](https://innersourcecommons.gitbook.io/innersource-patterns-staging/v/adopters-test/adopters/adopters) to our book. Goal: showcase the organizations and the patterns they use more prominently in our book. Looking for feedback! More [details here](https://github.com/InnerSourceCommons/InnerSourcePatterns/issues/623).
+* Some PRs are stuck. Reason is mostly that I (@spier) have less time to review things or communication with the contributor stopped somewhere.
+
+## 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
+
+## Next Goals
+
+Same as previous Board report.
+
+[patterns book]: https://patterns.innersourcecommons.org/
+[InnerSourcePatterns]: https://github.com/InnerSourceCommons/InnerSourcePatterns/
+[Trusted Committer]: https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/TRUSTED-COMMITTERS.md