RE: [VOTE] Apache Gearpump (incubating) 0.8.3-RC1

+1, Thanks. Best Regards Gary (Wang, Gang) External Contact: (323)801-6286 (WhatsApp) -Original Message- From: Karol Brejna [mailto:karolbre...@apache.org] Sent: Tuesday, April 11, 2017 2:34 AM To: general@incubator.apache.org Cc: d...@gearpump.incubator.apache.org Subject: [VOTE]

Re: Help with Dependency Licensing

On Wed, Apr 12, 2017 at 9:03 AM, John D. Ament wrote: > > The info I provided was based on a discussion on legal, originally carried > over from a discussion on optional dependencies on software licensed under > the Amazon Software License - >

Re: Help with Dependency Licensing

On Tue, Apr 11, 2017 at 8:29 PM Niclas Hedhman wrote: > On Wed, Apr 12, 2017 at 12:31 AM, Mike Jumper > wrote: > > > > > Even in the case of the GPL, my understanding is that the virality takes > > hold upon linking (at build time), not upon

Re: Help with Dependency Licensing

On Tue, Apr 11, 2017 at 8:40 PM Mike Jumper wrote: > On Apr 11, 2017 17:29, "Niclas Hedhman" wrote: > > On Wed, Apr 12, 2017 at 12:31 AM, Mike Jumper > wrote: > > > > > Even in the case of the GPL, my understanding is that

Re: Help with Dependency Licensing

On Apr 11, 2017 17:29, "Niclas Hedhman" wrote: On Wed, Apr 12, 2017 at 12:31 AM, Mike Jumper wrote: > > Even in the case of the GPL, my understanding is that the virality takes > hold upon linking (at build time), not upon referencing the API via

Re: Help with Dependency Licensing

On Wed, Apr 12, 2017 at 12:31 AM, Mike Jumper wrote: > > Even in the case of the GPL, my understanding is that the virality takes > hold upon linking (at build time), not upon referencing the API via an > import, include, etc. in the source. > Your understanding is,

Re: Publishing npm modules

Thanks, that was very helpful. On Wed, Apr 12, 2017 at 7:03 AM, Marvin Humphrey wrote: > On Tue, Apr 11, 2017 at 7:00 AM, Niclas Hedhman > wrote: > > > does anyone have any information on policy/process for uploading npm > > modules to global

Re: Publishing npm modules

On Tue, Apr 11, 2017 at 7:00 AM, Niclas Hedhman wrote: > does anyone have any information on policy/process for uploading npm > modules to global registry https://registry.npmjs.org/ With regards to publication of packages, npm is just another downstream distribution channel

Re: Help with Dependency Licensing

On Tue, Apr 11, 2017 at 9:16 AM, Niclas Hedhman wrote: > Please note that Cat X licenses are deemed to be incompatible with Apache > License, insofar that they are viral in nature, and FSF has made a claim > that dynamically linked languages, such as Java, forces the virality

Re: Help with Dependency Licensing

On Tue, Apr 11, 2017 at 12:16 PM Niclas Hedhman wrote: > Please note that Cat X licenses are deemed to be incompatible with Apache > License, insofar that they are viral in nature, and FSF has made a claim > that dynamically linked languages, such as Java, forces the virality

Re: Help with Dependency Licensing

Please note that Cat X licenses are deemed to be incompatible with Apache License, insofar that they are viral in nature, and FSF has made a claim that dynamically linked languages, such as Java, forces the virality to the dependent project... Meaning, if you have an import statement linking your

Re: Apache Metron - licensing question

Also, it may be worth mentioning: Metron is on its way out of the Apache Incubator. A vote has recently passed at the Incubator level for their graduation. It is likely that after the next ASF board meeting, Metron will no longer be a podling. I am worried that you did not receive a response

Re: Help with Dependency Licensing

On Tuesday, April 11, 2017 11:10 AM, John D. Ament wrote: Nick, > In general, the LICENSE and NOTICE refers to the contents of the release > itself.  If you're not bundling any of those outside dependencies, then > there would be nothing to include. Okay, sounds

Re: Help with Dependency Licensing

Nick, In general, the LICENSE and NOTICE refers to the contents of the release itself. If you're not bundling any of those outside dependencies, then there would be nothing to include. Please also note - you can provide a binary release, assuming that the binary release does not package the

Re: Publishing npm modules

INFRA-12886 might be relevant, since Nexus 3.x also comes with npm support. On Tue, Apr 11, 2017 at 5:04 PM, John D. Ament wrote: > On Tue, Apr 11, 2017 at 10:00 AM Niclas Hedhman > wrote: > > > Hi, > > > > does anyone have any information on

Re: Publishing npm modules

On Tue, Apr 11, 2017 at 10:00 AM Niclas Hedhman wrote: > Hi, > > does anyone have any information on policy/process for uploading npm > modules to global registry https://registry.npmjs.org/ You may want to check with the Cordova team, see what they've come up. > > > This

Help with Dependency Licensing

Hello, everyone,I'm currently working on the Guacamole incubator project, and am developing an extension for the project that has dependencies on binaries (JARs via Maven) that are licensed under Category-X licenses.  We've already determined that we cannot distribute a binary version of this

Publishing npm modules

Hi, does anyone have any information on policy/process for uploading npm modules to global registry https://registry.npmjs.org/ This is for convenience and should be similar to publishing to Maven Central, but I would like to know if there is anything explicit about it. Cheers -- Niclas

Re: How to deactivate/delete old GitHub mirror for log4cxx?

Leave link to the new location in description, this will be great promo. On 11 Apr 2017 12:42, "Pono Takamori" wrote: We can either delete the old Github mirror or put up a link to the new repo in the description. Feel free to file a ticket on JIRA for whatever you folks

Re: How to deactivate/delete old GitHub mirror for log4cxx?

And to be clear - that's an INFRA JIRA ticket - https://issues.apache.org/jira/browse/INFRA/ (since this went to many mailing lists) John On Tue, Apr 11, 2017 at 6:42 AM Pono Takamori wrote: > We can either delete the old Github mirror or put up a link to the new > repo in the

Re: How to deactivate/delete old GitHub mirror for log4cxx?

We can either delete the old Github mirror or put up a link to the new repo in the description. Feel free to file a ticket on JIRA for whatever you folks decide is best :) Cheers, -Pono on behalf of Infra On Tue, Apr 11, 2017 at 12:46 AM, Thorsten Schöning wrote: > Hi, >

Re: Apache Metron - licensing question

Ok great, thank you for your feedback. I did a bit more searching because that timeline didn't seem right and found that the original bro-kafka-plugin code[1] first appeared in the Metron repo on February 8, 2016. My apologies for not properly linking this in my first email, I hadn't realized it

[VOTE] Apache Gearpump (incubating) 0.8.3-RC1

Hi IPMC Community, The PPMC vote to release Apache Gearpump (incubating) 0.8.3-RC1 has passed. We would like to now submit this release candidate to the IPMC. The PPMC vote thread is here:

How to deactivate/delete old GitHub mirror for log4cxx?

Hi, the logging project log4cxx moved to a new GIT-repo recently, but had a mirror on GitHub already in the past at the following place: https://github.com/apache/log4cxx The new mirror is the following: https://github.com/apache/logging-log4cxx Is there any way to deactivate/delete/whatever

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating

Awesome. I learned a lot from this discussion. We will address these comments and call another vote. - Sijie On Mon, Apr 10, 2017 at 3:11 PM, Marvin Humphrey wrote: > On Mon, Apr 10, 2017 at 2:28 PM, Henry Saputra > wrote: > > The question is