Re: Copyright infringement and future of Hunspell

2017-11-22 Thread Димитриј Мијоски
wrote: Hi, 2017-11-17 19:44 GMT+01:00 Димитриј Мијоски mailto:dm...@hotmail.com>>: > 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

Re: Copyright infringement and future of Hunspell

2017-11-20 Thread Димитриј Мијоски
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 and

Re: Copyright infringement and future of Hunspell

2017-11-18 Thread Димитриј Мијоски
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 persona

Re: Copyright infringement and future of Hunspell

2017-11-17 Thread Димитриј Мијоски
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? LGP

Re: Copyright infringement and future of Hunspell

2017-11-16 Thread Димитриј Мијоски
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 rel