Switch entirely to MIT (or ISC) licence for MIME-Types 3.x #95

Closed
halostatue opened this Issue Apr 25, 2015 · 12 comments

Projects

None yet

10 participants

@halostatue
Member

I should have done this for version 2.x, but I didn’t. The API for the mime-types gem is substantially different than the original Perl version, and with discussions in #94, it’s pretty clear to me that version 3 is going to be throwing out a lot of older code with newer code that I have written.

Git shows me 289 commits, 265 of which are content (non-merge) commits. 28 of these are commits related to maintenance at RubyForge (CSV and SVN management) or importing to GitHub (all 22 by Tom Copeland, all 4 by (no author), the one by Todd Carrico, and the one by unknown). 192 are by me, so those aren’t a problem.

I do not need to get license-change permission from people who have only made data registry changes, as the copyright on this is at best a collection copyright and I am mirroring data that is otherwise publicly available. That eliminates the following commit collections:

I am also excluding these commits because they are configuration-only:

@halostatue halostatue self-assigned this Apr 25, 2015
@halostatue halostatue added this to the 3.0 milestone Apr 25, 2015
@halostatue
Member

This leaves me needing accession from the following individuals for their commits either to the software or its immediately related documentation:

If the users in question see this and can add a comment indicating whether they agree with this licence change or not, we can hopefully move toward a simpler, single-licence future.

@chancancode
Contributor

I consent! 👍💛💙💜💚❤️

@postmodern
Contributor

MIT, BSD or LGPL.

@henrikhodne
Contributor

MIT or ISC is okay with me 👍

@flexik
Contributor
flexik commented Apr 25, 2015

Fine by me. 👍

@punkrats
Contributor

Even though my commits are not relevant, I'm happy with any liberal license. :)

@schneems
Contributor

Works for me, most all of my work is MIT 👍

@albus522
Contributor

Fine by me

@halostatue halostatue modified the milestone: 3.0 Apr 26, 2015
@tenderlove
Contributor

I'm fine with it.

@ameuret
Contributor
ameuret commented Jun 15, 2015

MIT FTW ! ✌🏻️

@halostatue
Member

Hoorah! MIME::Types 3.0 will be MIT-licensed only.

@halostatue
Member

While not yet released, the mime-types-3.0 branch is already MIT only.

@halostatue halostatue closed this Nov 13, 2015
@halostatue halostatue added a commit that referenced this issue Nov 21, 2015
@halostatue halostatue mime-types 3.0
- Require Ruby 2.0 or later. Resolves #97.
- Remove deprecated methods.
- Update known registries when a MIME type extension changes. Resolves #84.
- Relicensed mime-types 3.0 as MIT only. Resolves #95.
- Extracted data from this gem to mime-types-data; removed deprecated data.
- Rewrote tests to better understand what is being tested—some of the tests
  were almost ten years old and didn’t make a lot of sense with this version. I
  have switched to minitest/spec with assertions.
- Columnar data is now the default registry store.
8378025
@halostatue halostatue added a commit that referenced this issue Nov 21, 2015
@halostatue halostatue mime-types 3.0
- Require Ruby 2.0 or later. Resolves #97.
- Remove deprecated methods.
- Update known registries when a MIME type extension changes. Resolves #84.
- Relicensed mime-types 3.0 as MIT only. Resolves #95.
- Extracted data from this gem to mime-types-data; removed deprecated data.
- Rewrote tests to better understand what is being tested—some of the tests
  were almost ten years old and didn’t make a lot of sense with this version. I
  have switched to minitest/spec with assertions.
- Columnar data is now the default registry store. Because JSON is not required
  by default, this change resolves #85.
- MIME::Types containers are now implemented with Set instead of Array to
  prevent data duplication. Resolves #79.
8967fa8
@halostatue halostatue added a commit that referenced this issue Nov 21, 2015
@halostatue halostatue mime-types 3.0
- Require Ruby 2.0 or later. Resolves #97.
- Remove deprecated methods.
- Update known registries when a MIME type extension changes. Resolves #84.
- Relicensed mime-types 3.0 as MIT only. Resolves #95.
- Extracted data from this gem to mime-types-data; removed deprecated data.
- Rewrote tests to better understand what is being tested—some of the tests
  were almost ten years old and didn’t make a lot of sense with this version. I
  have switched to minitest/spec with assertions.
- Columnar data is now the default registry store. Because JSON is not required
  by default, this change resolves #85.
- MIME::Types containers are now implemented with Set instead of Array to
  prevent data duplication. Resolves #79.
026ceea
@jsonn jsonn pushed a commit to jsonn/pkgsrc that referenced this issue Dec 14, 2015
taca Update ruby-mime-types to 3.0.
== 3.0 / 2015-11-21

* 2 governance changes

  * This project and the related mime-types-data project are now exclusively
    MIT licensed. Resolves
    {#95}[mime-types/ruby-mime-types#95].

  * All projects under the mime-types organization now have a standard code of
    conduct adapted from the {Contributor
    Covenant}[http://contributor-covenant.org]. This text can be found in the
    {Code-of-Conduct.rdoc}[Code-of-Conduct_rdoc.html] file.

* 3 major changes

  * All methods deprecated in mime-types 2.x have been removed.
  * mime-types now requires Ruby 2.0 compatibility or later. Resolves
    {#97}[mime-types/ruby-mime-types#97].
  * The registry data has been removed from mime-types and put into
    mime-types-data, maintained and released separately. It can be found at
    {mime-types-data}[https://github.com/mime-types/mime-types-data].

* 17 minor changes:

  * MIME::Type changes:

    * Changed the way that simplified types representations are creatd to
      reflect the fact that +x-+ prefixes are no longer considered special
      according to IANA. A simplified MIME type is case-folded to lowercase. A
      new keyword parameter, +remove_x_prefix+, can be provided to remove +x-+
      prefixes.
    * Improved initialization with an Array works so that extensions do not
      need to be wrapped in another array. This means that <tt>%w(text/yaml
      yaml yml)</tt> works in the same way that <tt>['text/yaml', %w(yaml
      yml)]</tt> did (and still does).
    * Changed +priority_compare+ to conform with attributes that no longer
      exist.
    * Changed the internal implementation of extensions to use a frozen Set.
    * When extensions are set or modified with +add_extensions+, the primary
      registry will be informed of a need to reindex extensions. Resolves
      {#84}[mime-types/ruby-mime-types#84].
    * The preferred extension can be set explicitly. If not set, it will be the
      first extension. If the preferred extension is not in the extension list,
      it will be added.
    * Improved how xref URLs are generated.
    * Converted +obsolete+, +registered+ and +signature+ to attr_accessors.

  * MIME::Types changes:

    * Modified MIME::Types.new to track instances of MIME::Types so that they
      can be told to reindex the extensions as necessary.
    * Removed +data_version+ attribute.
    * Changed #[] so that the +complete+ and +registered+ flags are keywords
      instead of a generic options parameter.
    * Extracted the class methods to a separate file.
    * Changed the container implementation to use a Set instead of an Array to
      prevent data duplication. Resolves
      {#79}[mime-types/ruby-mime-types#79].

  * MIME::Types::Cache changes:

    * Caching is now based on the data gem version instead of the mime-types
      version.
    * Caching is compatible with columnar registry stores.

  * MIME::Types::Loader changes:

    * MIME::Types::Loader::PATH has been removed and replaced with
      MIME::Types::Data::PATH from the mime-types-data gem. The environment
      variable RUBY_MIME_TYPES_DATA is still used.
    * Support for the long-deprecated mime-types v1 format has been removed.
    * The registry is default loaded from the columnar store by default. The
      internal format of the columnar store has changed; many of the boolean
      flags are now loaded from a single file. Resolves
      {#85}[https://github.com/mime-types/ruby-mime-types/85].
db107df
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment