[TEST] Update JA gitbook with latest from main

.gitbook.yaml

@@ -1,6 +1,5 @@
 root : ./
 
 structure:
-  readme: book/jp/introduction.md
-  summary: book/jp/toc.md
-
+  readme: book/en/introduction.md
+  summary: book/en/toc.md

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Slack
+    url: https://innersourcecommons.org/slack
+    about: Join our Community on Slack for help and a casual chat.
+  - name: Patterns Book
+    url: https://patterns.innersourcecommons.org
+    about: Read our most mature patterns here.

.github/ISSUE_TEMPLATE/pattern-draft.md

@@ -0,0 +1,70 @@
+---
+name: Pattern Draft
+about: Suggest a new Pattern
+title: "[Pattern Draft]"
+labels: 1-initial, Type - Content Work
+assignees: ''
+
+---
+
+This is the most basic template for a new pattern.
+See our full pattern syntax [here](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/meta/pattern-template.md).
+
+## Title
+
+Short Title Here
+
+## Patlet / Summary
+
+Concise 1-2 sentence description of the problem and solution.
+
+## Problem
+
+What is the problem - crisp definition of the problem.
+Short description, usually not more than a couple sentences, that describes what the issues and challenges are.
+Be careful not to morph into information found in other sections below.
+
+## Context
+
+Where does the problem exist?
+What are the pre-conditions?
+**Unchangeable** before the solution goes into place.
+The content here is often tied to the applicability of the pattern for other readers: "Do I have this same particular situation?"
+
+## Forces
+
+What makes the problem difficult?
+What are the trade-offs?
+These are constraints that **can be changed** at a cost.
+The solution might change one or more of these forces in order to solve the problem, while also in-turn changing the context.
+
+## Solutions
+
+Verified resolutions and possible resolutions to the problem.
+
+## Resulting Context
+
+What is the situation after the problem has been solved?
+The original context is changed indirectly by way of the solution.
+Often this section can include discussion of the next possible Patterns/problems introduced.
+This section can be short in content - the solution may not introduce new problems or change much context.
+
+## Known Instances (optional)
+
+Where has this been seen before?
+Helps to reinforce that this is a REAL pattern and that you match the context.
+
+May mention:
+
+* A particular business
+* Anonymized instances ex: "3 companies have proven that this is a good solution" or "A large financial services org...".
+
+## Status 
+
+Initial
+
+## Author(s) (optional)
+
+Often, this is yourself.
+If you need to, find someone in the InnerSource Commons to be the nominal author (As Told To).
+Could also be no-one if you do not want to take on authorship (common with a donut looking for a solution).

.github/config.yml

@@ -0,0 +1,44 @@
+# Configuration for welcome - https://github.com/behaviorbot/welcome
+
+# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
+
+# Comment to be posted to on first time issues
+newIssueWelcomeComment: >
+  [![Welcome Banner](https://zenodo.org/api/iiif/v2/0c0188d3-d03c-4830-a6e3-00405f5c22fa:8ff47a85-7250-4d86-8e48-2f346b48b2c1:BannerWelcome.jpg/full/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:
+
+  <br>If you haven't done so already, please check out our [Contributing Guidelines](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/CONTRIBUTING.md).
+  If you need to connect more synchronously with members of _The InnerSource Commons_ community, come chat with us in our [Slack workspace](https://innersourcecommons.org/slack).
+
+# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
+
+# Comment to be posted to on PRs from first time contributors in your repository
+newPRWelcomeComment: >
+  [![Thank You Banner](https://zenodo.org/api/iiif/v2/0c0188d3-d03c-4830-a6e3-00405f5c22fa:7fbd97cf-283b-480c-b8e1-11866e26245c:BannerThanks.jpg/full/750,/0/default.jpg)](https://zenodo.org/record/3695300)
+
+  :sparkling_heart: Thanks for opening this pull request! :sparkling_heart:
+  _The InnerSource Commons_ community really appreciates your time and effort to contribute to the project.
+  Please make sure you have read our [Contributing Guidelines](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/CONTRIBUTING.md).
+
+  If you are submitting a new pattern, the following things will help get your pull request across the finish line! :checkered_flag:
+
+  - Check you have used our [pattern template](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/meta/pattern-template.md) and removed any placeholder text and sections that your pattern did not need.
+
+  - We will run a number of automated checks on your PR. Please review the output of those checks on the PR itself, and see if any issues got flagged that you can fix yourself.
+
+  - Make sure you have added your new pattern to the list of patterns in the main [README.md](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/README.md). If you are unsure where to add your pattern, no worries. Just let us know on the PR and we will help you.
+
+  <br>This project has a small number of maintainers, volunteering their time to this project. So please be patient and we will get back to you as soon as we can.
+  If we don't acknowledge this pull request after 7 days, feel free to chat to us about it in our [Slack workspace](https://innersourcecommons.org/slack).
+
+# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
+
+# Comment to be posted to on pull requests merged by a first time user
+firstPRMergeComment: >
+  [![Congratulations Banner](https://zenodo.org/api/iiif/v2/0c0188d3-d03c-4830-a6e3-00405f5c22fa:32fbdb89-ae1b-434e-830c-88ade86724cc:BannerCongratulations.jpg/full/750,/0/default.jpg)](https://zenodo.org/record/3695300)
+
+  Congrats on merging your first pull request! :tada:
+  We here at _The InnerSource Commons_ are proud of you! :sparkling_heart:
+  Thank you so much for your contribution :gift:

.github/workflows/book.yml

@@ -23,7 +23,7 @@ jobs:
 
     - name: Determine book language
       run: |
-        [[ "$GITHUB_REF_NAME" == "book-jp" ]] && book_language="jp" || book_language="en"
+        [[ "$GITHUB_REF_NAME" =~ ^book-.*$ ]] && book_language=${GITHUB_REF_NAME:5:2} || book_language="en"
         echo "BOOK_LANGUAGE=$book_language" >> $GITHUB_ENV
 
     - name: Generate ToC

.github/workflows/generate-mindmap.yml

@@ -18,11 +18,11 @@ jobs:
   generate-mindmap:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
     - name: Use Node.js
-      uses: actions/setup-node@v2
+      uses: actions/setup-node@v3
       with:
-        node-version: 12.x
+        node-version: 16
         cache: 'npm'
         cache-dependency-path: pattern-categorization/package-lock.json
     - name: Install Node.js dependencies

.github/workflows/i18n-consistency-checker.yaml

@@ -0,0 +1,104 @@
+name: i18n check consistency and notify on GitHub Issues
+
+on:
+  pull_request:
+    branches:
+      - master
+    paths:
+      - .github/workflows/i18n-consistency-check.yml
+  schedule:
+    - cron: '0 0 1 * *'
+  workflow_dispatch:
+
+jobs:
+  consistency-check:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        language: [ja, zh]
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          fetch-depth: '0'
+      - name: Check consistency
+        id: check-consistency
+        run: |
+          # Set the issue header
+          issue="\
+          # i18n Contents Consistency Issue\\n\
+          \\n\
+          The following files may have consistency issues with the English version. Please check and update the files.\\n\
+          \\n\
+          This issue is created when there is an update to content/en. It compares the git update history to let you know what updates are overdue. The issue should be closed when the update is complete.\\n"
+
+          for file in $(find patterns/2-structured -name '*.md'); do
+
+            # Get the translated file name and check if it exists
+            i18n_filename=$(echo "$file" | sed 's/patterns\/2-structured/translation\/${{matrix.language}}\/patterns/g')
+            if [[ ! -e "$i18n_filename" ]]; then
+            	continue
+            fi
+            echo $file
+            echo $i18n_filename
+            # Loop through all the files in the English directory
+            # Get the last updated date of the original file and the translated file
+            original_updated_at=$(date -d "$(git log -1 --format=%cd --date=iso $file)" +%s) 
+            i18n_content_updated_at=$(date -d "$(git log -1 --format=%cd --date=iso $i18n_filename)" +%s)
+
+            # print the last updated date of the original file and the translated file
+
+            # Check if the translated file is updated after the original file
+            if [[ $(($original_updated_at - $i18n_content_updated_at)) -ge 1 ]]; then
+              # Get the title of the content
+              content_header=$(echo "$(cat "$file")" | grep -E '^title+' | sort -r | head -n1)
+              content_title=$(echo "$content_header" | sed 's/title: //g')
+
+              # Get the days since the translated file is overdue
+              days_since_overdue_updates=$(($(( $(date +%s) - $original_updated_at))/ 60 / 60 / 24))
+              # Get the diff between the original file and the translated file
+              original_last_update_hash=$(git log -1 --format=%H $file)
+              # Get the parent hash of the original last update hash
+              parent_hash=$(git log -1 --format=%P $original_last_update_hash)
+                # Get the diff between the original file and the translated file
+
+              result=$(echo "$(git diff ${parent_hash} HEAD $file)" | sed '1,4 s/^/# /')
+              echo -e "$result"
+
+              # Add the contents to the issue.md file
+              issue+="<details><summary><b>$content_title</b> ($file)</summary>\\n\\n"
+              issue+="- Original File(en): [$file](https://github.com/$GITHUB_REPOSITORY/blob/master/$file)\\n"
+              issue+="- Translated File(${{matrix.language}}): [$i18n_filename](https://github.com/$GITHUB_REPOSITORY/blob/master/$i18n_filename)\\n"
+              issue+="- [Diff on GitHub](https://github.com/yuhattor/innersourcecommons.org/compare/$i18n_last_update_hash...$original_last_update_hash)\\n"
+              issue+="- Days since overdue updates: $days_since_overdue_updates days\\n"
+              issue+="\`\`\`diff\\n"
+              issue+="$result"
+              issue+="\\n\`\`\`\\n"
+              issue+="</details>\\n"
+              echo -e "$issue" >> issue.md
+              issue=""
+            fi
+          done
+      - name: Create Issue
+        run: | 
+          # Declare the flags
+          declare -A flags=(
+            ["ja"]="🇯🇵 Japanese"
+            ["zh"]="🇨🇳 Chinese"
+          )
+
+          # Set the issue title
+          issue_title="${flags[${{matrix.language}}]}: Content Consistency Issue"
+
+          # Get the existing issue ID
+          existing_issue_id=$(gh issue list -S "state:open type:issue title:$issue_title" | cut -f1)
+
+          # If the issue.md file exists, create a new issue or comment on the existing issue
+          if [ -f issue.md ]; then
+            if expr "$existing_issue_id" : '^[0-9]*$' >/dev/null; then
+              gh issue comment "$existing_issue_id" -F issue.md -R $GITHUB_REPOSITORY
+            else
+              gh issue create -t "$issue_title" -F issue.md -R $GITHUB_REPOSITORY -l "Type - Translation"
+            fi
+          fi
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

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

@@ -0,0 +1,46 @@
+# This link check is run on all PRs but just for the files that were changed/added in the PR itself.
+# Otherwise we had it too often that PR authors would see a failing link check that had nothing to do with their PR.
+
+name: Link Check PR
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  linkChecker:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+
+      - name: Get changed files
+        id: changed-files
+        uses: tj-actions/changed-files@v32
+
+      - name: Filter markdown files only
+        run: |
+          md_files=`find ${{ steps.changed-files.outputs.all_changed_files }} -maxdepth 0 -name "*.md" | tr '\n' ' '`
+          echo "MARKDOWN_FILES=$md_files" >> $GITHUB_ENV
+
+      - name: Restore lychee cache
+        uses: actions/cache@v3
+        with:
+          path: .lycheecache
+          key: cache-lychee-${{ github.sha }}
+          restore-keys: cache-lychee-
+
+      - if: ${{ env.MARKDOWN_FILES != '' }}
+        name: Link Checker
+        uses: lycheeverse/lychee-action@v1.5.2
+        with:
+          args: --verbose --no-progress --exclude-mail --cache --max-cache-age 1d $MARKDOWN_FILES
+          fail: true
+          jobSummary: true
+        env:
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

.github/workflows/link-checker.yml

@@ -1,26 +1,33 @@
-# from: https://github.com/marketplace/actions/link-checker
-# link checker used is 'liche': https://github.com/raviqqe/liche
+# This link check is run on all content files once per day.
 
-name: Link Check on Patterns and README
+# from: https://github.com/lycheeverse/lychee-action
+# link checker used is 'lychee': https://github.com/lycheeverse/lychee
+
+name: Link Check
 
 on:
-  push:
-    branches:
-      - "main"
-  pull_request:
   schedule:
     # * is a special character in YAML so you have to quote this string
-    - cron:  '30 8 * * *'
+    - cron:  '30 8 * * 5'
 
 jobs:
   linkChecker:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - name: Link Checker
-      id: lc
-      uses: peter-evans/link-checker@v1
-      with:
-        args: -v -d . -x "http://creativecommons.org/licenses|https://isc-inviter.herokuapp.com|https://github.com/rcs/rcs-viewer/pull/81|fearlesschangepatterns.com|https://ulir.ul.ie/bitstream/handle/10344/4443/Stol_2014_inner.pdf|https://docs.github.com/en/rest/metrics/statistics|https://docs.github.com/en/rest/search#search-repositories" README.md patterns/ book/ translation/ -r
-    - name: Fail if there were link errors
-      run: exit ${{ steps.lc.outputs.exit_code }}
+      - uses: actions/checkout@v3
+
+      - name: Restore lychee cache
+        uses: actions/cache@v3
+        with:
+          path: .lycheecache
+          key: cache-lychee-${{ github.sha }}
+          restore-keys: cache-lychee-
+
+      - name: Link Checker
+        uses: lycheeverse/lychee-action@v1.5.2
+        with:
+          args: --verbose --no-progress --exclude-mail --cache --max-cache-age 1d README.md patterns/ book/ translation/
+          fail: true
+          jobSummary: true
+        env:
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

.github/workflows/lint-patterns.yml

@@ -1,4 +1,6 @@
 # from: https://github.com/marketplace/actions/markdown-linting-action
+# To test this locally, switch to the root of the repo and run:
+# markdownlint -r config/lint/pattern-template.js -c config/lint/pattern-template.yml patterns/2-structured/*.md patterns/2-structured/project-setup/*.md patterns/3-validated/*.md
 name: Pattern Syntax Validation
 
 on:
@@ -8,7 +10,7 @@ on:
   pull_request:
     paths:
       - ".github/workflows/lint-patterns.yml"
-      - "lint/*"
+      - ".github/lint-pattern-syntax/*"
       - "patterns/2-structured/*.md"
       - "patterns/2-structured/project-setup/*.md"
       - "patterns/3-validated/*.md"
@@ -17,12 +19,12 @@ jobs:
   validate:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v3
     - name: Problem Matcher for markdownlint-cli
-      uses: xt0rted/markdownlint-problem-matcher@v1
+      uses: xt0rted/markdownlint-problem-matcher@v2
     - name: Lint pattern files (markdown)
       uses: avto-dev/markdown-lint@v1
       with:
-        rules: './lint/pattern-template.js'
-        config: './lint/pattern-template.yml'
+        rules: './.github/lint-pattern-syntax/pattern-template.js'
+        config: './.github/lint-pattern-syntax/pattern-template.yml'
         args: 'patterns/2-structured/*.md patterns/2-structured/project-setup/*.md patterns/3-validated/*.md'