apache-2.0

[yoshuawuyts]

Changes the Choo license to Apache 2 as per https://github.com/choojs/discuss/issues/1. Thanks!

[goto-bus-stop]

Seems good, anything blocking this?

[YerkoPalma]

Is there any reason for this PR and #587 to be on hold?

@yoshuawuyts

[ungoldman]

This looks ok to merge once line mentioned in comment is fixed.

[brody4hire]

I am very sorry to be a pain but is this approved by all people listed in https://github.com/choojs/choo/graphs/contributors? I think this is needed to switch from MIT to Apache 2.0 license.

Bootstrap had to go through this kind of process to move from Apache 2.0 to MIT (needed to integrate with Drupal which is GPL v2) as discussed in https://github.com/twbs/bootstrap/issues/2054 (see also [1]). As described in https://github.com/twbs/bootstrap/issues/2054#issuecomment-30894685 they did have to revert and redo a few commits to do this properly.

As another example NPX has to go through the same thing to switch from CC0 to ISC license [2].

I would personally favor just adding Apache 2.0 license option if it is possible to get the needed approval. Apache 2.0 only license could be an issue in case of Drupal and other GPL v2 frameworks as discussed in https://github.com/twbs/bootstrap/issues/2054.

[1] https://opensource.stackexchange.com/questions/6097/how-does-bootstrap-v4-mit-deal-with-contributions-made-under-v3-apache-2-0 [2] https://github.com/zkat/npx/pull/132

[timwis]

That requirement sounds a bit silly, particularly if someone only PRd a typo a year ago, but for what it's worth, it's good by me!