Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0EFE0200C53 for ; Tue, 11 Apr 2017 17:58:34 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0DB39160B9B; Tue, 11 Apr 2017 15:58:34 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 56032160B89 for ; Tue, 11 Apr 2017 17:58:33 +0200 (CEST) Received: (qmail 57894 invoked by uid 500); 11 Apr 2017 15:58:32 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 57883 invoked by uid 99); 11 Apr 2017 15:58:32 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Apr 2017 15:58:32 +0000 Received: from hw10447.local (unknown [167.102.188.146]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id DEAAE1A002E for ; Tue, 11 Apr 2017 15:58:29 +0000 (UTC) Message-ID: <58ECFD22.2070702@apache.org> Date: Tue, 11 Apr 2017 11:58:26 -0400 From: Josh Elser User-Agent: Postbox 3.0.11 (Macintosh/20140602) MIME-Version: 1.0 To: general@incubator.apache.org Subject: Re: Apache Metron - licensing question References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit archived-at: Tue, 11 Apr 2017 15:58:34 -0000 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 from the community on a previous message. They should be more than capable to answer your questions in the future. I'd suggest you re-ping them if your questions go unanswered in the future. Zeolla@GMail.com wrote: > 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 was moved. > > 1: > https://github.com/apache/incubator-metron/commit/bc140a571a78c428e9ae5a3315c427724183782f > > Much appreciated, > > Jon > > On Mon, Apr 10, 2017, 11:33 PM Joe Witt wrote: > >> Jon, >> >> It appears that the code at [1] was initially committed on Mar 8, >> 2016. The code in Apache Metron [2] was committed on April 13, 2016. >> >> The code in Metron [2] appears heavily derived from the code in the >> initial repository [1]. >> >> In the Metron repository that code has an ASL v2 license and the >> Apache license headers. That, to me, is where the error occurred. >> >> When the code was copied over, even if it was the original author >> doing it, the original license from [1] should be retained/honored and >> this is very easy to do. You would simply ensure your source release >> LICENSE indicates the use of the BSD source. You would still be free >> to alter that source code you've pulled into the Metron codebase and >> build around it as you need. Obviously there are maintenance >> challenges and tradeoffs to consider but the licensing part can be >> pretty clear straightforward other than the question of "how much do I >> have to change the original before it would be appropriate to slap the >> apache license header on a given source file"? >> >> Anyway, I'm not an expert and my advice/interpretation could be wildly >> inaccurate but this looks like it might have an easy solution so >> hopefully that helps. >> >> [1] https://github.com/bro/bro-plugins/tree/master/kafka >> [2] >> https://github.com/apache/incubator-metron/tree/master/metron-sensors/bro-plugin-kafka >> >> Thanks >> Joe >> >> On Mon, Apr 10, 2017 at 8:46 PM, Zeolla@GMail.com >> wrote: >>> Hi all, >>> >>> >>> I recently asked a licensing question to our dev mailing list. I did get >>> feedback >>> < >> https://lists.apache.org/thread.html/a4e2e7bb7fb7497033696645b011c5604790f23f3802aaab32f1bd01@%3Cdev.metron.apache.org%3E >>> from one of our mentors, but he also requested that we get a double >> check. >>> Please see below for a bit of background and my questions. Thanks! >>> >>> >>> *Background* >>> >>> We have a situation where a portion of code >>> < >> https://github.com/apache/incubator-metron/tree/master/metron-sensors/bro-plugin-kafka >>> was created for Apache Metron (incubating), which is a plugin for a >>> separate open source project, bro. The code was >>> later pushed out by the initial author to the bro community under the >>> 3-Clause BSD license >>> , and >>> some important >>> enhancements >>> < >> https://github.com/bro/bro-plugins/commit/b9f1f35415cb0db065348da0a5043a8353b4a0a8 >>> have been made to the plugin in that separate community, which we would >>> like to include in our code, while merging with some recent changes >>> < >> https://github.com/apache/incubator-metron/commit/a2452a25caffdd8c35fd9efe0ed49ce0dd2e3781 >>> that have been made in the Metron code base as well (i.e. we are not >> simply >>> pulling the code down from the external project). This was discussed >>> recently >>> < >> https://lists.apache.org/thread.html/c92acd125dae05f0537d4505e0254dfa6382ca9f40edba7d2f4c6224@%3Cdev.metron.apache.org%3E >>> on the Metron dev mailing list, and we wanted to get some clarification >>> before moving forward. >>> >>> >>> *Questions* >>> >>> 1. Is it valid to assume that, as Casey mentioned >>> < >> https://lists.apache.org/thread.html/7468692c96ed0cb012ac9014229694ba8edf3a3b3b55d346eec57019@%3Cdev.metron.apache.org%3E >>> , >>> these are two separate plugins and we can simply make modifications to >> our >>> code base to resolve the current multithreading issue? >>> >>> 2. If we do 1, will this require a line in our LICENSE file as a >> derivative >>> work, or anything else? >>> >>> >>> Thanks, >>> >>> Jon >>> -- >>> >>> Jon >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org >> For additional commands, e-mail: general-help@incubator.apache.org >> >> -- > > Jon > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org