Re: [Moses-support] Dual Licensing or relicensing Moses

Seems worth a shot. I suggest contacting each of them with individual emails until (and if) you get a “no”. matt (from my phone) > Le 10 avr. 2018 à 19:26, liling tan a écrit : > > @Matt I'm not sure whether that'll work. > > > For tokenizer, that'll include: > >

Re: [Moses-support] Dual Licensing or relicensing Moses

@Matt I'm not sure whether that'll work. For tokenizer, that'll include: - [image: @phikoehn] phikoehn - [image: @hieuhoang] hieuhoang - [image: @bhaddow] bhaddow - [image: @jimregan] jimregan

Re: [Moses-support] Dual Licensing or relicensing Moses

Looks like 19 people when the nonbreaking_prefixes is included and multiple e-mail addresses for the same person are collapsed. git log tokenizer.perl ../share/nonbreaking_prefixes/* |grep Author |sort -u Some of whom have invalid e-mail addresses, but can probably be tracked down. Kenneth On

Re: [Moses-support] Dual Licensing or relicensing Moses

Liling—Would it work to get the permission of just those people who are in the commit log of the specific scripts you want to port? matt (from my phone) > Le 10 avr. 2018 à 18:19, liling tan a écrit : > > Got it. > > So I think we'll just remove the MosesTokenizer and

Re: [Moses-support] Dual Licensing or relicensing Moses

Got it. So I think we'll just remove the MosesTokenizer and MosesDetokenizer function from NLTK and maybe create a PR to put it in mosesdecoder/scripts/tokenizer Thank you for the clarification! Liling On Wed, Apr 11, 2018 at 12:17 AM, Hieu Hoang wrote: > Still the same

Re: [Moses-support] Dual Licensing or relicensing Moses

Still the same problem - everyone owns Moses so you need everyone's permission, not just mine. So no Hieu Hoang http://moses-smt.org/ On 10 April 2018 at 17:13, liling tan wrote: > I understand. > > Could we have permission that it's okay to derive work from Moses with >

Re: [Moses-support] Dual Licensing or relicensing Moses

I understand. Could we have permission that it's okay to derive work from Moses with respect to the (de-)tokenizer and possibly other scripts under an MIT/Apache tool? Legally it's a restriction but I think for what's it worth, having mutual agreement between the OSS is sufficient to still keep

Re: [Moses-support] Dual Licensing or relicensing Moses

we can't change the license, or dual license it, without the agreement of everyone who's contributed to Moses. Too much work Hieu Hoang http://moses-smt.org/ On 10 April 2018 at 15:47, liling tan wrote: > Dear Moses Dev, > > NLTK has a Python port of the word tokenizer in

[Moses-support] Dual Licensing or relicensing Moses

Dear Moses Dev, NLTK has a Python port of the word tokenizer in Moses. The tokenizer works well in Python and create a good synergy to bridge Python users to the code that Moses developers have spent years to hone. But it seemed to have hit a wall with some licensing issues.