mime-types-data 3.2024.0820 → 3.2024.0903

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e2ed9cd13978b5b288a280c31c31517f6412d49f6c30d42767d09d7e63ab12f9
-  data.tar.gz: 792d8ec7660fdd58a27ffba329fdeb8538dfedf0eef5e3dcf2c2e28ee040c28d
+  metadata.gz: 6fe5721c3a6908abf70900e33991528076221d0bcb199676087c6ce21b0d53eb
+  data.tar.gz: 9f16b9c9eff8641527120f33cd9d4a19582f2a700409157dbb70ad94a6a76a97
 SHA512:
-  metadata.gz: fd16bc1aaec94b42d498ded768bb2e4274fa9e1701fbc82fc1f0f7466554395277d9f655f617cb64c2b9eacb2c2fb8897bae927f74e3f5815ed9eb334e0fa795
-  data.tar.gz: d1bebc6d35b7d00d5053e417c036f3bcbd1967eaf01818187773589559fa7623f5252e757aa45fddf93b4c18c6fe9a1612f010e1fff80f9e3d4b48c8b28c12e8
+  metadata.gz: e36be28b72b2822cb9050e7daf7044ff88018f47b36d1b6087f84e3f3d03a8c16fb4fcc90fe75d0dac1eb0bc0be9f38e864568d907948e061fb17310efddfab4
+  data.tar.gz: 1ba019bb39861d7295cd4914b0aa6fb5c55b35340c5e34b9e0704e7b559538ce7f4ec486b21cc376923b8a6984506284de6ebae6ca8c217a8de95bce248f9211

data/Code-of-Conduct.md

@@ -2,74 +2,127 @@
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of
-experience, nationality, personal appearance, race, religion, or sexual identity
-and orientation.
+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 creating a positive environment
-include:
+Examples of behavior that contributes to a positive environment for our
+community include:
 
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+- 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 by participants include:
+Examples of unacceptable behavior include:
 
-- The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
+- 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 electronic
-  address, without explicit permission
+- 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
 
-## Our Responsibilities
+## Enforcement Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+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.
 
-Project maintainers have the right and responsibility to remove, edit, or reject
+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, or to ban temporarily or permanently any
-contributor for other behaviors that they deem inappropriate, threatening,
-offensive, or harmful.
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+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 by contacting the project team at [INSERT EMAIL ADDRESS]. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an
-incident. Further details of specific enforcement policies may be posted
-separately.
+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.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+**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 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
+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>.
+
+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>. Translations are available at
+<https://www.contributor-covenant.org/translations>.
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+[homepage]: https://www.contributor-covenant.org
+[Mozilla CoC]: https://github.com/mozilla/diversity

data/Contributing.md

@@ -1,4 +1,4 @@
-## Contributing
+# Contributing
 
 Contributions to mime-types-data is encouraged in any form: a bug report, new
 MIME type definitions, or additional code to help manage the MIME types. As with
@@ -21,7 +21,7 @@ implementation that wishes to use the data as a MIME types registry, so I am
 particularly interested in tools that will create a mime-types-data package for
 other languages.
 
-### Adding or Modifying MIME Types
+## Adding or Modifying MIME Types
 
 The Ruby mime-types gem loads its data from files encoded in the `data`
 directory in this gem by loading `mime-types-data` and reading
@@ -60,7 +60,7 @@ If you are making a change for a private fork, use `rake convert:yaml:json` to
 convert the YAML to JSON, or `rake convert:yaml:columnar` to convert it to the
 new columnar format.
 
-#### Updating Types from the IANA or Apache Lists
+### Updating Types from the IANA or Apache Lists
 
 If you are maintaining a private fork and wish to update your copy of the MIME
 types registry used by this gem, you can do this with the rake tasks:
@@ -70,63 +70,37 @@ $ rake mime:iana
 $ rake mime:apache
 ```
 
-##### A Note on Provisional Types
+#### A Note on Provisional Types
 
-The file `types/provisional-standard-types.yaml` contains the provisionally
-registered types from IANA. Per IANA,
+Provisionally registered types from IANA are contained in the `types/*.yaml`
+files. Per IANA,
 
 > This registry, unlike some other provisional IANA registries, is only for
 > temporary use. Entries in this registry are either finalized and moved to the
 > main media types registry or are abandoned and deleted. Entries in this
 > registry are suitable for use for development and test purposes only.
 
-The provisional types file is rewritten when updated, so pull requests to
-manually promote or customize provisional types (such as with extensions). It is
-recommended that any updates required to the data be performed in your
-application if you require provisional types.
+Provisional types are rewritten when updated, so pull requests to manually
+customize provisional types (such as with extensions) are considered lower
+priority. It is recommended that any updates required to the data be performed
+in your application if you require provisional types.
 
-### Development Dependencies
+## Development Dependencies
 
-mime-types-data uses Ryan Davis’s {Hoe}[https://github.com/seattlerb/hoe] to
-manage the release process, and it adds a number of rake tasks. You will mostly
-be interested in:
+## Test Dependencies
 
-```sh
-$ rake
-```
-
-which runs the tests the same way that:
-
-```sh
-$ rake test
-$ rake travis
-```
-
-will do.
-
-To assist with the installation of the development dependencies for
-mime-types-data, I have provided the simplest possible Gemfile pointing to the
-(generated) `mime-types-data.gemspec` file. This will permit you to do:
-
-```sh
-$ bundle install
-```
-
-to get the development dependencies. If you aleady have `hoe` installed, you can
-accomplish the same thing with:
+mime-types-data 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 tests the same way that `rake test` does.
 
-```sh
-$ rake newb
-```
-
-This task will install any missing dependencies, run the tests/specs, and
+To assist with the installation of the development dependencies for mime-types,
+I have provided the simplest possible Gemfile pointing to the (generated)
+`mime-types-data.gemspec` file. This permits `bundle install` for dependencies.
+If you already have `hoe` installed, you can accomplish the same thing with
+`rake newb`. This task will install any missing dependencies, run the tests, and
 generate the RDoc.
 
-You can run tests with code coverage analysis by running:
-
-```sh
-$ rake test:coverage
-```
+You can run tests with code coverage analysis by running `rake test:coverage`.
 
 ### Workflow
 
@@ -144,49 +118,31 @@ Here's the most direct way to get your work merged into the project:
 - Create a pull request against mime-types/mime-types-data and describe what
   your change does and the why you think it should be merged.
 
-### The Release Process
+## The Release Process
 
-The release process needs automation; as it includes generating code and
-committing to the repository, it is not clear how this will happen safely.
+The release process is much more automated than it used to be, as regular
+updates are performed with GitHub actions on Tuesdays. Before release, however,
+a final step of checking for IANA updates should be performed.
 
 1. Review any outstanding issues or pull requests to see if anything needs to be
-   addressed. This is necessary because there is currently no automated source
-   for extensions for the thousands of MIME entries. (Suggestions and/or pull
+   addressed. This is necessary because there is no automated source for
+   extensions for the thousands of MIME entries. (Suggestions and/or pull
    requests for same would be deeply appreciated.)
 2. `bundle install`
 3. `bundle exec rake mime:apache`
 4. `bundle exec rake mime:iana`
 5. Review the changes to make sure that the changes are sane. The IANA data
    source changes from time to time, resulting in big changes or even a broken
-   step 4. (The most recent change was the addition of the font/\* top-level
+   step 4. (The most recent change was the addition of the `font/*` top-level
    category.)
 6. `bundle exec rake convert`
 7. `bundle exec rake update:version`
-8. Write up the changes in History.md. If any PRs have been merged, these should
-   be noted specifically.
+8. Write up the changes in `History.md`. If any PRs have been merged, these
+   should be noted specifically and contributions should be added in
+   `Contributing.md`.
 9. Commit the changes and push to GitHub.
 10. `bundle exec rake release VERSION=newversion`
 
-### Automating the Release
-
-If anyone wishes to provide suggestions on automation, this would be a two-phase
-process:
-
-1. A system would need to periodically create PRs to the GitHub repository with
-   the output of the following commands (steps 2, 3, and 4):
-
-   ```sh
-   bundle install
-   bundle exec rake mime:apache
-   bundle exec rake mime:iana
-   git add .
-   git commit -m "[Automated] MIME Type update for $(date)"
-   # Somehow make the PR from here.
-   ```
-
-2. Once this PR is approved and merged, the next steps would be conversion,
-   version update, automatic update of History.md, and release (steps 6–10).
-
 This is based on an issue [#18][#18].
 
 ### Contributors
@@ -244,4 +200,4 @@ Thanks to everyone else who has contributed to mime-types:
 
 [qcm]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
 [rmt]: https://github.com/mime-types/ruby-mime-types/
-[#18]: https://github.com/mime-types/mime-types-data/issues/18
+[hoe]: https://github.com/seattlerb/hoe

data/History.md

@@ -2,6 +2,10 @@
 
 <!-- automatic-release -->
 
+## 3.2024.0903 / 2024-09-03
+
+- Updated the Apache and IANA media registry entries as of release date
+
 ## 3.2024.0820 / 2024-08-20
 
 - Updated the Apache and IANA media registry entries as of release date.

data/Licence.md

@@ -1,6 +1,6 @@
 ## Licence
 
-- Copyright 2003–2021 Austin Ziegler and other contributors.
+- Copyright 2003–2024 Austin Ziegler and other contributors.
 
 The software in this repository is made available under the MIT license.
 

data/Manifest.txt

@@ -5,6 +5,7 @@ Licence.md
 Manifest.txt
 README.md
 Rakefile
+SECURITY.md
 data/content_type_mime.db
 data/ext_mime.db
 data/mime-types.json

data/SECURITY.md

@@ -0,0 +1,7 @@
+# mime-types Security
+
+## Security contact information
+
+To report a security vulnerability, please use the
+[Tidelift security contact](https://tidelift.com/security). Tidelift will
+coordinate the fix and disclosure.