color 2.1.1 → 2.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2d4c9c7de02c29ef865bd03c3e91309c2880726e8919e2a0c8916b9e935fe1c6
-  data.tar.gz: acfd302f192306092af688898d9186d7460c59646dce0df698cf32e29fb6212c
+  metadata.gz: b32b311487259ef9b4a72e7264f1eaa8a34a617918829f41b629fe814b72776f
+  data.tar.gz: 9fe85bc3e862e29c0fded320e03ec77063a30e86faa205c71dbae2cc6b840f28
 SHA512:
-  metadata.gz: d7bf088dca85deeb798f0c68542fc1f1fac08e7f629e41b38c91d95537d963ce603768a290af699c5e3b71bcb3183f165c438bf8769d12fd6c84a6e0167b127b
-  data.tar.gz: 185273ad56535d55992ab8f78aec618f9b65ce6407ee68c2c5c56475660c87d536941bea440852393030369906bc55ed5daaf1da97340f8879c743b79b583edf
+  metadata.gz: 712f80bb0eb3f8f04d6144d3ca0d608546b7bdf371b03d549aae1be985f73a8f84b7e615792206f32db8caf587e68cfb66f59c75c0ee1911d3af4d34efe0ed3f
+  data.tar.gz: ec2928f2caf9b5d9614168b0109d33743a542192e0ef2a30dc0d08b2dda5b5825bd539f9b5b477c1b96ffc3a37e8ebbacd57c5b71e18bd8cb9e77c023caec323

data/CHANGELOG.md

@@ -1,4 +1,60 @@
-# Changelog
+# color Changelog
+
+## 2.2.0 / 2026-01-DD
+
+- When `color/rgb/colors` is loaded and the RGB color does not have defined
+  names, a fallback lookup to named RGB colors will be performed to use that
+  name.
+
+  ```ruby
+  simple_black = Color.from_values(r: 0, g: 0, b: 0)
+  stuart_black = Color.from_values(r: 0, g: 0, b: 0, names: ["semple-black-4.0"])
+
+  simple_black.name # => nil
+  stuart_black.name # => "semple-black-4.0"
+
+  require 'color/rgb/colors'
+
+  simple_black.name # => "black"
+  stuart_black.name # => "semple-black-4.0"
+  ```
+
+  This was suggested by [@akicho8][gh-user-akicho8] in [#89][gh-issue-89].
+
+- The RGB inspect and pretty print formats have been modified to include defined
+  names. This was suggested by @akicho8 in #89.
+
+- Added unit tests for `#pretty_print` implementations. Fixed some bugs found in
+  the implementations.
+
+## 2.1.2 / 2025-12-30
+
+- Updated to Contributor Covenant 3.0 and applied updates to several support
+  documents.
+
+- Full coverage of conversion tests. Adds CIELAB `to_yiq` and Grayscale `to_xyz`
+  methods. Only YIQ now lacks conversions support. Fixed in [#69][pull-69].
+
+- Fix an incorrect conversion of CIELAB colors with low lightness to XYZ, which
+  caused the Y component to be ~903 times larger than correct. In practice, this
+  returned unexpectedly bright colours.
+
+  This also affected conversion from CIELAB to RGB, CMYK, HSL, YIQ, and
+  grayscale, which convert from CIELAB to XYZ as an intermediate step.
+
+  Reported by [@alexwlchan][gh-user-alexwlchan] in [#95][issue-95] and fixed in [#96][pull-96].
+
+- Fix an incorrect comparison when converting CIE XYZ colors to RGB that could
+  raise a `NoMethodError` when constructing the RGB value. The conversion
+  incorrectly compared the absolute value of an intermediate value against the
+  0.0031308 threshold instead of comparing the original value, causing certain
+  negative values to follow the wrong branch and return complex RGB components.
+
+  This also affected conversion from XYZ to CMYK, HSL, and YIK, and from CIELAB
+  to RGB, HSL, YIQ, and Grayscale -- all of which convert from XYZ to RGB as an
+  intermediate step.
+
+  Reported by @alexwlchan in [#92][issue-92] and fixed in [#93][pull-93].
 
 ## 2.1.1 / 2025-08-08
 
@@ -15,7 +71,7 @@ and adds more Color::XYZ white points for standard illuminants.
   was seen in `Color::RGB#to_lab` since CIELAB conversions must go through the
   XYZ color model. Even though we were using the D65 white point, the Z value
   was being clamped to 1.0 instead of the correct value of ≅1.08. Reported by
-  @r-plus in [#45][issue-45] and fixed in [#45][pr-46].
+  @r-plus in [#45][issue-45] and fixed in [#45][pull-46].
 
   The resulting Color::LAB values are not _exactly_ the same values under Color
   1.8, but they are within fractional differences deemed acceptable.
@@ -99,8 +155,8 @@ this release without prior warning.
 ### 🚀 New Features
 
 - `Color::CIELAB` and `Color::XYZ` namespaces have been added. Separate
-  implementations were submitted by David Heitzman and @stiff (in [#8][pr-8] and
-  [#11][pr-11]), but I have reworked the code substantially. These
+  implementations were submitted by David Heitzman and @stiff (in [#8][pull-8]
+  and [#11][pull-11]), but I have reworked the code substantially. These
   implementations were originally as `Color::LAB` and include a new contrast
   calculation using the ΔE\*00 algorithm.
 
@@ -111,7 +167,7 @@ this release without prior warning.
   automated releases are enabled), full GitHub Actions, Dependabot, Standard
   Ruby, and more.
 
-- Charles Nutter re-added JRuby support in CI. [#36][pr-36]
+- Charles Nutter re-added JRuby support in CI. [#36][pull-36]
 
 ### Governance
 
@@ -140,23 +196,22 @@ ownership to contribute it to this project under the licence terms.
   by Eric Meyer. For purposes of backwards compatibility, the previous name is
   still permitted, but its use is strongly discouraged, and it will be removed
   in the Color 2.0 release.
-  <http://meyerweb.com/eric/thoughts/2014/06/19/rebeccapurple/>
+  <https://meyerweb.com/eric/thoughts/2014/06/19/rebeccapurple/>
 
 ## 1.7 / 2014-06-12
 
-- Added `Color::RGB::BeccaPurple` (#663399) in honour of Rebecca Meyer, the
-  daughter of Eric Meyer, who passed away on the 7 June 2014. Her favourite
-  color was purple. `#663399becca`
-  <https://twitter.com/meyerweb/status/476089708674428929>
-  <http://www.zeldman.com/2014/06/10/the-color-purple/>
-  <http://discourse.specifiction.org/t/name-663399-becca-purple-in-css4-color/225>
+- Added `Color::RGB::BeccaPurple` ([#663399][gh-issue-663399]) in honour of Rebecca Meyer, the
+  daughter of Eric Meyer, who passed away on 7 June 2014. Her favourite color
+  was purple. `#663399becca`
+  <https://www.zeldman.com/2014/06/10/the-color-purple/>
+  <https://discourse.wicg.io/t/name-663399-becca-purple-in-css4-color/225/>
 
 - Changed the homepage in the gem to point to GitHub instead of RubyForge, which
-  has been shut down. Fixes [#10][issue-10], reported by @voxik.
+  has been shut down. Fixes [#10][issue-10], reported by [@voxik][gh-user-voxik].
 
 ## 1.6 / 2014-05-19
 
-- Aaron Hill (@armahillo) implemented the CIE Delta E 94 method by which an RGB
+- Aaron Hill ([@armahillo][gh-user-armahillo]) implemented the CIE Delta E 94 method by which an RGB
   color can be asked for the closest matching color from a list of provided
   colors. Fixes [#5][issue-5].
 
@@ -191,7 +246,7 @@ ownership to contribute it to this project under the licence terms.
   this work, color classes should `include` Color only need to implement
   `#coerce(other)`, `#to_a`, and supported conversion methods (e.g., `#to_rgb`).
 
-- Added @daveheitzman's initial implementation of a RGB contrast method as an
+- Added [@daveheitzman][gh-user-daveheitzman]'s initial implementation of a RGB contrast method as an
   extension file: `require 'color/rgb/contrast'`. This method and the value it
   returns should be considered experimental; it requires further examination to
   ensure that the results produced are consistent with the contrast comparisons
@@ -338,8 +393,25 @@ ownership to contribute it to this project under the licence terms.
 [issue-10]: https://github.com/halostatue/color/issues/10
 [issue-30]: https://github.com/halostatue/color/issues/30
 [issue-45]: https://github.com/halostatue/color/issues/45
-[pr-11]: https://github.com/halostatue/color/pull/11
-[pr-36]: https://github.com/halostatue/color/pull/36
-[pr-46]: https://github.com/halostatue/pull/46
-[pr-8]: https://github.com/halostatue/color/pulls/8
+[issue-4]: https://github.com/halostatue/color/issues/4
+[issue-5]: https://github.com/halostatue/color/issues/5
+[issue-92]: https://github.com/halostatue/color/issues/92
+[issue-95]: https://github.com/halostatue/color/issues/95
+[pull-11]: https://github.com/halostatue/color/pull/11
+[pull-15]: https://github.com/halostatue/color/pull/15
+[pull-18]: https://github.com/halostatue/color/pull/18
+[pull-24]: https://github.com/halostatue/color/pull/24
+[pull-36]: https://github.com/halostatue/color/pull/36
+[pull-46]: https://github.com/halostatue/color/pull/46
+[pull-69]: https://github.com/halostatue/color/pull/69
+[pull-8]: https://github.com/halostatue/color/pulls/8
+[pull-93]: https://github.com/halostatue/color/pull/93
+[pull-96]: https://github.com/halostatue/color/pull/96
 [wp-std-illuminant]: https://en.wikipedia.org/wiki/Standard_illuminant#White_points_of_standard_illuminants
+[gh-user-akicho8]: https://github.com/akicho8
+[gh-issue-89]: https://github.com/halostatue/color/issues/89
+[gh-user-alexwlchan]: https://github.com/alexwlchan
+[gh-issue-663399]: https://github.com/halostatue/color/issues/663399
+[gh-user-voxik]: https://github.com/voxik
+[gh-user-armahillo]: https://github.com/armahillo
+[gh-user-daveheitzman]: https://github.com/daveheitzman

data/CODE_OF_CONDUCT.md

@@ -1,128 +1,166 @@
-# Contributor Covenant Code of Conduct
+# Contributor Covenant 3.0 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.
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the
+dignity, rights, and contributions of all individuals, regardless of
+characteristics including race, ethnicity, caste, color, age, physical
+characteristics, neurodiversity, disability, sex or gender, gender identity or
+expression, sexual orientation, language, philosophy or religion, national or
+social origin, socio-economic position, level of education, or other status. The
+same privileges of participation are extended to everyone who participates in
+good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our
+community's expectations for positive behavior. We also understand that our
+words and actions may be interpreted differently than we intend based on
+culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each
+other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of
+   gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our
+   community**.
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances,
+threats, and promotion of these behaviors are violations of this Code of
+Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in
+   unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments
+   directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or
+   behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered
+   inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or
+   private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm
+   toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or
+   pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content
+   you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a
+   way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which
+   includes, links or describes any other restricted behaviors.
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their
+best to collaborate. Not every conflict represents a code of conduct violation,
+and this Code of Conduct reinforces encouraged behaviors and norms that can help
+avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a
+possible violation, create a [private security advisory][advisory] — violations
+of this code of conduct are considered security vulnerabilities.
+
+Community Moderators take reports of violations seriously and will make every
+effort to respond in a timely manner. They will investigate all reports of code
+of conduct violations, reviewing messages, logs, and recordings, or interviewing
+witnesses and other participants. Community Moderators will keep investigation
+and enforcement actions as transparent as possible while prioritizing safety and
+confidentiality. In order to honor these values, enforcement actions are carried
+out in private with the involved parties, but communicating to the whole
+community may be part of a mutually agreed upon resolution.
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct
+has been violated, the following enforcement ladder may be used to determine how
+best to repair harm, based on the incident's impact on the individuals involved
+and the community as a whole. Depending on the severity of a violation, lower
+rungs on the ladder may be skipped.
+
+1. Warning
+   1. Event: A violation involving a single incident or series of incidents.
+   2. Consequence: A private, written warning from the Community Moderators.
+   3. Repair: Examples of repair include a private written apology,
+      acknowledgement of responsibility, and seeking clarification on
+      expectations.
+
+2. Temporarily Limited Activities
+   1. Event: A repeated incidence of a violation that previously resulted in a
+      warning, or the first incidence of a more serious violation.
+   2. Consequence: A private, written warning with a time-limited cooldown
+      period designed to underscore the seriousness of the situation and give
+      the community members involved time to process the incident. The cooldown
+      period may be limited to particular communication channels or interactions
+      with particular community members.
+   3. Repair: Examples of repair may include making an apology, using the
+      cooldown period to reflect on actions and impact, and being thoughtful
+      about re-entering community spaces after the period is over.
+
+3. Temporary Suspension
+   1. Event: A pattern of repeated violation which the Community Moderators have
+      tried to address with warnings, or a single serious violation.
+   2. Consequence: A private written warning with conditions for return from
+      suspension. In general, temporary suspensions give the person being
+      suspended time to reflect upon their behavior and possible corrective
+      actions.
+   3. Repair: Examples of repair include respecting the spirit of the
+      suspension, meeting the specified conditions for return, and being
+      thoughtful about how to reintegrate with the community when the suspension
+      is lifted.
+
+4. Permanent Ban
+   1. Event: A pattern of repeated code of conduct violations that other steps
+      on the ladder have failed to resolve, or a violation so serious that the
+      Community Moderators determine there is no way to keep the community safe
+      with this person as a member.
+   2. Consequence: Access to all community spaces, tools, and communication
+      channels is removed. In general, permanent bans should be rarely used,
+      should have strong reasoning behind them, and should only be resorted to
+      if working through other remedies has failed to change the behavior.
+   3. Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the
+ability of Community Managers to use their discretion and judgment, in keeping
+with the best interests of our community.
 
 ## 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
+an individual is officially representing the community in public or other
+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 [INSERT 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>.
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0,
+permanently available at <https://www.contributor-covenant.org/version/3/0/>.
 
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+Contributor Covenant is stewarded by the Organization for Ethical Source and
+licensed under CC BY-SA 4.0. To view a copy of this license, visit
+<https://creativecommons.org/licenses/by-sa/4.0/>.
 
-For answers to common questions about this code of conduct, see the FAQ at
-<https://www.contributor-covenant.org/faq>. Translations are available at
-<https://www.contributor-covenant.org/translations>.
+For answers to common questions about Contributor Covenant, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are provided at
+<https://www.contributor-covenant.org/translations>. Additional enforcement and
+community guideline resources can be found at
+<https://www.contributor-covenant.org/resources>. The enforcement ladder was
+inspired by the work of [Mozilla’s code of conduct team][inclusion].
 
-[homepage]: https://www.contributor-covenant.org
-[Mozilla CoC]: https://github.com/mozilla/diversity
+[advisory]: https://github.com/halostatue/color/security/advisories/new
+[inclusion]: https://github.com/mozilla/inclusion

data/CONTRIBUTING.md

@@ -1,84 +1,123 @@
 # Contributing
 
-Contribution to color is encouraged: bug reports, feature requests, or code
-contributions. There are a few DOs and DON'Ts that should be followed.
+Contribution to Color is encouraged: bug reports, feature requests, or code
+contributions. New features should be proposed and discussed in an
+[issue][issues].
 
-## DO
+Before contributing patches, please read the [Licence](./LICENCE.md).
 
-- Keep the coding style that already exists for any updated Ruby code (support
-  or otherwise). I use [Standard Ruby][standardrb] for linting and formatting.
+Color is governed under the [Contributor Covenant Code of Conduct][cccoc].
 
-- Use thoughtfully-named topic branches for contributions. Rebase your commits
-  into logical chunks as necessary.
+## Code Guidelines
 
-- Use [quality commit messages][qcm].
+I have several guidelines to contributing code through pull requests:
 
-- Add your name or GitHub handle to `CONTRIBUTORS.md` and a record in the
-  `CHANGELOG.md` as a separate commit from your main change. (Follow the style
-  in the `CHANGELOG.md` and provide a link to your PR.)
+- All code changes require tests. In most cases, this will be added or updated
+  unit tests. I use [Minitest][minitest].
 
-- Add or update tests as appropriate for your change. The test suite is written
-  with [minitest][minitest].
+- I use code formatters, static analysis tools, and linting to ensure consistent
+  styles and formatting. There should be no warning output from test run
+  processes. I use [Standard Ruby][standardrb].
 
-- Add or update documentation as appropriate for your change. The documentation
-  is RDoc; color does not use extensions that may be present in alternative
-  documentation generators.
+- Proposed changes should be on a thoughtfully-named topic branch and organized
+  into logical commit chunks as appropriate.
 
-## DO NOT
+- Use [Conventional Commits][conventional] with my
+  [conventions](#commit-conventions).
 
-- Modify `VERSION` in `lib/color/version.rb`. When your patch is accepted and a
-  release is made, the version will be updated at that point.
+- Versions must not be updated in pull requests unless otherwise directed. This
+  means that you must not:
 
-- Modify `color.gemspec`; it is a generated file. (You _may_ use `rake gemspec`
-  to regenerate it if your change involves metadata related to gem itself).
+  - Modify `VERSION` in `lib/color/version.rb`. When your patch is accepted and
+    a release is made, the version will be updated at that point.
 
-- Modify the `Gemfile`.
+  - Modify `color.gemspec`; it is a generated file. (You _may_ use
+    `rake gemspec` to regenerate it if your change involves metadata related to
+    gem itself).
 
-## LLM-Generated Contribution Policy
+  - Modify the `Gemfile`.
 
-Color is a library full of complex math and subtle decisions (some of them
-possibly even wrong). It is extremely important that any issues or pull requests
-be well understood by the submitter and that, especially for pull requests, the
-developer can attest to the [Developer Certificate of Origin][dco] for each pull
-request (see [LICENCE](LICENCE.md)).
+- Documentation should be added or updated as appropriate for new or updated
+  functionality. The documentation is RDoc; color does not use extensions that
+  may be present in alternative documentation generators.
+
+- All GitHub Actions checks marked as required must pass before a pull request
+  may be accepted and merged.
+
+- Add your name or GitHub handle to `CONTRIBUTORS.md` and a record in the
+  `CHANGELOG.md` as a separate commit from your main change. (Follow the style
+  in the `CHANGELOG.md` and provide a link to your PR.)
 
-If LLM assistance is used in writing pull requests, this must be documented in
-the commit message and pull request. If there is evidence of LLM assistance
-without such declaration, the pull request **will be declined**.
+- Include your DCO sign-off in each commit message (see [LICENCE](LICENCE.md)).
 
-Any contribution (bug, feature request, or pull request) that uses unreviewed
-LLM output will be rejected.
+## AI Contribution Policy
+
+Color is a library full of complex math and subtle decisions (some of them
+possibly even wrong). It is extremely important that contributions of any sort
+be well understood by the submitter and that the developer can attest to the
+[Developer Certificate of Origin][dco] for each pull request (see
+[LICENCE](LICENCE.md)).
+
+Any contribution (bug, feature request, or pull request) that uses undeclared AI
+output will be rejected.
 
 ## Test Dependencies
 
-color uses Ryan Davis's [Hoe][Hoe] to manage the release process, and it adds a
+Color uses Ryan Davis's [Hoe][Hoe] to manage the release process, and it adds a
 number of rake tasks. You will mostly be interested in `rake`, which runs the
 tests the same way that `rake test` will do.
 
-To assist with the installation of the development dependencies for mime-types,
-I have provided the simplest possible Gemfile pointing to the (generated)
+To assist with the installation of the development dependencies for color, I
+have provided the simplest possible Gemfile pointing to the (generated)
 `color.gemspec` file. This will permit you to do `bundle install` to get the
 development dependencies.
 
 You can run tests with code coverage analysis by running `rake coverage`.
 
-## Workflow
+## Commit Conventions
+
+Color has adopted a variation of the Conventional Commits format for commit
+messages. The following types are permitted:
+
+| Type    | Purpose                                               |
+| ------- | ----------------------------------------------------- |
+| `feat`  | A new feature                                         |
+| `fix`   | A bug fix                                             |
+| `chore` | A code change that is neither a bug fix nor a feature |
+| `docs`  | Documentation updates                                 |
+| `deps`  | Dependency updates, including GitHub Actions.         |
+
+I encourage the use of [Tim Pope's][tpope-qcm] or [Chris Beam's][cbeams]
+guidelines on the writing of commit messages
+
+I require the use of [git][trailers1] [trailers][trailers2] for specific
+additional metadata and strongly encourage it for others. The conditionally
+required metadata trailers are:
+
+- `Breaking-Change`: if the change is a breaking change. **Do not** use the
+  shorthand form (`feat!(scope)`) or `BREAKING CHANGE`.
+
+- `Signed-off-by`: this is required for all developers except me, as outlined in
+  the [Licence](./LICENCE.md#developer-certificate-of-origin).
 
-Here's the most direct way to get your work merged into the project:
+- `Fixes` or `Resolves`: If a change fixes one or more open [issues][issues],
+  that issue must be included in the `Fixes` or `Resolves` trailer. Multiple
+  issues should be listed comma separated in the same trailer:
+  `Fixes: #1, #5, #7`, but _may_ appear in separate trailers. While both `Fixes`
+  and `Resolves` are synonyms, only _one_ should be used in a given commit or
+  pull request.
 
-- Fork the project.
-- Clone down your fork (`git clone git://github.com/<username>/color.git`).
-- Create a topic branch to contain your change
-  (`git checkout -b my_awesome_feature`).
-- Hack away, add tests. Not necessarily in that order.
-- Make sure everything still passes by running `rake`.
-- If necessary, rebase your commits into logical chunks, without errors.
-- Push the branch up (`git push origin my_awesome_feature`).
-- Create a pull request against halostatue/color and describe what your change
-  does and the why you think it should be merged.
+- `Related to`: If a change does not fix an issue, those issue references should
+  be included in this trailer.
 
+[cbeams]: https://cbea.ms/git-commit/
+[cccoc]: ./CODE_OF_CONDUCT.md
+[conventional]: https://www.conventionalcommits.org/en/v1.0.0/
 [dco]: licences/dco.txt
 [hoe]: https://github.com/seattlerb/hoe
+[issues]: https://github.com/halostatue/color/issues
 [minitest]: https://github.com/seattlerb/minitest
-[qcm]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
 [standardrb]: https://github.com/standardrb/standard
+[tpope-qcm]: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[trailers1]: https://git-scm.com/docs/git-interpret-trailers
+[trailers2]: https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---trailerlttokengtltvaluegt

data/CONTRIBUTORS.md

@@ -6,7 +6,12 @@
 - Thomas Sawyer
 - Aaron Hill (CIE94 color matching)
 - Luke Bennellick
-- @stiff (CIELAB color support)
-- @r-plus
+- [@stiff][gh-user-stiff] (CIELAB color support)
+- [@r-plus][gh-user-r-plus]
 - Matthew Draper
 - Charles Nutter
+- Paul Gallagher
+- Alex Chan
+
+[gh-user-stiff]: https://github.com/stiff
+[gh-user-r-plus]: https://github.com/r-plus