Re: [DISCUSS] NLPCraft Proposal

2020-02-07 Thread Justin Mclean
HI, > - as the original NLPCraft developers from DataLingvo are all a part of > NLPCraft project This is not the case, but the SGA from DataLingvo will cover this. Thanks, Justin - To unsubscribe, e-mail:

Re: [DISCUSS] NLPCraft Proposal

2020-02-07 Thread Dave Fisher
Inline. Sent from my iPhone > On Feb 7, 2020, at 5:07 PM, Konstantin Boudnik wrote: > > Looks like the discussion is winding down a bit. So, to sum it up: > > - CC shall be removed during code transfer to ASF > - an SGA will be expected from DataLingvo > - as the original NLPCraft developers

Re: [DISCUSS] NLPCraft Proposal

2020-02-07 Thread Konstantin Boudnik
Looks like the discussion is winding down a bit. So, to sum it up: - CC shall be removed during code transfer to ASF - an SGA will be expected from DataLingvo - as the original NLPCraft developers from DataLingvo are all a part of NLPCraft project there is no need for explicit copyright

Re: [DISCUSS] NLPCraft Proposal

2020-02-05 Thread Konstantin Boudnik
Thanks for the offer Furkan. While we have a pretty packed house already, I think we can find a spot for one more ;) Welcome! I will update the proposal to reflect this. --   Cos On 2/4/20 5:45 AM, Furkan KAMACI wrote: Hi, I've checked your proposal, website, and blog posts and seems

Re: [DISCUSS] NLPCraft Proposal

2020-02-05 Thread Nikita Ivanov
Justin, As far as "all people signing ICLA" - we can't guarantee this as I don't think we know (or have a record of) all the people who touched the code years back (I do know main contributors - they are in this proposal). I think SGA would be the best option as it should make things clear. I

Re: [DISCUSS] NLPCraft Proposal

2020-02-05 Thread Justin Mclean
Hi, > NLPCraft came originally from DataLingvo. OK so that clarifies that there is code developed by DataLingvo in this code base. > During migration, some DataLingvo artefacts weren't properly > renamed (it should be fixed by now). I would question why they were “renamed”, while you’re not

Re: [DISCUSS] NLPCraft Proposal

2020-02-05 Thread Nikita Ivanov
Justin, et. al., NLPCraft came originally from DataLingvo. DataLingvo was a legal entity that originally developed some initial code. It has open-sourced it around 2018 along with the license change and it was developed thereafter within NLPCraft project (including by all the original developers

Re: [DISCUSS] NLPCraft Proposal

2020-02-05 Thread Justin Mclean
Hi, > perhaps the company changed it’s name but it’s the same organization? Perhaps or perhaps not, it hard to say with the information currently at hand. Hopefully the proposed project can clarify. The IP provenance of the codebase needs to be clear, removing copyright headers without

Re: [DISCUSS] NLPCraft Proposal

2020-02-05 Thread Dave Fisher
Hi - A little research on Google, Quadra and LinkedIn shows that DataLingvo and NLPCraft seem to be the same with a name change. Regards, Dave > On Feb 5, 2020, at 5:24 PM, David Jencks wrote: > > Is there perhaps a language problem? I often have trouble saying what I mean > in a way that

Re: [DISCUSS] NLPCraft Proposal

2020-02-05 Thread David Jencks
Is there perhaps a language problem? I often have trouble saying what I mean in a way that can be understood… even by me, a few minutes later. https://www.datalingvo.com now seems to redirect to https://nlpcraft.org, perhaps the company changed it’s name but it’s the same organization? I

Re: [DISCUSS] NLPCraft Proposal

2020-02-05 Thread Justin Mclean
HI, > The original code for NLPCraft was developed under DataLingvo. So wouldn’t they be the copyright owner? If soyou can’t change headers or remove copyright statements without permission from them, do you have that? Can you point me to the original repos? It may be that that are other

Re: [DISCUSS] NLPCraft Proposal

2020-02-05 Thread Nikita Ivanov
Justin - let me clarify (sorry for confusion). The original code for NLPCraft was developed under DataLingvo. A few years back it was decided to rename the project to NLPCraft and adopt CC w/ASL2.0 license. The codebase was migrated to a new GitHub repo along with these changes. Apparently, not

Re: [DISCUSS] NLPCraft Proposal

2020-02-05 Thread Justin Mclean
Hi, Thanks for the answers. > 3. There are historical mentions of DataLingvo in the source code (here and > there) and that needs to be cleaned up (they are just an artefact of > migration from repo to repo). I'm not sure that answers my question(s), historical how? Thanks, Justin

Re: [DISCUSS] NLPCraft Proposal

2020-02-05 Thread Nikita Ivanov
Justin, Let me reply on these. 1. The common clause will be removed (if and when the project enters ASF Incubator). I mentioned that in my last reply. 2. nlpcraft.* domains will be donated to ASF during the incubation period. 3. There are historical mentions of DataLingvo in the source code (here

Re: [DISCUSS] NLPCraft Proposal

2020-02-04 Thread Justin Mclean
Hi, Great proposal and an interesting project you have there: Some comments: - The common clause is a big concern, it basically means this is not open source software. The project needs to be willing to remove it and have permission to do so from all contributors. - Is nlpcraft a company

Re: [DISCUSS] NLPCraft Proposal

2020-02-04 Thread Furkan KAMACI
Hi, I've checked your proposal, website, and blog posts and seems promising! I can help as a mentor if needed too. Kind Regards, Furkan KAMACI On Tue, Feb 4, 2020 at 1:21 PM Paul King wrote: > All sounds good to me. > > On Tue, Feb 4, 2020 at 4:30 PM Nikita Ivanov wrote: > > > Hi Paul, > >

Re: [DISCUSS] NLPCraft Proposal

2020-02-04 Thread Paul King
All sounds good to me. On Tue, Feb 4, 2020 at 4:30 PM Nikita Ivanov wrote: > Hi Paul, > I'm one of the NLPCraft project members, let me chime in here. > > 1. The project is very interested in native Groovy/Kotlin/Scala model > APIs. It is a bit unclear for now how much work needs to be done >

Re: [DISCUSS] NLPCraft Proposal

2020-02-03 Thread Nikita Ivanov
Hi Paul, I'm one of the NLPCraft project members, let me chime in here. 1. The project is very interested in native Groovy/Kotlin/Scala model APIs. It is a bit unclear for now how much work needs to be done specifically for these languages given that NLPCraft provides a very plain (and

Re: [DISCUSS] NLPCraft Proposal

2020-02-03 Thread Konstantin Boudnik
Paul, I think five is the charm! Groovy has been my favorite language for near a decade so I would love you to join the group of mentors. And I think I am expressing the unspoken consensus of the rest of us :) So, welcome! As for the use of Commons Clause: thanks for the good catch. Let's look

Re: [DISCUSS] NLPCraft Proposal

2020-02-03 Thread Paul King
Looks like you have close to a full house for mentors. I could certainly put my hat in the ring if you need another, otherwise I will certainly be an interested community member. It seems like an interesting project. I would have a particular interest in Groovy/Micronaut integration. I did notice

Re: [DISCUSS] NLPCraft Proposal

2020-02-03 Thread Konstantin Boudnik
Dave, appreciate the offer - having someone of your caliber on the team is a huge help. I will update the proposal shortly! Welcome and thank you! -- Cos On Mon, Feb 03, 2020 at 04:59PM, Dave Fisher wrote: > This is very interesting. You’ve got a good set of mentors! > > If you are looking

Re: [DISCUSS] NLPCraft Proposal

2020-02-03 Thread Dave Fisher
This is very interesting. You’ve got a good set of mentors! If you are looking for a fourth mentor then I volunteer if you are interested. Regards, Dave > On Feb 3, 2020, at 4:43 PM, Konstantin Boudnik wrote: > > Good time of the time to all! > > I'd like to bring this new interesting

[DISCUSS] NLPCraft Proposal

2020-02-03 Thread Konstantin Boudnik
Good time of the time to all! I'd like to bring this new interesting project for the discussion, comments and feedback with the aim of starting a formal [VOTE] of its acceptance into Incubator. People behind this project aren't new to Apache: some of them were behind the Apache Ignite