Re: [mojo-dev] [DISCUSSION] Switching plugins to MIT license

2014-09-06 Thread David Karlsen
+1 2014-09-06 19:42 GMT+02:00 Jörg Hohwiller : > Hi there, > > In order to change the license of the source-code of an open-source > project the official procedure is that all authors that contributed > (reasonable) to the code give their agreement (potentially by signature). > This is especial

Re: [mojo-dev] [DISCUSSION] Switching plugins to MIT license

2014-09-06 Thread David Jencks
IANAL. I'm a little mystified by the motivations of your company's lawyers. To me it seems like either 1. They want the ability to sue everyone else using this software while using it themselves since someone else independently implemented a patent they hold. (in which case the patent is perh

Re: [mojo-dev] [DISCUSSION] Switching plugins to MIT license

2014-09-06 Thread Jörg Hohwiller
Hi there, In order to change the license of the source-code of an open-source project the official procedure is that all authors that contributed (reasonable) to the code give their agreement (potentially by signature). This is especially for larger projects a big procedure. I personally see

Re: [mojo-dev] [DISCUSSION] Switching plugins to MIT license

2014-09-04 Thread Dan Tran
Here is quote from our internal doc regarding apachev2 These licenses contain automatic patent licenses. Some specific technologies have been reviewed and found to be free of undesired impact on X's patent portfolio. X development organizations are approved only to use the specific technol

Re: [mojo-dev] [DISCUSSION] Switching plugins to MIT license

2014-09-04 Thread Robert Scholte
Hi, read http://www.codehaus.org/customs/licenses.html The advice is to use ASL2, although MIT is permitted. I want to hear the facts why "they say" MIT would be better. Robert Op Wed, 03 Sep 2014 21:40:48 +0200 schreef Dan Tran : OK, They are not my plugins, they belong to MOJO@codehaus th