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: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Fwd: svn commit: r1873757 - /incubator/public/trunk/content/ip-clearance/index.xml

2020-02-07 Thread Dave Fisher
> +Weex UI

You need to fix this.

Thanks,
Dave

> Begin forwarded message:
> 
> From: pa...@apache.org
> Subject: svn commit: r1873757 - 
> /incubator/public/trunk/content/ip-clearance/index.xml
> Date: February 7, 2020 at 5:28:20 PM EST
> To: c...@incubator.apache.org
> Reply-To: general@incubator.apache.org
> 
> Author: pauls
> Date: Fri Feb  7 22:28:20 2020
> New Revision: 1873757
> 
> URL: http://svn.apache.org/viewvc?rev=1873757=rev
> Log:
> Add the Apache Felix Atomos contribution ip-clearance form.
> 
> Modified:
>incubator/public/trunk/content/ip-clearance/index.xml
> 
> Modified: incubator/public/trunk/content/ip-clearance/index.xml
> URL: 
> http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/index.xml?rev=1873757=1873756=1873757=diff
> ==
> --- incubator/public/trunk/content/ip-clearance/index.xml [utf-8] (original)
> +++ incubator/public/trunk/content/ip-clearance/index.xml [utf-8] Fri Feb  7 
> 22:28:20 2020
> @@ -48,6 +48,13 @@
> 
> 
>   
> +Weex UI
> +  
> +Apache Felix
> +2020-02-07
> +
> +
> +  
> Weex UI
>   
> Apache Weex (Incubating)
> 
> 
> 
> -
> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> For additional commands, e-mail: cvs-h...@incubator.apache.org
> 



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 from DataLingvo are all a part of
>  NLPCraft project there is no need for explicit copyright transfer
>  permission from them (or at least this is how I understand the
>  situation)
> 
> Anything else I haven't covered (sorry, the thread was a bit of asynchronous 
> and I might have missed some points).

Pretty much.

I’m curious is the address on Howard St in San Francisco a shared office 
location?

Regards,
Dave

> 
> Thanks,
>  Cos
> 
>> On 2/5/20 6:44 PM, Justin Mclean wrote:
>> 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 an ASF project 
>> yet please see [1] for future expectations. ASF policy is generally to not 
>> remove 3rd party headers.
>>> Just to be clear - NLPCraft has no
>>> affiliation with DataLingvo of any kind (beyond the original roots) nor it
>>> is a legal entity; it's just a project name.
>> You mentioned all the original developers from DataLingvo worked on 
>> NLPCraft. Is this still the case? Are any of them initial committers? Will 
>> all people who worked on the original DataLingvo code base be signing ICLAs?
>>> If required, DataLingvo will execute SGA (as it already open-sourced it
>>> with ASL 2.0 license two years ago). Please advise.
>> I think that would be best.
>> Thanks,
>> Justin
>> 1. https://www.apache.org/legal/src-headers.html#3party
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



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 transfer
  permission from them (or at least this is how I understand the
  situation)

Anything else I haven't covered (sorry, the thread was a bit of 
asynchronous and I might have missed some points).


Thanks,
  Cos

On 2/5/20 6:44 PM, Justin Mclean wrote:

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 an ASF project yet 
please see [1] for future expectations. ASF policy is generally to not remove 
3rd party headers.


Just to be clear - NLPCraft has no
affiliation with DataLingvo of any kind (beyond the original roots) nor it
is a legal entity; it's just a project name.


You mentioned all the original developers from DataLingvo worked on NLPCraft. 
Is this still the case? Are any of them initial committers? Will all people who 
worked on the original DataLingvo code base be signing ICLAs?


If required, DataLingvo will execute SGA (as it already open-sourced it
with ASL 2.0 license two years ago). Please advise.


I think that would be best.

Thanks,
Justin

1. https://www.apache.org/legal/src-headers.html#3party
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Looking for Champion and Mentors

2020-02-07 Thread Eya Badal Abdisho



On 2020/01/31 13:52:17, "John D. Ament"  wrote: 
> On Fri, Jan 31, 2020 at 12:48 AM Eya Badal Abdisho 
> wrote:
> 
> >
> >
> > On 2020/01/29 23:45:40, Justin Mclean  wrote:
> > > Hi,
> > >
> > > > Meanwhile please let me know if there is any other information that I
> > can provide you with.
> > >
> > > The Incubator prefers projects that already have a community around
> > them.  A little more information about that community around your project
> > would help, so far it seems (but I could be mistaken) it’s more of an
> > internal company project that wants to become an open source one and grow a
> > community around it.
> > >
> > > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >Thank you, Justin, for your feedback.
> >
> > >AgensGraph Extension project started as an internal project due to our
> > community requests and needs in regard to having an extension instead of
> > the fork edition of PostgreSQL. From the beginning, the plan was to make
> > the extension an open-source project after a beta version was released. We
> > hope that the old existing users will join this community as committers as
> > well since the initial goal of this project was based on the user's desire
> > to eliminate the need to perform data migrations or replication. (The ease
> > of adoption for the extension is incomparable to that of for edition that
> > will create an even bigger community than the current edition.)
> >
> > For your reference please find the requests and comments in links below
> > from our community where they asked for an extension version of AgensGraph:
> >
> > https://github.com/bitnine-oss/agensgraph/issues/268
> >
> >
> I think another way to look at what Justin's saying is that we don't want
> to bring on a project that only has one developer on it.  It's very hard
> for that project to grow.  It's pretty common for corporate sponsored
> projects to move to Apache; the project can grow outside of any one
> corporate structure.
> 
> 
> >
> > >We are actively engaged in the PostgreSQL community by co-sponsoring
> > PostgreSQL events. Through this project, we expect that lots of people from
> > that community will join and participate as developers and users.
> >
> >
> > Please let me know if you need any additional information and we will be
> > more than happy to provide that.
> >
> > Best regards,
> > Eya
> >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> Dear everyone, 

I just want to mention that the AgensGraph Extension project repository is 
public now for your consideration: https://github.com/bitnine-oss/agensgraph-ext
 
It is also updated on our proposal: 
https://cwiki.apache.org/confluence/display/INCUBATOR/AgensGraphExtension

Please let me know if you have any questions. 

Best, 
Eya 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [RESULT] [IP CLEARANCE] Maven Wrapper

2020-02-07 Thread Robert Scholte
After sharing the information with the Maven PMC, we want to do the following:

- accept Maven wrapper. 
- don't wait for Walmart to hand over a SGA for the wrapper-plugin. Instead we 
will start to write our own maven-wrapper-plugin. This is actually a very small 
plugin, won't require a lot of effort to get it running.

thanks,
Robert
On 4-2-2020 19:28:03, Robert Scholte  wrote:
Thanks John, I'll share this with the PMC and we'll let you now what we'll 
decide.

Robert
On 4-2-2020 17:07:31, John D. Ament  wrote:
To be very explicit here:

- The code for the maven wrapper is fine, it's already apache licensed and
has no NOTICE file declared with it, so would be perfectly fine to import.
ICLA's would be nice, but not required, and adding a NOTICE indicating the
origination of parts of it would also be nice but not required.
- The code for the Takari Maven Plugin is EPLv1 and requires an SGA to
change the license to apache license.

I'd recommend the Maven PMC take this back and decide if importing just the
wrapper is enough.

John

On Mon, Feb 3, 2020 at 5:20 PM Brian Fox wrote:

> I do not have answers to those questions, which seems like good ones.
> I just wanted to break the loop, which I think I might have ;-)
>
> On Mon, Feb 3, 2020 at 5:13 PM David Nalley wrote:
> >
> > My sense from reading this thread is that it was a 'work-for-hire' and
> > that the contributors are not owners. Otherwise, why have they been
> > bothering to talk to Walmart Labs? Why is a company (as opposed to
> > project or indivudal(s)) listed as the copyright holder in source
> > code?
> >
> > The copyright headers identify Takari Inc as the copyright
> > holder/owner, which from this thread seems to have been acquired by
> > Walmart Labs?
> >
> > --David
> >
> > On Mon, Feb 3, 2020 at 11:01 PM Brian Fox wrote:
> > >
> > > I think what Robert is highlighting was that collectively, the
> > > contributors are still owners and have granted permission to use
> > > another license.
> > >
> > > On Mon, Feb 3, 2020 at 4:59 PM David Nalley wrote:
> > > >
> > > > On Mon, Feb 3, 2020 at 9:27 PM Justin Mclean <>
> jus...@classsoftware.com> wrote:
> > > > >
> > > > > HI,
> > > > >
> > > > > I agree with what John wrote, part of the code is EPL which is not
> compatible with the ALv2, you need the owner permission to change the
> license on that..
> > > > >
> > > > > My understanding of "Let me try to get in contact with Walmart
> Labs to get an SGA for the Takari Maven Wrapper.” was that the next step
> would be an SGA.
> > > > >
> > > >
> > > > I agree with Justin.
> > > >
> > > > The lack of an SGA makes this ineligible for the normal lazy
> consensus route.
> > > > The fact that 1 of the chunks of code you're looking at is licensed
> > > > under the EPL is a further blocker. You can't relicense it without
> > > > explicit permission from the owner, preferably memorialized as a SGA.
> > > >
> > > > While I don't think that the IP Clearance process is perfectly rigid,
> > > > it is a process and this one is missing some significant parts of
> that
> > > > process.
> > > >
> > > > --David
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [RESULT] [IP CLEARANCE] Maven Wrapper

2020-02-07 Thread Christofer Dutz
Hi all,

how about just adding the maven-wrapper itself ... the maven plugin isn't even 
needed.
I have been using the maven-wrapper in almost every project, however the plugin 
I have never.

It's just a little tool to add the cmd, sh files as well as some properties. 
I think we could even just whip up a small archive containing this information 
and make that available.

And if we want to I think I'd whip up a maven plugin that automates this in 
just an hour or so.

So I would suggest to add the maven wrapper and just skip the maven plugin.


Chris



Am 04.02.20, 17:07 schrieb "John D. Ament" :

To be very explicit here:

- The code for the maven wrapper is fine, it's already apache licensed and
has no NOTICE file declared with it, so would be perfectly fine to import.
ICLA's would be nice, but not required, and adding a NOTICE indicating the
origination of parts of it would also be nice but not required.
- The code for the Takari Maven Plugin is EPLv1 and requires an SGA to
change the license to apache license.

I'd recommend the Maven PMC take this back and decide if importing just the
wrapper is enough.

John

On Mon, Feb 3, 2020 at 5:20 PM Brian Fox  wrote:

> I do not have answers to those questions, which seems like good ones.
> I just wanted to break the loop, which I think I might have ;-)
>
> On Mon, Feb 3, 2020 at 5:13 PM David Nalley  wrote:
> >
> > My sense from reading this thread is that it was a 'work-for-hire' and
> > that the contributors are not owners. Otherwise, why have they been
> > bothering to talk to Walmart Labs? Why is a company  (as opposed to
> > project or indivudal(s)) listed as the copyright holder in source
> > code?
> >
> > The copyright headers identify Takari Inc as the copyright
> > holder/owner, which from this thread seems to have been acquired by
> > Walmart Labs?
> >
> > --David
> >
> > On Mon, Feb 3, 2020 at 11:01 PM Brian Fox  wrote:
> > >
> > > I think what Robert is highlighting was that collectively, the
> > > contributors are still owners and have granted permission to use
> > > another license.
> > >
> > > On Mon, Feb 3, 2020 at 4:59 PM David Nalley  wrote:
> > > >
> > > > On Mon, Feb 3, 2020 at 9:27 PM Justin Mclean <
> jus...@classsoftware.com> wrote:
> > > > >
> > > > > HI,
> > > > >
> > > > > I agree with what John wrote, part of the code is EPL which is not
> compatible with the ALv2, you need the owner permission to change the
> license on that..
> > > > >
> > > > > My understanding of "Let me try to get in contact with Walmart
> Labs to get an SGA for the Takari Maven Wrapper.” was that the next step
> would be an SGA.
> > > > >
> > > >
> > > > I agree with Justin.
> > > >
> > > > The lack of an SGA makes this ineligible for the normal lazy
> consensus route.
> > > > The fact that 1 of the chunks of code you're looking at is licensed
> > > > under the EPL is a further blocker. You can't relicense it without
> > > > explicit permission from the owner, preferably memorialized as a 
SGA.
> > > >
> > > > While I don't think that the IP Clearance process is perfectly 
rigid,
> > > > it is a process and this one is missing some significant parts of
> that
> > > > process.
> > > >
> > > > --David
> > > >
> > > > 
-
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org