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ó
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.
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.
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
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
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?
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
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
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
ubi
Cc: libreoffice-dev
Subject: Copyright infringement and future of Hunspell
Hi,
A week ago you modified Hunspell’s license in the official Hunspell repository
without permission of the author, me, and the main contributor and maintainer,
Caolán McNamara.
==
n good hands. If you want I can even show you
> my computer science degree with the grades.
>
>
> *From:* Németh László <nem...@numbertext.org>
> *Sent:* Wednesday, November 15, 2017 6:19:45 PM
> *To:* Dimitrij Mijoski; PanderMusu
Hi,
A week ago you modified Hunspell’s license in the official Hunspell
repository
without permission of the author, me, and the main contributor and
maintainer,
Caolán McNamara.
==
commit d49170ce949dbe0d2e6ad74b6b876e5580704a5e
Author: Dimitrij Mijoski
12 matches
Mail list logo