Re: Copyright infringement and future of Hunspell

Really appreciate we resolved this. I have learned greatly. My mistake was really unintentional, I was not aware of possible consequences. Still would you be interested in making short video call to clear all doubts. We are available to do this right now. On 21.11.2017 13:57, Németh László

Re: Copyright infringement and future of Hunspell

On Mon, 2017-11-20 at 18:04 +, Димитриј Мијоски wrote: > Considering all the input, would you be interested in updating the > license to MPL version 2. Regardless of the final outcome here, moving to MPLv2 appeals to me, if only for simplicity sake.

Re: Copyright infringement and future of Hunspell

Hi, 2017-11-17 19:44 GMT+01:00 Димитриј Мијоски : > Reverted. > https://github.com/hunspell/hunspell/commit/58dfe79637982c5c49658c57c3b01d 4f44c07c19 > I guess everybody should be happy now. Life goes on. I won't touch > version 1 code any more. Thanks for reverting.

Re: Copyright infringement and future of Hunspell

Hello Németh László, hopefully you noticed that I fixed the issue you raised and reverted things to where they were. Considering all the input, would you be interested in updating the license to MPL version 2. That license can be practically used as a drop-in replacement of the tri-license

Re: Copyright infringement and future of Hunspell

On 17.11.2017 22:48, Wol's lists wrote: > Except that LGPL2 at least contains bugs that result in > unexpected/unwanted liabilities. > Maybe that's why it got updated to LGPL v3? I have not read v2, i know only v3 and look fine to me. > Some projects avoid (L)GPL on political grounds. > I

Re: Copyright infringement and future of Hunspell

Reverted. https://github.com/hunspell/hunspell/commit/58dfe79637982c5c49658c57c3b01d4f44c07c19 I guess everybody should be happy now. Life goes on. I won't touch version 1 code any more. On 17.11.2017 15:21, Rene Engelhard wrote: > > But not Apache, for example. > Can you explain how is this?

Re: Copyright infringement and future of Hunspell

On Wed, Nov 15, 2017 at 06:03:30PM +, Димитриј Мијоски wrote: >I don't see any copyright infringement, as Hunspell allowed LGPLv2.1 or >later, which safely allows us to put out derivative work to LGPLv3. And >also, ALL copyright notices were kept. But you didn't ask the copyrigh

Re: Copyright infringement and future of Hunspell

On Wed, 2017-11-15 at 18:03 +, Димитриј Мијоски wrote: > Hello Nemeth Laszlo, > > I don't see any copyright infringement, as Hunspell allowed LGPLv2.1 > or later, which safely allows us to put out derivative work to > LGPLv3. Sure, if you were forking hunspell to create something else and

Re: Copyright infringement and future of Hunspell

Hi guys, Димитриј Мијоски wrote: > I don't see any copyright infringement, as Hunspell allowed LGPLv2.1 > or later, which safely allows us to put out derivative work to > LGPLv3. And also, ALL copyright notices were kept. > With LibreOffice being one of the major downstream consumers of

Re: Copyright infringement and future of Hunspell

Hello Nemeth Laszlo, I don't see any copyright infringement, as Hunspell allowed LGPLv2.1 or later, which safely allows us to put out derivative work to LGPLv3. And also, ALL copyright notices were kept. You can answered much earlier, we created issues both about Mozilla funding and about

Re: Copyright infringement and future of Hunspell

Dear László, Thanks for your message and I understand you might be concerned. If you want, we can schedule an on-line meeting in order to discuss this further and hopefully find suitable answers for your questions. Me and Dimitrij regularly discuss the project on Jitsi. Would you like to join us