Merge branch 'main' into governance-based-project-setup

Author: spier

.github/config.yml

@@ -4,7 +4,7 @@
 
 # Comment to be posted to on first time issues
 newIssueWelcomeComment: >
-  [![Welcome Banner](https://zenodo.org/api/iiif/record:3695300:BannerWelcome.jpg/full/!750,750/0/default.jpg)](https://zenodo.org/record/3695300)](https://zenodo.org/record/3695300)
+  [![Welcome Banner](https://zenodo.org/api/iiif/record:3695300:BannerWelcome.jpg/full/!750,750/0/default.jpg)](https://zenodo.org/record/3695300)
 
   :tada: Welcome to _The InnerSource Commons_ community, and in particular to our patterns! :tada:
   We're really excited to have your input into the project! :sparkling_heart:

.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 }}

.github/workflows/vale.yml

@@ -21,7 +21,7 @@ jobs:
     - uses: actions/checkout@v4
 
     - name: Vale Linting
-      uses: errata-ai/vale-action@reviewdog
+      uses: errata-ai/vale-action@v2
       with:
         files: '["patterns/2-structured/", "patterns/3-validated/"]'
         vale_flags: "--glob=*.md"

.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

@@ -86,6 +86,7 @@ Our mission
 * [Creating an InnerSource Strategy](/patterns/1-initial/creating_an_innersource_strategy.md) - *Sometimes, it is difficult to convince people of the relevance of InnerSource for your organization and/or to get support from management. Creating an InnerSource strategy, that connects your InnerSource approach and activities to the goals and the overall strategy of your organization, can help in this regard.*
 * [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.*
 * [Governance Level Guided Project Setup](/patterns/1-initial/governance-based-project-setup.md) - *Before publishing their first InnerSource project, a team wants to choose an appropriate Governance Level but is unsure about the impact of the different levels on their daily doing. A dedicated list of resources (best practices, recommended patterns, target maturity levels) provides specific guidance to the team and helps them to make an educated decision.*
 
 <!--