way_of_working 1.0.0 → 2.0.0

data/lib/way_of_working/templates/.github/linters/rubocop_defaults.yml

@@ -1,55 +0,0 @@
----
-require:
-  - ndr_dev_support
-
-inherit_mode:
-  merge:
-    - Exclude
-
-AllCops:
-  TargetRubyVersion: 2.7
-
-# Ignore rules related to templated files
-Layout/EmptyLines:
-  Exclude:
-    - "config/**/*.rb"
-
-Layout/SpaceInsideArrayLiteralBrackets:
-  Exclude:
-    - "config/**/*.rb"
-
-Rails/Date:
-  Enabled: false
-
-Rails/TimeZone:
-  Enabled: false
-
-Style/Documentation:
-  Exclude:
-    - "app/helpers/application_helper.rb"
-    - "config/**/*.rb"
-
-Style/GlobalStdStream:
-  Exclude:
-    - "config/environments/production.rb"
-
-Style/OptionalBooleanParameter:
-  Enabled: false
-
-Style/RedundantConstantBase:
-  Exclude:
-    - "config/environments/production.rb"
-
-Style/RedundantFetchBlock:
-  Exclude:
-    - "config/puma.rb"
-
-Style/StringLiterals:
-  Exclude:
-    - "config.ru"
-    - "config/**/*.rb"
-    - "Rakefile"
-
-Style/SymbolArray:
-  Exclude:
-    - "config/initializers/filter_parameter_logging.rb"

data/lib/way_of_working/templates/.github/workflows/mega-linter.yml

@@ -1,82 +0,0 @@
----
-# MegaLinter GitHub Action configuration file
-# More info at https://megalinter.io
-name: MegaLinter
-
-on:
-  # Trigger mega-linter at every push. Action will also be visible from Pull Requests to master
-  push: # Comment this line to trigger action only on pull-requests (not recommended if you don't pay for GH Actions)
-  pull_request:
-    branches: [master, main]
-
-env: # Comment env block if you do not want to apply fixes
-  # Apply linter fixes configuration
-  APPLY_FIXES: none # When active, APPLY_FIXES must also be defined as environment variable (in github/workflows/mega-linter.yml or other CI tool)
-  APPLY_FIXES_EVENT: pull_request # Decide which event triggers application of fixes in a commit or a PR (pull_request, push, all)
-  APPLY_FIXES_MODE: commit # If APPLY_FIXES is used, defines if the fixes are directly committed (commit) or posted in a PR (pull_request)
-
-concurrency:
-  group: ${{ github.ref }}-${{ github.workflow }}
-  cancel-in-progress: true
-
-jobs:
-  build:
-    name: MegaLinter
-    runs-on: ubuntu-latest
-    steps:
-      # Git Checkout
-      - name: Checkout Code
-        uses: actions/checkout@v3
-        with:
-          token: ${{ secrets.PAT || secrets.GITHUB_TOKEN }}
-          fetch-depth: 0 # If you use VALIDATE_ALL_CODEBASE = true, you can remove this line to improve performances
-
-      # MegaLinter
-      - name: MegaLinter
-        id: ml
-        # You can override MegaLinter flavor used to have faster performances
-        # More info at https://megalinter.io/flavors/
-        uses: oxsecurity/megalinter@v6
-        env:
-          # All available variables are described in documentation
-          # https://megalinter.io/configuration/
-          VALIDATE_ALL_CODEBASE: true # Set ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }} to validate only diff with main branch
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          # ADD YOUR CUSTOM ENV VARIABLES HERE TO OVERRIDE VALUES OF .mega-linter.yml AT THE ROOT OF YOUR REPOSITORY
-
-      # # Upload MegaLinter artifacts
-      # - name: Archive production artifacts
-      #   if: ${{ success() }} || ${{ failure() }}
-      #   uses: actions/upload-artifact@v3
-      #   with:
-      #     name: MegaLinter reports
-      #     path: |
-      #       megalinter-reports
-      #       mega-linter.log
-
-      # # Create pull request if applicable (for now works only on PR from same repository, not from forks)
-      # - name: Create Pull Request with applied fixes
-      #   id: cpr
-      #   if: steps.ml.outputs.has_updated_sources == 1 && (env.APPLY_FIXES_EVENT == 'all' || env.APPLY_FIXES_EVENT == github.event_name) && env.APPLY_FIXES_MODE == 'pull_request' && (github.event_name == 'push' || github.event.pull_request.head.repo.full_name == github.repository) && !contains(github.event.head_commit.message, 'skip fix')
-      #   uses: peter-evans/create-pull-request@v4
-      #   with:
-      #     token: ${{ secrets.PAT || secrets.GITHUB_TOKEN }}
-      #     commit-message: "[MegaLinter] Apply linters automatic fixes"
-      #     title: "[MegaLinter] Apply linters automatic fixes"
-      #     labels: bot
-      # - name: Create PR output
-      #   if: steps.ml.outputs.has_updated_sources == 1 && (env.APPLY_FIXES_EVENT == 'all' || env.APPLY_FIXES_EVENT == github.event_name) && env.APPLY_FIXES_MODE == 'pull_request' && (github.event_name == 'push' || github.event.pull_request.head.repo.full_name == github.repository) && !contains(github.event.head_commit.message, 'skip fix')
-      #   run: |
-      #     echo "Pull Request Number - ${{ steps.cpr.outputs.pull-request-number }}"
-      #     echo "Pull Request URL - ${{ steps.cpr.outputs.pull-request-url }}"
-
-      # # Push new commit if applicable (for now works only on PR from same repository, not from forks)
-      # - name: Prepare commit
-      #   if: steps.ml.outputs.has_updated_sources == 1 && (env.APPLY_FIXES_EVENT == 'all' || env.APPLY_FIXES_EVENT == github.event_name) && env.APPLY_FIXES_MODE == 'commit' && github.ref != 'refs/heads/main' && (github.event_name == 'push' || github.event.pull_request.head.repo.full_name == github.repository) && !contains(github.event.head_commit.message, 'skip fix')
-      #   run: sudo chown -Rc $UID .git/
-      # - name: Commit and push applied linter fixes
-      #   if: steps.ml.outputs.has_updated_sources == 1 && (env.APPLY_FIXES_EVENT == 'all' || env.APPLY_FIXES_EVENT == github.event_name) && env.APPLY_FIXES_MODE == 'commit' && github.ref != 'refs/heads/main' && (github.event_name == 'push' || github.event.pull_request.head.repo.full_name == github.repository) && !contains(github.event.head_commit.message, 'skip fix')
-      #   uses: stefanzweifel/git-auto-commit-action@v4
-      #   with:
-      #     branch: ${{ github.event.pull_request.head.ref || github.head_ref || github.ref }}
-      #     commit_message: "[MegaLinter] Apply linters fixes"

data/lib/way_of_working/templates/.mega-linter.yml

@@ -1,129 +0,0 @@
----
-# Configuration file for MegaLinter
-# See all available variables at https://megalinter.io/configuration/ and in linters documentation
-
-APPLY_FIXES: none # all, none, or list of linter keys
-ENABLE_LINTERS: # If you use ENABLE_LINTERS variable, all other linters will be disabled by default
-# Languages
-  - BASH_EXEC # in Super-Linter
-  - BASH_SHELLCHECK # in Super-Linter
-  - BASH_SHFMT # in Super-Linter
-  - C_CPPLINT
-  # - CLOJURE_CLJ_KONDO # in Super-Linter
-  - COFFEE_COFFEELINT # in Super-Linter
-  - CPP_CPPLINT # in Super-Linter
-  - CSHARP_DOTNET_FORMAT # in Super-Linter
-  - DART_DARTANALYZER # in Super-Linter
-  - GO_GOLANGCI_LINT # in Super-Linter
-  - GO_REVIVE
-  # - GROOVY_NPM_GROOVY_LINT # in Super-Linter
-  - JAVA_CHECKSTYLE # in Super-Linter
-  - JAVA_PMD
-  - JAVASCRIPT_ES # in Super-Linter
-  # - JAVASCRIPT_PRETTIER
-  - JAVASCRIPT_STANDARD # in Super-Linter
-  - JSX_ESLINT
-  - KOTLIN_KTLINT # in Super-Linter
-  # - LUA_LUACHECK # in Super-Linter
-  - MAKEFILE_CHECKMAKE
-  # - PERL_PERLCRITIC # in Super-Linter
-  # - PHP_PHPCS # in Super-Linter
-  # - PHP_PHPLINT # in Super-Linter
-  # - PHP_PHPSTAN # in Super-Linter
-  # - PHP_PSALM # in Super-Linter
-  # - POWERSHELL_POWERSHELL
-  # - POWERSHELL_POWERSHELL_FORMATTER
-  - PYTHON_BANDIT
-  - PYTHON_BLACK # in Super-Linter
-  - PYTHON_FLAKE8 # in Super-Linter
-  - PYTHON_ISORT # in Super-Linter
-  - PYTHON_MYPY
-  - PYTHON_PYLINT # in Super-Linter
-  - PYTHON_PYRIGHT
-  - R_LINTR # in Super-Linter
-  # - RAKU_RAKU # in Super-Linter
-  # - RUBY_RUBOCOP # in Super-Linter
-  - RUST_CLIPPY # in Super-Linter
-  # - SALESFORCE_SFDX_SCANNER_APEX
-  # - SALESFORCE_SFDX_SCANNER_AURA
-  # - SALESFORCE_SFDX_SCANNER_LWC
-  - SCALA_SCALAFIX
-  - SQL_SQL_LINT # in Super-Linter
-  - SQL_SQLFLUFF # in Super-Linter
-  - SQL_TSQLLINT
-  - SWIFT_SWIFTLINT
-  - TSX_ESLINT
-  - TYPESCRIPT_ES # in Super-Linter
-  # - TYPESCRIPT_PRETTIER
-  - TYPESCRIPT_STANDARD # in Super-Linter
-  # - VBDOTNET_DOTNET_FORMAT
-
-# Formats
-  - CSS_SCSS_LINT
-  - CSS_STYLELINT # in Super-Linter
-  - ENV_DOTENV_LINTER # in Super-Linter
-  # - GRAPHQL_GRAPHQL_SCHEMA_LINTER
-  # - HTML_DJLINT # Refuses to see config file
-  - HTML_HTMLHINT # in Super-Linter
-  - JSON_ESLINT_PLUGIN_JSONC # in Super-Linter
-  - JSON_JSONLINT
-  - JSON_NPM_PACKAGE_JSON_LINT
-  # - JSON_PRETTIER
-  - JSON_V8R
-  # - LATEX_CHKTEX # in Super-Linter
-  - MARKDOWN_MARKDOWNLINT # in Super-Linter
-  - MARKDOWN_MARKDOWN_LINK_CHECK
-  - MARKDOWN_MARKDOWN_TABLE_FORMATTER
-  - MARKDOWN_REMARK_LINT
-  # - PROTOBUF_PROTOLINT # in Super-Linter
-  # - RST_RSTCHECK
-  # - RST_RSTFMT
-  # - RST_RST_LINT
-  - XML_XMLLINT # in Super-Linter
-  # - YAML_PRETTIER
-  - YAML_V8R
-  - YAML_YAMLLINT # in Super-Linter
-
-# Tooling
-  - ACTION_ACTIONLINT # in Super-Linter
-  - ANSIBLE_ANSIBLE_LINT # in Super-Linter
-  - ARM_ARM_TTK # in Super-Linter
-  # - BICEP_BICEP_LINTER
-  - CLOUDFORMATION_CFN_LINT # in Super-Linter
-  - DOCKERFILE_HADOLINT # in Super-Linter
-  - EDITORCONFIG_EDITORCONFIG_CHECKER # in Super-Linter
-  # - GHERKIN_GHERKIN_LINT # in Super-Linter
-  - KUBERNETES_KUBECONFORM
-  - KUBERNETES_KUBEVAL # in Super-Linter
-  - OPENAPI_SPECTRAL # in Super-Linter
-  - PUPPET_PUPPET_LINT
-  # - SNAKEMAKE_LINT # in Super-Linter
-  # - SNAKEMAKE_SNAKEFMT # in Super-Linter
-  # - TEKTON_TEKTON_LINT # in Super-Linter
-  - TERRAFORM_CHECKOV
-  - TERRAFORM_KICS
-  - TERRAFORM_TERRAFORM_FMT # in Super-Linter
-  - TERRAFORM_TERRAGRUNT # in Super-Linter
-  - TERRAFORM_TERRASCAN # in Super-Linter
-  - TERRAFORM_TFLINT # in Super-Linter
-
-# Code quality checkers
-  - COPYPASTE_JSCPD # in Super-Linter
-  - REPOSITORY_CHECKOV
-  - REPOSITORY_DEVSKIM
-  - REPOSITORY_DUSTILOCK
-  - REPOSITORY_GITLEAKS # in Super-Linter
-  - REPOSITORY_GIT_DIFF
-  - REPOSITORY_GOODCHECK
-  - REPOSITORY_SECRETLINT
-  - REPOSITORY_SEMGREP
-  - REPOSITORY_SYFT
-  - REPOSITORY_TRIVY
-  # - SPELL_CSPELL
-  - SPELL_MISSPELL
-  - SPELL_PROSELINT
-
-SHOW_ELAPSED_TIME: false
-FILEIO_REPORTER: false
-FAIL_IF_MISSING_LINTER_IN_FLAVOR: true
-# DISABLE_ERRORS: true # Uncomment if you want MegaLinter to detect errors but not block CI to pass

data/lib/way_of_working/templates/.rubocop

@@ -1 +0,0 @@
---config .github/linters/rubocop_defaults.yml

data/lib/way_of_working/templates/CODE_OF_CONDUCT.md.tt

@@ -1,134 +0,0 @@
-
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall
-  community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances of
-  any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-<%= options['contact_method'] %>.
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of
-actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
-ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the
-community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
-[https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations
-

data/lib/way_of_working/templates/docs/decisions/README.md

@@ -1,7 +0,0 @@
-# Decisions
-
-This directory contains decision records for the project.
-
-For new ADRs, please use [adr-template.md](adr-template.md) as basis.
-More information on MADR is available at <https://adr.github.io/madr/>.
-General information about architectural decision records is available at <https://adr.github.io/>.

data/lib/way_of_working/templates/docs/decisions/adr-template.md.tt

@@ -1,79 +0,0 @@
----
-# These are optional elements. Feel free to remove any of them.
-status: {proposed | rejected | accepted | deprecated | … | superseded by ADR-0005 <0005-example.md>}
-date: <%= @decision_date %>
-deciders: {list everyone involved in the decision}
-consulted: {list everyone whose opinions are sought (typically subject-matter experts); and with whom there is a two-way communication}
-informed: {list everyone who is kept up-to-date on progress; and with whom there is a one-way communication}
----
-# <%= @title %>
-
-## Context and Problem Statement
-
-{Describe the context and problem statement, e.g., in free form using two to three sentences or in the form of an illustrative story.
- You may want to articulate the problem in form of a question and add links to collaboration boards or issue management systems.}
-
-<!-- This is an optional element. Feel free to remove. -->
-## Decision Drivers
-
-* {decision driver 1, e.g., a force, facing concern, …}
-* {decision driver 2, e.g., a force, facing concern, …}
-* … <!-- numbers of drivers can vary -->
-
-## Considered Options
-
-* {title of option 1}
-* {title of option 2}
-* {title of option 3}
-* … <!-- numbers of options can vary -->
-
-## Decision Outcome
-
-Chosen option: "{title of option 1}", because
-{justification. e.g., only option, which meets k.o. criterion decision driver | which resolves force {force} | … | comes out best (see below)}.
-
-<!-- This is an optional element. Feel free to remove. -->
-### Consequences
-
-* Good, because {positive consequence, e.g., improvement of one or more desired qualities, …}
-* Bad, because {negative consequence, e.g., compromising one or more desired qualities, …}
-* … <!-- numbers of consequences can vary -->
-
-<!-- This is an optional element. Feel free to remove. -->
-## Validation
-
-{describe how the implementation of/compliance with the ADR is validated. E.g., by a review or an ArchUnit test}
-
-<!-- This is an optional element. Feel free to remove. -->
-## Pros and Cons of the Options
-
-### {title of option 1}
-
-<!-- This is an optional element. Feel free to remove. -->
-{example | description | pointer to more information | …}
-
-* Good, because {argument a}
-* Good, because {argument b}
-<!-- use "neutral" if the given argument weights neither for good nor bad -->
-* Neutral, because {argument c}
-* Bad, because {argument d}
-* … <!-- numbers of pros and cons can vary -->
-
-### {title of other option}
-
-{example | description | pointer to more information | …}
-
-* Good, because {argument a}
-* Good, because {argument b}
-* Neutral, because {argument c}
-* Bad, because {argument d}
-* …
-
-<!-- This is an optional element. Feel free to remove. -->
-## More Information
-
-{You might want to provide additional evidence/confidence for the decision outcome here and/or
- document the team agreement on the decision and/or
- define when and how this decision should be realized and if/when it should be re-visited and/or
- how the decision is validated.
- Links to other decisions and resources might appear here as well.}