mime-types 1.17.2 → 3.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 7023816dbfc18473c51bed6f14864322167273fe
+  data.tar.gz: d29e9c15601cca71c991bc5cc1b50b31c1864d74
+SHA512:
+  metadata.gz: 1e7ba49d9b78b1331085a956c9c4c6c24687e7f69443bc00370b4e233874d32d28067d9171d50d14b14ea2bd4885a9b452b6ccc0a1fd179283855aebf9a23a3d
+  data.tar.gz: 7aa2a2ff6b297ed18a4feb6029d30b051fcc87bcd6d7aa6be37be3b9caa15e4207756614c729322e62592ae71abc5beeafbae40959194719fb11ac8acbfde2d9

data/.autotest

@@ -0,0 +1,35 @@
+# -*- ruby -*-
+
+require 'autotest/bundler'
+require 'autotest/restart'
+require 'autotest/timestamp'
+
+def require_plugin(resource)
+  require resource
+rescue LoadError
+  false
+end
+
+require_plugin 'autotest/clear'
+
+Autotest.add_hook :initialize do |at|
+  # at.testlib = "minitest/unit"
+  #
+  # at.extra_files << "../some/external/dependency.rb"
+  #
+  # at.libs << ":../some/external"
+  #
+  # at.add_exception "vendor"
+  #
+  # at.add_mapping(/dependency.rb/) do |f, _|
+  #   at.files_matching(/test_.*rb$/)
+  # end
+  #
+  # %w(TestA TestB).each do |klass|
+  #   at.extra_class_map[klass] = "test/test_misc.rb"
+  # end
+end
+
+# Autotest.add_hook :run_command do |at|
+#   system "rake build"
+# end

data/.gitignore

@@ -0,0 +1,17 @@
+*.md
+*.swp
+*~
+.rake_tasks~
+.source_index
+.vagrant
+Gemfile.lock
+Vagrantfile
+coverage
+doc
+html
+pkg
+publish
+test/cache.tst
+tmp/
+.rubocop.yml
+.byebug_history

data/.hoerc

@@ -1,12 +1,20 @@
---- 
-publish_on_announce: false
-exclude: !ruby/regexp /\.(?:svn|git)|(?:\.(?:swp|hoerc|DS_Store)|~|email.txt)$|(?:coverage|type-lists)\//
-signing_key_file: ~/.gem/gem-private_key.pem
-signing_cert_file: ~/.gem/gem-public_cert.pem
-blogs: 
-- user: user
-  url: url
-  extra_headers: 
-    mt_convert_breaks: markdown
-  blog_id: blog_id
-  password: password
+---
+exclude: !ruby/regexp '/
+  \.(tmp|swp)$
+  |
+  (CVS|tmp)\/
+  |
+  (?i:TAGS)
+  |
+  \.(svn|git|hg|DS_Store|idea|vagrant)\/
+  |
+  Gemfile(?:\.lock)?
+  |
+  \.(rubocop|coveralls|pullreview|travis).yml$
+  |
+  \.gemspec
+  |
+  \.byebug_history
+  |
+  Vagrantfile
+  /x'

data/Code-of-Conduct.rdoc

@@ -0,0 +1,41 @@
+==  Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of
+fostering an open and welcoming community, we pledge to respect all people who
+contribute through reporting issues, posting feature requests, updating
+documentation, submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free
+experience for everyone, regardless of level of experience, gender, gender
+identity and expression, sexual orientation, disability, personal appearance,
+body size, race, ethnicity, age, religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing other's private information, such as physical or electronic
+  addresses, without explicit permission
+* Other unethical or unprofessional conduct.
+
+Project maintainers 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. By adopting this Code of Conduct,
+project maintainers commit themselves to fairly and consistently applying these
+principles to every aspect of managing this project. Project maintainers who do
+not follow or enforce the Code of Conduct may be permanently removed from the
+project team.
+
+This code of conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by opening an issue or contacting one or more of the project
+maintainers.
+
+This Code of Conduct is adapted from the
+{Contributor Covenant}[http://contributor-covenant.org], version 1.2.0,
+available at
+{http://contributor-covenant.org/version/1/2/0/}[http://contributor-covenant.org/version/1/2/0/].

data/Contributing.rdoc

@@ -0,0 +1,169 @@
+== Contributing
+
+I value any contribution to mime-types you can provide: a bug report, a feature
+request, or code contributions.
+
+There are a few guidelines for contributing to mime-types:
+
+* Code changes *will* *not* be accepted without tests. The test suite is
+  written with {Minitest}[https://github.com/seattlerb/minitest].
+* Match my coding style.
+* Use a thoughtfully-named topic branch that contains your change. Rebase your
+  commits into logical chunks as necessary.
+* Use {quality commit messages}[http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html].
+* Do not change the version number; when your patch is accepted and a release
+  is made, the version will be updated at that point.
+* Submit a GitHub pull request with your changes.
+* New or changed behaviours require new or updated documentation.
+
+=== Adding or Modifying MIME Types
+
+The mime-types registry is loaded from encoded files in +data+. These are not
+editable and cannot be compared meaningfully in a pull request; pull requests
+that include changes to these files will require amendment to revert these
+files.
+
+New or modified MIME types should be edited in the appropriate YAML file under
++type-lists+. The format is as shown below for the +application/xml+ MIME type
+in +type-lists/application.yml+.
+
+  - !ruby/object:MIME::Type
+    content-type: application/xml
+    encoding: 8bit
+    extensions:
+    - xml
+    - xsl
+    xrefs: !ruby/hash:MIME::Types::Container
+      rfc:
+      - rfc3023
+    registered: true
+
+There are other fields that can be added, matching the fields discussed in the
+documentation for MIME::Type. Pull requests for MIME types should just contain
+the changes to the YAML files for the new or modified MIME types; I will
+convert the YAML files to JSON prior to a new release. I would rather not have
+to verify that the JSON matches the YAML changes, which is why it is not
+necessary to convert for the pull request.
+
+If you are making a change for a private fork, use <tt>rake
+convert:yaml:json</tt> to convert the YAML to JSON, or <tt>rake
+convert:yaml:columnar</tt> to convert it to the new columnar format.
+
+==== 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:
+
+    $ rake mime:iana
+    $ rake mime:apache
+
+Both of these require
+{Nokogiri}[http://www.nokogiri.org/tutorials/installing_nokogiri.html], which
+is not installed by default. Install it in the usual way for your Ruby.
+
+=== Test Dependencies
+
+mime-types 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:
+
+    $ rake
+
+which runs the tests the same way that:
+
+    $ rake test
+    $ rake travis
+
+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)
++mime-types.gemspec+ file. This will permit you to do:
+
+    $ bundle install
+
+to get the development dependencies. If you aleady have +hoe+ installed, you
+can accomplish the same thing with:
+
+    $ rake newb
+
+This task will install any missing dependencies, run the tests/specs, and
+generate the RDoc.
+
+You can run tests with code coverage analysis by running:
+
+    $ rake test:coverage
+
+=== Benchmarks
+
+mime-types offers several benchmark tasks to measure different measures of
+performance.
+
+There is a repeated load test, measuring how long it takes to start and load
+mime-types with its full registry. By default, it runs fifty loops and uses the
+built-in benchmark library.
+
+    $ rake benchmark:load
+
+There are two allocation tracing benchmarks (for normal and columnar loads).
+These can only be run on Ruby 2.1 or better and requires the
+{allocation_tracer}[https://github.com/ko1/allocation_tracer] gem (not
+installed by default).
+
+    $ rake benchmark:allocations
+    $ rake benchmark:allocations:columnar
+
+There are two loaded object count benchmarks (for normal and columnar loads).
+These use <tt>ObjectSpace.count_objects</tt>.
+
+    $ rake benchmark:objects
+    $ rake benchmark:objects:columnar
+
+=== Workflow
+
+Here's the most direct way to get your work merged into the project:
+
+* Fork the project.
+* Clone down your fork (<tt>git clone git://github.com/<username>/ruby-mime-types.git</tt>).
+* Create a topic branch to contain your change (<tt>git checkout -b my\_awesome\_feature</tt>).
+* 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 (<tt>git push origin my\_awesome\_feature</tt>).
+* Create a pull request against mime-types/ruby-mime-types and describe what
+  your change does and the why you think it should be merged.
+
+=== Contributors
+
+* Austin Ziegler created mime-types.
+
+Thanks to everyone else who has contributed to mime-types:
+
+* Aaron Patterson
+* Aggelos Avgerinos
+* Andre Pankratz
+* Andy Brody
+* Arnaud Meuret
+* Brandon Galbraith
+* Chris Gat
+* David Genord
+* Eric Marden
+* Garret Alfert
+* Godfrey Chan
+* Greg Brockman
+* Hans de Graaff
+* Henrik Hodne
+* Jeremy Evans
+* Juanito Fatas
+* Łukasz Śliwa
+* Keerthi Siva
+* Ken Ip
+* Martin d'Allens
+* Mauricio Linhares
+* nycvotes-dev
+* Postmodern
+* Richard Hirner
+* Richard Hurt
+* Richard Schneeman
+* Tibor Szolár
+* Todd Carrico