incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Witt <>
Subject Re: Apache Metron - licensing question
Date Tue, 11 Apr 2017 03:33:00 GMT

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.



On Mon, Apr 10, 2017 at 8:46 PM, <> wrote:
> Hi all,
> I recently asked a licensing question to our dev mailing list.  I did get
> feedback
> <>
> 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
> <>
> 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
> <>
> 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
> <>
> 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
> <>
> 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
> <>,
> 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:
For additional commands, e-mail:

View raw message