kettle-jem 7.0.0 → 7.1.3

data/lib/kettle/jem/templates/Appraisals.example

@@ -0,0 +1,150 @@
+# frozen_string_literal: true
+
+# {KJ|FREEZE_TOKEN}:freeze
+# To retain chunks of comments & code during kettle-jem templating:
+# Wrap custom sections with freeze markers (e.g., as above and below this comment chunk).
+# kettle-jem will then preserve content between those markers across template runs.
+# {KJ|FREEZE_TOKEN}:unfreeze
+
+# HOW TO GENERATE APPRAISALS (Appraisal2 RuboCop plugin normalizes generated gemfiles on modern Ruby):
+#   bin/rake appraisal:generate
+# Use bin/rake appraisal:update only when refreshing appraisal locks is intentional.
+
+plugin "appraisal2-rubocop", require: "appraisal2/rubocop", optional: true
+
+# Lock/Unlock Deps Pattern
+#
+# Two often conflicting goals resolved!
+#
+#  - unlocked_deps.yml
+#    - All runtime & dev dependencies, but does not have a `gemfiles/*.gemfile.lock` committed
+#    - Uses an Appraisal2 "unlocked_deps" gemfile, and the current MRI Ruby release
+#    - Know when new dependency releases will break local dev with unlocked dependencies
+#    - Broken workflow indicates that new releases of dependencies may not work
+#
+#  - locked_deps.yml
+#    - All runtime & dev dependencies, and has a `Gemfile.lock` committed
+#    - Uses the project's main Gemfile, and the current MRI Ruby release
+#    - Matches what contributors and maintainers use locally for development
+#    - Broken workflow indicates that a new contributor will have a bad time
+#
+appraise "unlocked_deps" do
+  # Seems to be an undeclared dependency of yard.
+  # /opt/hostedtoolcache/Ruby/4.0.0/x64/lib/ruby/gems/4.0.0/gems/yard-0.9.38/lib/yard/parser/ruby/legacy/irb/slex.rb:13: warning: irb/notifier is found in irb, which is not part of the default gems since Ruby 4.0.0.
+  # You can add irb to your Gemfile or gemspec to fix this error.
+  # rake aborted!
+  # LoadError: cannot load such file -- irb/notifier (LoadError)
+  # /opt/hostedtoolcache/Ruby/4.0.0/x64/bin/bundle:25:in '<main>'
+  # But it won't install on TruffleRuby, so it can't be part of modular gemfiles used there:
+  # An error occurred while installing psych (5.3.1), and Bundler cannot continue.
+  #
+  # In ruby_3_2.gemfile:
+  #   irb was resolved to 1.16.0, which depends on
+  #     rdoc was resolved to 7.0.3, which depends on
+  #       psych
+  gem "irb", "~> 1.17" # ruby >= 2.7
+
+  eval_gemfile "modular/coverage.gemfile"
+  eval_gemfile "modular/documentation.gemfile"
+  eval_gemfile "modular/optional.gemfile"
+  eval_gemfile "modular/recording/r4/recording.gemfile"
+  eval_gemfile "modular/style.gemfile"
+  eval_gemfile "modular/x_std_libs.gemfile"
+end
+
+# Used for head (nightly) releases of ruby, truffleruby, and jruby.
+# Split into discrete appraisals if one of them needs a dependency locked discretely.
+appraise "head" do
+  eval_gemfile "modular/recording/r4/recording.gemfile"
+  eval_gemfile "modular/x_std_libs.gemfile"
+end
+
+# Used for current releases of ruby, truffleruby, and jruby.
+# Split into discrete appraisals if one of them needs a dependency locked discretely.
+appraise "current" do
+  eval_gemfile "modular/recording/r4/recording.gemfile"
+  eval_gemfile "modular/x_std_libs.gemfile"
+end
+
+# Test current Rubies against head versions of runtime dependencies
+appraise "dep-heads" do
+  eval_gemfile "modular/recording/vHEAD.gemfile"
+  eval_gemfile "modular/runtime_heads.gemfile"
+end
+
+appraise "ruby-2-3" do
+  eval_gemfile "modular/recording/r2.3/recording.gemfile"
+  eval_gemfile "modular/x_std_libs/r2.3/libs.gemfile"
+end
+
+appraise "ruby-2-4" do
+  eval_gemfile "modular/recording/r2.4/recording.gemfile"
+  eval_gemfile "modular/x_std_libs/r2.4/libs.gemfile"
+end
+
+appraise "ruby-2-5" do
+  eval_gemfile "modular/recording/r2.5/recording.gemfile"
+  eval_gemfile "modular/x_std_libs/r2.6/libs.gemfile"
+end
+
+appraise "ruby-2-6" do
+  eval_gemfile "modular/recording/r2.5/recording.gemfile"
+  eval_gemfile "modular/x_std_libs/r2.6/libs.gemfile"
+end
+
+appraise "ruby-2-7" do
+  eval_gemfile "modular/recording/r2.5/recording.gemfile"
+  eval_gemfile "modular/x_std_libs/r2/libs.gemfile"
+end
+
+appraise "ruby-3-0" do
+  eval_gemfile "modular/json/truffleruby_22_3.gemfile"
+  eval_gemfile "modular/json/truffleruby_23_0.gemfile"
+  eval_gemfile "modular/recording/r3/recording.gemfile"
+  eval_gemfile "modular/x_std_libs/r3.1/libs.gemfile"
+end
+
+appraise "ruby-3-1" do
+  eval_gemfile "modular/recording/r3/recording.gemfile"
+  eval_gemfile "modular/x_std_libs/r3.1/libs.gemfile"
+end
+
+appraise "ruby-3-2" do
+  eval_gemfile "modular/json/truffleruby_23_1.gemfile"
+  eval_gemfile "modular/recording/r3/recording.gemfile"
+  eval_gemfile "modular/x_std_libs/r3/libs.gemfile"
+end
+
+appraise "ruby-3-3" do
+  eval_gemfile "modular/recording/r3/recording.gemfile"
+  eval_gemfile "modular/x_std_libs/r3/libs.gemfile"
+end
+
+appraise "ruby-3-4" do
+  eval_gemfile "modular/recording/r3/recording.gemfile"
+  eval_gemfile "modular/x_std_libs/r3/libs.gemfile"
+end
+
+# Only run security audit on the latest version of Ruby
+appraise "audit" do
+  eval_gemfile "modular/x_std_libs.gemfile"
+end
+
+# Only run coverage on the latest version of Ruby
+appraise "coverage" do
+  eval_gemfile "modular/coverage.gemfile"
+  eval_gemfile "modular/optional.gemfile"
+  eval_gemfile "modular/recording/r4/recording.gemfile"
+  eval_gemfile "modular/x_std_libs.gemfile"
+end
+
+# Only run linter on the latest version of Ruby (but, in support of oldest supported Ruby version)
+appraise "style" do
+  eval_gemfile "modular/style.gemfile"
+  eval_gemfile "modular/x_std_libs.gemfile"
+end
+
+appraise "templating" do
+  eval_gemfile "modular/templating.gemfile"
+  eval_gemfile "modular/x_std_libs.gemfile"
+end

data/lib/kettle/jem/templates/Big-Time-Public-License.md.example

@@ -0,0 +1,99 @@
+# Big Time Public License
+
+Version 2.0.2
+
+<https://bigtimelicense.com/versions/2.0.2>
+
+## Purpose
+
+These terms let you use and share this software for noncommercial purposes and in small business for free, while also guaranteeing that paid licenses for big businesses will be available on fair, reasonable, and nondiscriminatory terms.
+
+## Acceptance
+
+In order to get any license under these terms, you must agree to them as both strict obligations and conditions to all your licenses.
+
+## Noncommercial Purposes
+
+You may use the software for any noncommercial purpose.
+
+## Personal Uses
+
+Personal use for research, experiment, and testing for the benefit of public knowledge, personal study, private entertainment, hobby projects, amateur pursuits, or religious observance, without any anticipated commercial application, count as use for noncommercial purposes.
+
+## Noncommercial Organizations
+
+Use by any charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization, or government institution counts as use for noncommercial purposes, regardless of the source of funding or obligations resulting from the funding.
+
+## Small Business
+
+You may use the software for the benefit of your company if it meets all these criteria:
+
+1.  had fewer than 20 total individuals working as employees and independent contractors at all times during the last tax year
+
+2.  earned less than $1,000,000 total revenue in the last tax year
+
+3.  received less than $1,000,000 total debt, equity, and other investment in the last five tax years, counting investment in predecessor companies that reorganized into, merged with, or spun out your company
+
+All dollar figures are United States dollars as of 2019.  Adjust for them inflation according to the United States Bureau of Labor Statistics' consumer price index for all urban consumers, United States city average, for all items, not seasonally adjusted, with 1982–1984=100 reference base.
+
+## Big Business
+
+You may use the software for the benefit of your company:
+
+1.  for 128 days after your company stops qualifying under [Small Business](#small-business)
+
+2.  indefinitely, if the licensor or their legal successor does not offer fair, reasonable, and nondiscriminatory terms for a commercial license for the software within 32 days of [written request](#how-to-request) and negotiate in good faith to conclude a deal
+
+## How to Request
+
+If this software includes an address for the licensor or an agent of the licensor in a standard place, such as in documentation, software package metadata, or an "about" page or screen, try to request a fair commercial license at that address.  If this package includes both online and offline addresses, try online before offline.  If you can't deliver a request that way, or this software doesn't include any addressees, spend one hour online researching an address, recording all your searches and inquiries as you go, and try any addresses that you find.  If you can't find any addresses, or if those addresses also fail, that counts as failure to offer a fair commercial license by the licensor under [Big Business](#big-business).
+
+## Fair, Reasonable, and Nondiscriminatory Terms
+
+Fair, reasonable, and nondiscriminatory terms may license the software perpetually or for a term, and may or may not cover new versions of the software.  If the licensor advertises license terms and a pricing structure for generally available commercial licenses, the licensor proposes license terms and a price as advertised, and a customer not affiliated with the licensor has bought a commercial license for the software on substantially equivalent terms in the past year, the proposal is fair, reasonable, and nondiscriminatory.
+
+## Copyright License
+
+The licensor grants you a copyright license to do everything with the software that would otherwise infringe the licensor's copyright in it for any purpose allowed by these terms.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms or the URL for them above, as well as copies of any plain-text lines beginning with `Required Notice:` that the licensor provided with the software.  For example:
+
+> Required Notice: Copyright Yoyodyne, Inc. (http://example.com)
+
+## Patent License
+
+The licensor grants you a patent license for the software that covers patent claims the licensor can license, or becomes able to license, that you would infringe by using the software.
+
+## Fair Use
+
+You may have "fair use" rights for the software under the law. These terms do not limit them.
+
+## No Other Rights
+
+These terms do not allow you to sublicense or transfer any of your licenses to anyone else, or prevent the licensor from granting licenses to anyone else.  These terms do not imply any other licenses.
+
+## Patent Defense
+
+If you make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company.
+
+## Violations
+
+The first time you are notified in writing that you have violated any of these terms, or done anything with the software not covered by your licenses, your licenses can nonetheless continue if you come into full compliance with these terms, and take practical steps to correct past violations, within 32 days of receiving notice.  Otherwise, all your licenses end immediately.
+
+## No Liability
+
+***As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.***
+
+## Definitions
+
+The **licensor** is the individual or entity offering these terms, and the **software** is the software the licensor makes available under these terms.
+
+**You** refers to the individual or entity agreeing to these terms.
+
+**Your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization.  **Control** means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise.  Control can be direct or indirect.
+
+**Your licenses** are all the licenses granted to you for the software under these terms.
+
+**Use** means anything you do with the software requiring one of your licenses.

data/lib/kettle/jem/templates/CHANGELOG.md.example

@@ -0,0 +1,33 @@
+# Changelog
+
+[![SemVer 2.0.0][📌semver-img]][📌semver] [![Keep-A-Changelog 1.0.0][📗keep-changelog-img]][📗keep-changelog]
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog][📗keep-changelog],
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
+and [yes][📌major-versions-not-sacred], platform and engine support are part of the [public API][📌semver-breaking].
+Please file a bug if you notice a violation of semantic versioning.
+
+[📌semver]: https://semver.org/spec/v2.0.0.html
+[📌semver-img]: https://img.shields.io/badge/semver-2.0.0-FFDD67.svg?style=flat
+[📌semver-breaking]: https://github.com/semver/semver/issues/716#issuecomment-869336139
+[📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
+[📗keep-changelog]: https://keepachangelog.com/en/1.0.0/
+[📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
+
+## [Unreleased]
+
+### Added
+
+### Changed
+
+### Deprecated
+
+### Removed
+
+### Fixed
+
+### Security
+
+[Unreleased]: {KJ|CHANGELOG:GL_COMPARE_URL}/HEAD

data/lib/kettle/jem/templates/CHANGELOG.transfer.md

@@ -0,0 +1,109 @@
+# kettle-jem Transferable Changelog
+
+This file contains **destination release notes**, not a record of every template
+implementation change. Add an entry only when applying the template change
+changes behavior, configuration, compatibility, packaging, documentation, or
+developer workflow for a destination gem. A replayed entry is intentionally
+inserted into that gem's `Unreleased` section and must make it pending for
+release. Do not add entries for internal template refactors, merge mechanics,
+or other changes with no destination user or developer impact.
+
+`kettle-jem-template-YYYYMMDD-NNN` is a stable replay identifier, not metadata
+that exempts the entry from the destination changelog or release state.
+
+An entry may declare destination-only applicability immediately after its
+identifier: `[if field=value & other.field!=value]`. Kettle/Jem evaluates these
+filters against a fixed project context, never transfers them to a destination
+changelog, and rejects unknown fields, values, and operators. Use filters only
+for genuine destination applicability boundaries.
+
+Available fields are `profile`, `topology`, `ruby.min`, `engine.jruby`,
+`engine.truffleruby`, `engine.alternates`, `feature.appraisals`,
+`feature.rubyforum`, `feature.rubyforum_project_tag`,
+`feature.corporate_sponsors`, `feature.organization_logo`,
+`feature.structuredmerge_driver`, `feature.dedicated_version_gem`,
+`workflow.dep_heads`, `workflow.jruby_94`, and `version_gem.mode`. Boolean
+fields accept `true` or `false`; `ruby.min` accepts normal version comparisons;
+the other fields accept `=` or `!=`.
+
+## Added
+
+- kettle-jem-template-20260720-001 [if feature.corporate_sponsors=true] - READMEs can now display configured
+  corporate sponsor logos.
+- kettle-jem-template-20260720-005 - README Support & Community links now
+  include RubyForum.
+- kettle-jem-template-20260726-001 - Projects now include YARD lint
+  configuration and documentation dependencies so documentation issues fail
+  before generated docs are refreshed.
+- kettle-jem-template-20260727-001 - Spec harness documentation now lists the
+  RSpec helpers provided by `kettle-test`.
+- kettle-jem-template-20260729-005 [if feature.rubyforum_project_tag=true] - Gemspec metadata now publishes this
+  project's RubyForum tag as `mailing_list_uri`, and support docs link to the
+  tagged RubyForum community alongside Discord.
+
+## Changed
+
+- kettle-jem-template-20260716-002 - Gemspecs now ship fewer repository-only
+  files, reducing package noise for downstream packagers.
+- kettle-jem-template-20260720-002 - Development Gemfiles now use the released
+  `tree_sitter_language_pack` gem 1.13.3 or newer by default.
+- kettle-jem-template-20260725-002 - Version specs now use `anonymous_loader` to
+  cover `version.rb` without redefining constants, or are removed when version
+  specs are not managed for the project.
+- kettle-jem-template-20260728-001 [if feature.appraisals=true] - Generated Ruby workflows now use clearer
+  setup-ruby-flash planning and can prepare appraisal-only jobs without
+  installing the main Gemfile bundle.
+- kettle-jem-template-20260801-001 - Generated README gem dashboard links now
+  use ClickGems instead of BestGems.
+
+## Fixed
+
+- kettle-jem-template-20260802-001 - Devcontainer JSON files now merge as JSONC,
+  preserving comments and trailing commas during template updates.
+- kettle-jem-template-20260801-004 - Generated organization README logos now
+  use GitHub's stable organization avatar endpoint instead of assuming a
+  matching Galtzo-hosted asset exists.
+- kettle-jem-template-20260801-003 - Generated project metadata and
+  documentation now normalize configured underscore hostnames to valid
+  hyphenated hostnames.
+- kettle-jem-template-20260801-002 - Generated RSpec helpers now normalize
+  managed configuration block bindings structurally, preventing mixed block
+  parameter names from producing invalid configuration after a merge.
+- kettle-jem-template-20260716-001 [if profile=shim] - Shim gems now package `LICENSE.md` instead
+  of a missing `LICENSE.txt` file.
+- kettle-jem-template-20260720-003 [if feature.structuredmerge_driver=true] - StructuredMerge Git diff driver config now
+  uses the installed `smorg-rb` driver command.
+- kettle-jem-template-20260720-004 [if engine.alternates=false] - MRI-only projects now omit JRuby and
+  TruffleRuby workflow jobs.
+- kettle-jem-template-20260725-001 [if engine.alternates=true] - Release pull request branches beginning
+  with `feature/release` now run JRuby and TruffleRuby workflows.
+- kettle-jem-template-20260726-002 - Generated version files now document their
+  version namespace and constants, reducing warning-only YARD lint output.
+- kettle-jem-template-20260726-003 - Coverage upload steps now treat Coveralls,
+  QLTY, and Codecov as optional, so provider outages do not fail CI when local
+  coverage thresholds still pass.
+- kettle-jem-template-20260728-002 - Generated RuboCop configs now ignore the
+  same `gemfiles/vendor/bundle` tree as `.gitignore`, so vendored dependency
+  installs are not reported as project lint debt.
+- kettle-jem-template-20260728-003 [if workflow.dep_heads=true & engine.truffleruby=true] - Generated dep-heads workflows now run
+  TruffleRuby jobs with current RubyGems and Bundler, avoiding setup failures
+  before the test suite starts.
+- kettle-jem-template-20260728-004 [if workflow.dep_heads=true & feature.appraisals=true] - Generated dep-heads workflows now use the
+  setup-ruby Bundler install path for direct appraisal Gemfiles, avoiding rv
+  lockfile parser failures on Git and path dependencies.
+- kettle-jem-template-20260728-005 - VersionGem bootstrap now creates the
+  missing canonical version spec when a project only has shim namespace version
+  specs.
+- kettle-jem-template-20260729-001 [if workflow.jruby_94=true] - Generated JRuby 9.4 workflows now use the
+  legacy manual bundle install path, avoiding setup-time Bundler full-index
+  failures against `gem.coop`.
+- kettle-jem-template-20260729-002 [if feature.dedicated_version_gem=true] - VersionGem bootstrap now preserves
+  and templates dedicated `version_gem.rb` entrypoints even when the gemspec
+  dependency is intentionally omitted, and generated anonymous-loader specs
+  cover both `version.rb` and `version_gem.rb`.
+- kettle-jem-template-20260729-003 [if ruby.min<2.2] - Old-Ruby gems below the VersionGem runtime
+  floor now get managed minimal `version.rb` files and anonymous-loader version
+  specs without adding `version_gem`.
+- kettle-jem-template-20260730-001 - Gemspec package file enumeration now runs
+  relative to the gemspec directory, so release package contents stay correct
+  even when the gemspec is loaded from another working directory.

data/lib/kettle/jem/templates/CITATION.cff.example

@@ -0,0 +1,20 @@
+cff-version: 1.2.0
+title: "{KJ|GEM_NAME}"
+message: >-
+  If you use this work and you want to cite it,
+  then you can use the metadata from this file.
+type: software
+authors:
+  - given-names: "{KJ|AUTHOR:GIVEN_NAMES}"
+    family-names: "{KJ|AUTHOR:FAMILY_NAMES}"
+    email: "{KJ|AUTHOR:EMAIL}"
+    affiliation: "{KJ|AUTHOR:DOMAIN}"
+    orcid: 'https://orcid.org/{KJ|AUTHOR:ORCID}'
+identifiers:
+  - type: url
+    value: '{KJ|README:GH_PACKAGE_SOURCE_URL}'
+    description: "{KJ|GEM_NAME}"
+repository-code: '{KJ|README:GH_PACKAGE_SOURCE_URL}'
+abstract: >-
+  {KJ|GEM_NAME}
+license: See license file

data/lib/kettle/jem/templates/CODE_OF_CONDUCT.md.example

@@ -0,0 +1,134 @@
+# 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 email 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
+[![Contact Maintainer][🚂maint-contact-img]][🚂maint-contact].
+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
+[🚂maint-contact]: http://www.railsbling.com/contact
+[🚂maint-contact-img]: https://img.shields.io/badge/Contact-Maintainer-0093D0.svg?style=flat&logo=rubyonrails&logoColor=red