mime-types-data 3.2024.0820 → 3.2024.0903
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/Code-of-Conduct.md +99 -46
- data/Contributing.md +32 -76
- data/History.md +4 -0
- data/Licence.md +1 -1
- data/Manifest.txt +1 -0
- data/SECURITY.md +7 -0
- data/data/mime-types.json +1 -1
- data/data/mime.content_type.column +2 -0
- data/data/mime.docs.column +2 -0
- data/data/mime.encoding.column +2 -0
- data/data/mime.flags.column +2 -0
- data/data/mime.friendly.column +2 -0
- data/data/mime.pext.column +2 -0
- data/data/mime.use_instead.column +2 -0
- data/data/mime.xrefs.column +2 -0
- data/lib/mime/types/data.rb +1 -1
- data/types/application.yaml +18 -0
- data/types/image.yaml +1 -1
- metadata +5 -3
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 6fe5721c3a6908abf70900e33991528076221d0bcb199676087c6ce21b0d53eb
|
|
4
|
+
data.tar.gz: 9f16b9c9eff8641527120f33cd9d4a19582f2a700409157dbb70ad94a6a76a97
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: e36be28b72b2822cb9050e7daf7044ff88018f47b36d1b6087f84e3f3d03a8c16fb4fcc90fe75d0dac1eb0bc0be9f38e864568d907948e061fb17310efddfab4
|
|
7
|
+
data.tar.gz: 1ba019bb39861d7295cd4914b0aa6fb5c55b35340c5e34b9e0704e7b559538ce7f4ec486b21cc376923b8a6984506284de6ebae6ca8c217a8de95bce248f9211
|
data/Code-of-Conduct.md
CHANGED
|
@@ -2,74 +2,127 @@
|
|
|
2
2
|
|
|
3
3
|
## Our Pledge
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
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
|
|
15
|
-
include:
|
|
17
|
+
Examples of behavior that contributes to a positive environment for our
|
|
18
|
+
community include:
|
|
16
19
|
|
|
17
|
-
-
|
|
18
|
-
- Being respectful of differing viewpoints and experiences
|
|
19
|
-
-
|
|
20
|
-
-
|
|
21
|
-
|
|
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
|
|
28
|
+
Examples of unacceptable behavior include:
|
|
24
29
|
|
|
25
|
-
- The use of sexualized language or imagery and
|
|
26
|
-
|
|
27
|
-
- Trolling, insulting
|
|
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
|
|
30
|
-
|
|
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
|
-
##
|
|
39
|
+
## Enforcement Responsibilities
|
|
35
40
|
|
|
36
|
-
|
|
37
|
-
behavior and
|
|
38
|
-
response to any
|
|
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
|
-
|
|
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,
|
|
43
|
-
|
|
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
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
representative at an online or offline event.
|
|
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
|
|
59
|
-
complaints will be reviewed and investigated and
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
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
|
-
|
|
66
|
-
|
|
67
|
-
|
|
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],
|
|
72
|
-
available at
|
|
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]:
|
|
75
|
-
[
|
|
127
|
+
[homepage]: https://www.contributor-covenant.org
|
|
128
|
+
[Mozilla CoC]: https://github.com/mozilla/diversity
|
data/Contributing.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
|
|
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
|
|
@@ -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
|
-
|
|
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
|
-
|
|
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,63 +70,37 @@ $ rake mime:iana
|
|
|
70
70
|
$ rake mime:apache
|
|
71
71
|
```
|
|
72
72
|
|
|
73
|
-
|
|
73
|
+
#### A Note on Provisional Types
|
|
74
74
|
|
|
75
|
-
|
|
76
|
-
|
|
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
|
-
|
|
84
|
-
|
|
85
|
-
recommended that any updates required to the data be performed
|
|
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
|
-
|
|
88
|
+
## Development Dependencies
|
|
89
89
|
|
|
90
|
-
|
|
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
|
-
|
|
95
|
-
|
|
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 can
|
|
116
|
-
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
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
This task will install any missing dependencies, run the tests
|
|
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
|
|
|
@@ -144,49 +118,31 @@ Here's the most direct way to get your work merged into the project:
|
|
|
144
118
|
- Create a pull request against mime-types/mime-types-data and describe what
|
|
145
119
|
your change does and the why you think it should be merged.
|
|
146
120
|
|
|
147
|
-
|
|
121
|
+
## The Release Process
|
|
148
122
|
|
|
149
|
-
The release process
|
|
150
|
-
|
|
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.
|
|
151
126
|
|
|
152
127
|
1. Review any outstanding issues or pull requests to see if anything needs to be
|
|
153
|
-
addressed. This is necessary because there is
|
|
154
|
-
|
|
128
|
+
addressed. This is necessary because there is no automated source for
|
|
129
|
+
extensions for the thousands of MIME entries. (Suggestions and/or pull
|
|
155
130
|
requests for same would be deeply appreciated.)
|
|
156
131
|
2. `bundle install`
|
|
157
132
|
3. `bundle exec rake mime:apache`
|
|
158
133
|
4. `bundle exec rake mime:iana`
|
|
159
134
|
5. Review the changes to make sure that the changes are sane. The IANA data
|
|
160
135
|
source changes from time to time, resulting in big changes or even a broken
|
|
161
|
-
step 4. (The most recent change was the addition of the font
|
|
136
|
+
step 4. (The most recent change was the addition of the `font/*` top-level
|
|
162
137
|
category.)
|
|
163
138
|
6. `bundle exec rake convert`
|
|
164
139
|
7. `bundle exec rake update:version`
|
|
165
|
-
8. Write up the changes in History.md
|
|
166
|
-
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`.
|
|
167
143
|
9. Commit the changes and push to GitHub.
|
|
168
144
|
10. `bundle exec rake release VERSION=newversion`
|
|
169
145
|
|
|
170
|
-
### Automating the Release
|
|
171
|
-
|
|
172
|
-
If anyone wishes to provide suggestions on automation, this would be a two-phase
|
|
173
|
-
process:
|
|
174
|
-
|
|
175
|
-
1. A system would need to periodically create PRs to the GitHub repository with
|
|
176
|
-
the output of the following commands (steps 2, 3, and 4):
|
|
177
|
-
|
|
178
|
-
```sh
|
|
179
|
-
bundle install
|
|
180
|
-
bundle exec rake mime:apache
|
|
181
|
-
bundle exec rake mime:iana
|
|
182
|
-
git add .
|
|
183
|
-
git commit -m "[Automated] MIME Type update for $(date)"
|
|
184
|
-
# Somehow make the PR from here.
|
|
185
|
-
```
|
|
186
|
-
|
|
187
|
-
2. Once this PR is approved and merged, the next steps would be conversion,
|
|
188
|
-
version update, automatic update of History.md, and release (steps 6–10).
|
|
189
|
-
|
|
190
146
|
This is based on an issue [#18][#18].
|
|
191
147
|
|
|
192
148
|
### Contributors
|
|
@@ -244,4 +200,4 @@ Thanks to everyone else who has contributed to mime-types:
|
|
|
244
200
|
|
|
245
201
|
[qcm]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
|
|
246
202
|
[rmt]: https://github.com/mime-types/ruby-mime-types/
|
|
247
|
-
[
|
|
203
|
+
[hoe]: https://github.com/seattlerb/hoe
|
data/History.md
CHANGED
data/Licence.md
CHANGED
data/Manifest.txt
CHANGED