mime-types-data 3.2023.1205 → 3.2024.1105

Sign up to get free protection for your applications and to get access to all the features.
Files changed (31) hide show
  1. checksums.yaml +4 -4
  2. data/Code-of-Conduct.md +99 -46
  3. data/Contributing.md +40 -81
  4. data/History.md +230 -177
  5. data/Licence.md +1 -1
  6. data/Manifest.txt +3 -0
  7. data/Rakefile +1 -2
  8. data/SECURITY.md +7 -0
  9. data/data/content_type_mime.db +4 -3
  10. data/data/ext_mime.db +5 -3
  11. data/data/mime-types.json +1 -1
  12. data/data/mime.content_type.column +65 -5
  13. data/data/mime.docs.column +60 -0
  14. data/data/mime.encoding.column +60 -0
  15. data/data/mime.flags.column +65 -5
  16. data/data/mime.friendly.column +60 -0
  17. data/data/mime.pext.column +60 -0
  18. data/data/mime.use_instead.column +61 -1
  19. data/data/mime.xrefs.column +105 -45
  20. data/lib/mime/types/data.rb +1 -1
  21. data/types/application.yaml +513 -29
  22. data/types/audio.yaml +36 -8
  23. data/types/example.yaml +1 -0
  24. data/types/haptics.yaml +28 -0
  25. data/types/image.yaml +18 -2
  26. data/types/message.yaml +10 -4
  27. data/types/model.yaml +4 -0
  28. data/types/multipart.yaml +8 -0
  29. data/types/text.yaml +24 -0
  30. data/types/video.yaml +18 -8
  31. metadata +7 -17
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 0acb69292ebd66bccb44b0394e71a0e6f586c63dc7ddbab44f08f686c011a3a8
4
- data.tar.gz: 526f60d2801bb82b6cbc309e1c15cd295b221f84b7518a51ac22f77ff1f7ab21
3
+ metadata.gz: '0937eb75576c62fc7d9f0f739ae14f0f152c8c583f624d07281c5d7537cacfeb'
4
+ data.tar.gz: f9ff3c4db4325ae6f598ed4936b05fa1dd2b5423d085a6d5982e69d97550bd91
5
5
  SHA512:
6
- metadata.gz: c5b83ae4811c869591f34916dbd650440ccebe25813b59690b205706afe63c5ca5a1e6ff6b2a23e9cc4db154ab02f17da67068ab933f63ead522961603329cf3
7
- data.tar.gz: 00a776572ba0d4ae82b85f8ae2c58bfa52f597104056269df5f280f2713bb2dc68a45844d5ab2d11871e7c56769527d37d4bb558363788bcb61a675c241b3b4f
6
+ metadata.gz: c9460e457a889555adfff73b2f2979df787993992dba879180b1712ab9b95bfbef534bc707ec99b6908ccd7d76f3830d37c2ecc34a1dddf657f7a90f2702f8a7
7
+ data.tar.gz: 2ce654b768c2c2f010212a341a3dd695fe8e537a8376a0a8a3ca3882522ac41248380fc625e1fd6bf87bb0edcea4bfe41d588b8e86c506c4cb5369cf9b52b611
data/Code-of-Conduct.md CHANGED
@@ -2,74 +2,127 @@
2
2
 
3
3
  ## Our Pledge
4
4
 
5
- In the interest of fostering an open and welcoming environment, we as
6
- contributors and maintainers pledge to making participation in our project and
7
- our community a harassment-free experience for everyone, regardless of age, body
8
- size, disability, ethnicity, gender identity and expression, level of
9
- experience, nationality, personal appearance, race, religion, or sexual identity
10
- and orientation.
5
+ We as members, contributors, and leaders pledge to make participation in our
6
+ community a harassment-free experience for everyone, regardless of age, body
7
+ size, visible or invisible disability, ethnicity, sex characteristics, gender
8
+ identity and expression, level of experience, education, socio-economic status,
9
+ nationality, personal appearance, race, caste, color, religion, or sexual
10
+ identity and orientation.
11
+
12
+ We pledge to act and interact in ways that contribute to an open, welcoming,
13
+ diverse, inclusive, and healthy community.
11
14
 
12
15
  ## Our Standards
13
16
 
14
- Examples of behavior that contributes to creating a positive environment
15
- include:
17
+ Examples of behavior that contributes to a positive environment for our
18
+ community include:
16
19
 
17
- - Using welcoming and inclusive language
18
- - Being respectful of differing viewpoints and experiences
19
- - Gracefully accepting constructive criticism
20
- - Focusing on what is best for the community
21
- - Showing empathy towards other community members
20
+ - Demonstrating empathy and kindness toward other people
21
+ - Being respectful of differing opinions, viewpoints, and experiences
22
+ - Giving and gracefully accepting constructive feedback
23
+ - Accepting responsibility and apologizing to those affected by our mistakes,
24
+ and learning from the experience
25
+ - Focusing on what is best not just for us as individuals, but for the overall
26
+ community
22
27
 
23
- Examples of unacceptable behavior by participants include:
28
+ Examples of unacceptable behavior include:
24
29
 
25
- - The use of sexualized language or imagery and unwelcome sexual attention or
26
- advances
27
- - Trolling, insulting/derogatory comments, and personal or political attacks
30
+ - The use of sexualized language or imagery, and sexual attention or advances of
31
+ any kind
32
+ - Trolling, insulting or derogatory comments, and personal or political attacks
28
33
  - Public or private harassment
29
- - Publishing others' private information, such as a physical or electronic
30
- address, without explicit permission
34
+ - Publishing others' private information, such as a physical or email address,
35
+ without their explicit permission
31
36
  - Other conduct which could reasonably be considered inappropriate in a
32
37
  professional setting
33
38
 
34
- ## Our Responsibilities
39
+ ## Enforcement Responsibilities
35
40
 
36
- Project maintainers are responsible for clarifying the standards of acceptable
37
- behavior and are expected to take appropriate and fair corrective action in
38
- response to any instances of unacceptable behavior.
41
+ Community leaders are responsible for clarifying and enforcing our standards of
42
+ acceptable behavior and will take appropriate and fair corrective action in
43
+ response to any behavior that they deem inappropriate, threatening, offensive,
44
+ or harmful.
39
45
 
40
- Project maintainers have the right and responsibility to remove, edit, or reject
46
+ Community leaders have the right and responsibility to remove, edit, or reject
41
47
  comments, commits, code, wiki edits, issues, and other contributions that are
42
- not aligned to this Code of Conduct, or to ban temporarily or permanently any
43
- contributor for other behaviors that they deem inappropriate, threatening,
44
- offensive, or harmful.
48
+ not aligned to this Code of Conduct, and will communicate reasons for moderation
49
+ decisions when appropriate.
45
50
 
46
51
  ## Scope
47
52
 
48
- This Code of Conduct applies both within project spaces and in public spaces
49
- when an individual is representing the project or its community. Examples of
50
- representing a project or community include using an official project e-mail
51
- address, posting via an official social media account, or acting as an appointed
52
- representative at an online or offline event. Representation of a project may be
53
- further defined and clarified by project maintainers.
53
+ This Code of Conduct applies within all community spaces, and also applies when
54
+ an individual is officially representing the community in public spaces.
55
+ Examples of representing our community include using an official email address,
56
+ posting via an official social media account, or acting as an appointed
57
+ representative at an online or offline event.
54
58
 
55
59
  ## Enforcement
56
60
 
57
61
  Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
- reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
59
- complaints will be reviewed and investigated and will result in a response that
60
- is deemed necessary and appropriate to the circumstances. The project team is
61
- obligated to maintain confidentiality with regard to the reporter of an
62
- incident. Further details of specific enforcement policies may be posted
63
- separately.
62
+ reported to the community leaders responsible for enforcement at [INSERT CONTACT
63
+ METHOD]. All complaints will be reviewed and investigated promptly and fairly.
64
+
65
+ All community leaders are obligated to respect the privacy and security of the
66
+ reporter of any incident.
67
+
68
+ ## Enforcement Guidelines
69
+
70
+ Community leaders will follow these Community Impact Guidelines in determining
71
+ the consequences for any action they deem in violation of this Code of Conduct:
72
+
73
+ ### 1. Correction
74
+
75
+ **Community Impact**: Use of inappropriate language or other behavior deemed
76
+ unprofessional or unwelcome in the community.
77
+
78
+ **Consequence**: A private, written warning from community leaders, providing
79
+ clarity around the nature of the violation and an explanation of why the
80
+ behavior was inappropriate. A public apology may be requested.
81
+
82
+ ### 2. Warning
83
+
84
+ **Community Impact**: A violation through a single incident or series of
85
+ actions.
64
86
 
65
- Project maintainers who do not follow or enforce the Code of Conduct in good
66
- faith may face temporary or permanent repercussions as determined by other
67
- members of the project's leadership.
87
+ **Consequence**: A warning with consequences for continued behavior. No
88
+ interaction with the people involved, including unsolicited interaction with
89
+ those enforcing the Code of Conduct, for a specified period of time. This
90
+ includes avoiding interactions in community spaces as well as external channels
91
+ like social media. Violating these terms may lead to a temporary or permanent
92
+ ban.
93
+
94
+ ### 3. Temporary Ban
95
+
96
+ **Community Impact**: A serious violation of community standards, including
97
+ sustained inappropriate behavior.
98
+
99
+ **Consequence**: A temporary ban from any sort of interaction or public
100
+ communication with the community for a specified period of time. No public or
101
+ private interaction with the people involved, including unsolicited interaction
102
+ with those enforcing the Code of Conduct, is allowed during this period.
103
+ Violating these terms may lead to a permanent ban.
104
+
105
+ ### 4. Permanent Ban
106
+
107
+ **Community Impact**: Demonstrating a pattern of violation of community
108
+ standards, including sustained inappropriate behavior, harassment of an
109
+ individual, or aggression toward or disparagement of classes of individuals.
110
+
111
+ **Consequence**: A permanent ban from any sort of public interaction within the
112
+ community.
68
113
 
69
114
  ## Attribution
70
115
 
71
- This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
72
- available at [http://contributor-covenant.org/version/1/4][version]
116
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage],
117
+ version 2.1, available at
118
+ <https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
119
+
120
+ Community Impact Guidelines were inspired by
121
+ [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
122
+
123
+ For answers to common questions about this code of conduct, see the FAQ at
124
+ <https://www.contributor-covenant.org/faq>. Translations are available at
125
+ <https://www.contributor-covenant.org/translations>.
73
126
 
74
- [homepage]: http://contributor-covenant.org
75
- [version]: http://contributor-covenant.org/version/1/4/
127
+ [homepage]: https://www.contributor-covenant.org
128
+ [Mozilla CoC]: https://github.com/mozilla/diversity
data/Contributing.md CHANGED
@@ -1,4 +1,4 @@
1
- ## Contributing
1
+ # Contributing
2
2
 
3
3
  Contributions to mime-types-data is encouraged in any form: a bug report, new
4
4
  MIME type definitions, or additional code to help manage the MIME types. As with
@@ -10,8 +10,8 @@ acceptance of your code contributions:
10
10
  - Use a thoughtfully-named topic branch that contains your change. Rebase your
11
11
  commits into logical chunks as necessary.
12
12
  - Use [quality commit messages][qcm].
13
- - Do not change the version number; when your patch is accepted and a release
14
- is made, the version will be updated at that point.
13
+ - Do not change the version number; when your patch is accepted and a release is
14
+ made, the version will be updated at that point.
15
15
  - Submit a GitHub pull request with your changes.
16
16
  - New or changed behaviours require new or updated documentation.
17
17
 
@@ -21,7 +21,7 @@ implementation that wishes to use the data as a MIME types registry, so I am
21
21
  particularly interested in tools that will create a mime-types-data package for
22
22
  other languages.
23
23
 
24
- ### Adding or Modifying MIME Types
24
+ ## Adding or Modifying MIME Types
25
25
 
26
26
  The Ruby mime-types gem loads its data from files encoded in the `data`
27
27
  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
60
60
  convert the YAML to JSON, or `rake convert:yaml:columnar` to convert it to the
61
61
  new columnar format.
62
62
 
63
- #### Updating Types from the IANA or Apache Lists
63
+ ### Updating Types from the IANA or Apache Lists
64
64
 
65
65
  If you are maintaining a private fork and wish to update your copy of the MIME
66
66
  types registry used by this gem, you can do this with the rake tasks:
@@ -70,71 +70,47 @@ $ rake mime:iana
70
70
  $ rake mime:apache
71
71
  ```
72
72
 
73
- ##### A Note on Provisional Types
73
+ #### A Note on Provisional Types
74
74
 
75
- The file `types/provisional-standard-types.yaml` contains the provisionally
76
- registered types from IANA. Per IANA,
75
+ Provisionally registered types from IANA are contained in the `types/*.yaml`
76
+ files. Per IANA,
77
77
 
78
78
  > This registry, unlike some other provisional IANA registries, is only for
79
79
  > temporary use. Entries in this registry are either finalized and moved to the
80
80
  > main media types registry or are abandoned and deleted. Entries in this
81
81
  > registry are suitable for use for development and test purposes only.
82
82
 
83
- The provisional types file is rewritten when updated, so pull requests to
84
- manually promote or customize provisional types (such as with extensions). It is
85
- recommended that any updates required to the data be performed in your
86
- application if you require provisional types.
83
+ Provisional types are rewritten when updated, so pull requests to manually
84
+ customize provisional types (such as with extensions) are considered lower
85
+ priority. It is recommended that any updates required to the data be performed
86
+ in your application if you require provisional types.
87
87
 
88
- ### Development Dependencies
88
+ ## Development Dependencies
89
89
 
90
- mime-types-data uses Ryan Davis’s {Hoe}[https://github.com/seattlerb/hoe] to
91
- manage the release process, and it adds a number of rake tasks. You will mostly
92
- be interested in:
90
+ ## Test Dependencies
93
91
 
94
- ```sh
95
- $ rake
96
- ```
97
-
98
- which runs the tests the same way that:
99
-
100
- ```sh
101
- $ rake test
102
- $ rake travis
103
- ```
104
-
105
- will do.
106
-
107
- To assist with the installation of the development dependencies for
108
- mime-types-data, I have provided the simplest possible Gemfile pointing to the
109
- (generated) `mime-types-data.gemspec` file. This will permit you to do:
110
-
111
- ```sh
112
- $ bundle install
113
- ```
114
-
115
- to get the development dependencies. If you aleady have `hoe` installed, you
116
- can accomplish the same thing with:
92
+ mime-types-data uses Ryan Davis’s [Hoe][hoe] to manage the release process, and
93
+ it adds a number of rake tasks. You will mostly be interested in `rake`, which
94
+ runs tests the same way that `rake test` does.
117
95
 
118
- ```sh
119
- $ rake newb
120
- ```
121
-
122
- This task will install any missing dependencies, run the tests/specs, and
96
+ To assist with the installation of the development dependencies for mime-types,
97
+ I have provided the simplest possible Gemfile pointing to the (generated)
98
+ `mime-types-data.gemspec` file. This permits `bundle install` for dependencies.
99
+ If you already have `hoe` installed, you can accomplish the same thing with
100
+ `rake newb`. This task will install any missing dependencies, run the tests, and
123
101
  generate the RDoc.
124
102
 
125
- You can run tests with code coverage analysis by running:
126
-
127
- ```sh
128
- $ rake test:coverage
129
- ```
103
+ You can run tests with code coverage analysis by running `rake test:coverage`.
130
104
 
131
105
  ### Workflow
132
106
 
133
107
  Here's the most direct way to get your work merged into the project:
134
108
 
135
109
  - Fork the project.
136
- - Clone down your fork (`git clone git://github.com/<username>/mime-types-data.git`).
137
- - Create a topic branch to contain your change (`git checkout -b my\_awesome\_feature`).
110
+ - Clone down your fork
111
+ (`git clone git://github.com/<username>/mime-types-data.git`).
112
+ - Create a topic branch to contain your change
113
+ (`git checkout -b my\_awesome\_feature`).
138
114
  - Hack away, add tests. Not necessarily in that order.
139
115
  - Make sure everything still passes by running `rake`.
140
116
  - If necessary, rebase your commits into logical chunks, without errors.
@@ -142,50 +118,32 @@ Here's the most direct way to get your work merged into the project:
142
118
  - Create a pull request against mime-types/mime-types-data and describe what
143
119
  your change does and the why you think it should be merged.
144
120
 
145
- ### The Release Process
121
+ ## The Release Process
146
122
 
147
- The release process needs automation; as it includes generating code and
148
- committing to the repository, it is not clear how this will happen safely.
123
+ The release process is much more automated than it used to be, as regular
124
+ updates are performed with GitHub actions on Tuesdays. Before release, however,
125
+ a final step of checking for IANA updates should be performed.
149
126
 
150
127
  1. Review any outstanding issues or pull requests to see if anything needs to be
151
- addressed. This is necessary because there is currently no automated source
152
- for extensions for the thousands of MIME entries. (Suggestions and/or pull
128
+ addressed. This is necessary because there is no automated source for
129
+ extensions for the thousands of MIME entries. (Suggestions and/or pull
153
130
  requests for same would be deeply appreciated.)
154
131
  2. `bundle install`
155
132
  3. `bundle exec rake mime:apache`
156
133
  4. `bundle exec rake mime:iana`
157
134
  5. Review the changes to make sure that the changes are sane. The IANA data
158
135
  source changes from time to time, resulting in big changes or even a broken
159
- step 4. (The most recent change was the addition of the font/\* top-level
136
+ step 4. (The most recent change was the addition of the `font/*` top-level
160
137
  category.)
161
138
  6. `bundle exec rake convert`
162
139
  7. `bundle exec rake update:version`
163
- 8. Write up the changes in History.md. If any PRs have been merged, these should
164
- be noted specifically.
140
+ 8. Write up the changes in `History.md`. If any PRs have been merged, these
141
+ should be noted specifically and contributions should be added in
142
+ `Contributing.md`.
165
143
  9. Commit the changes and push to GitHub.
166
144
  10. `bundle exec rake release VERSION=newversion`
167
145
 
168
- ### Automating the Release
169
-
170
- If anyone wishes to provide suggestions on automation, this would be a two-phase
171
- process:
172
-
173
- 1. A system would need to periodically create PRs to the GitHub repository with
174
- the output of the following commands (steps 2, 3, and 4):
175
-
176
- ```sh
177
- bundle install
178
- bundle exec rake mime:apache
179
- bundle exec rake mime:iana
180
- git add .
181
- git commit -m "[Automated] MIME Type update for $(date)"
182
- # Somehow make the PR from here.
183
- ```
184
-
185
- 2. Once this PR is approved and merged, the next steps would be conversion,
186
- version update, automatic update of History.md, and release (steps 6–10).
187
-
188
- This is based on an issue [#18][].
146
+ This is based on an issue [#18][#18].
189
147
 
190
148
  ### Contributors
191
149
 
@@ -233,6 +191,7 @@ Thanks to everyone else who has contributed to mime-types:
233
191
  - Robert Buchberger
234
192
  - Samuel Williams
235
193
  - Sergio Baptista
194
+ - Shane Eskritt
236
195
  - Tao Guo
237
196
  - Thomas Leese
238
197
  - Tibor Szolár
@@ -241,4 +200,4 @@ Thanks to everyone else who has contributed to mime-types:
241
200
 
242
201
  [qcm]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
243
202
  [rmt]: https://github.com/mime-types/ruby-mime-types/
244
- [#18]: https://github.com/mime-types/mime-types-data/issues/18
203
+ [hoe]: https://github.com/seattlerb/hoe