search

deniselashlley / google-code-prettify

Automatically exported from code.google.com/p/google-code-prettify
Apache License 2.0
0 stars 0 forks source link

Migrate to MIT License? #270

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Similar as license issue generated by Twitter Bootstrap Apache 2.0 with Drupal 
GPL2+ (https://github.com/twitter/bootstrap/issues/2054), google-code-prettify 
should also not allow to be included into Drupal even now carelessly allowed 
(http://drupal.org/node/1710706#comment-7150538).

I would like to suggest migrate from Apache 2.0 license into MIT license, 
therefore we will able to include this nice library into numbers of GPL2+ 
project. Any idea?

Original issue reported on code.google.com by hswong3i@gmail.com on 8 Mar 2013 at 3:36

GoogleCodeExporter commented 9 years ago 
I can dual license the core code, but I can't unilaterally relicense 
contributed handlers.

Original comment by mikesamuel@gmail.com on 8 Mar 2013 at 6:35

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Since I am just a Drupal developer but not licensing expert, please feel free 
to correct me: what if we:
1. dual license the core code
2. contact contributed handlers authors and request for relicense
3. partly migrate handlers to MIT step by step
4. finally all in MIT?

Or from other point of approach:
1. just relicense core code in MIT + handlers that can switch license by you
2. for else contributed handlers, package as optional downloadable plugins?

The 2nd suggestion is a bit similar as Drupal's module + 3rd party libraries 
integration handling, which means in Drupal all core code + libraries 
integrated MUST be GPL2+ compatible, or else redirect end-user to download 
those incompatible license libraries and install into their local copy 
manually. This style works for Drupal's community for numbers of years ;-)

Original comment by hswong3i@gmail.com on 9 Mar 2013 at 2:17