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 promisi
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 know
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 a
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 fr
Hi,
Report are due to be signed off by the Tue February 11th.
Its good to see some projects already having sign offs including
DolphinScheduler where 4 mentors have signed and ECharts where 3 mentors have
signed off the report.
Other than non reporting podling, currently missing sign-offs are:
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 explana
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 ca
Hi,
We still missing reports from:
- Annotator
- PageSpeed
- SDAP
- Taverna
Both Annotator and Taverna have failed to report twice in a row which is
concerning.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@i
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 could
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 people
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 al
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
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
13 matches
Mail list logo
