metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "P. Taylor Goetz" <>
Subject Re: [MENTORS] Licensing
Date Mon, 10 Apr 2017 20:19:46 GMT
In my opinion, I think you are probably okay including it. You would want to retain any license
headers, and also make sure your NOTICE file is updated to include the copyright information.

I’m not by any means an expert in these matters, so I would recommend getting a second opinion
by leveraging the collective intelligence of the general@incubator (while you are a podling
or even afterward) or legal-discuss@. The latter list is often home to some important legal
discussions, and I would recommend PMC members read and/or subscribe to that list.


> On Apr 5, 2017, at 4:50 PM, <> wrote:
> *Background*
> We have a situation where a portion of code
> <>
> was created for Metron, which is a plugin for a separate open source
> project, bro.  The code was separately pushed out by the initial author to
> the bro community under the 3-Clause BSD license
> <>, and
> some important
> enhancements
> <>
> have been made to it in that separate community, which we would like to
> include, in addition to 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 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?
> Anyone, feel free to correct my historical understanding here - I wasn't
> closely involved with the project at the time this all occurred.  Thanks,
> Jon
> -- 
> Jon

View raw message