Oh awesome, thanks Nick. I guess it just took another day (or at least several additional hours) for it to be created.
Jon On Tue, Apr 11, 2017, 3:51 PM Nick Allen <n...@nickallen.org> wrote: > I think that was done with the original request. > > https://github.com/apache/incubator-metron-bro-plugin-kafka > > > > > On Mon, Apr 10, 2017 at 8:59 PM, zeo...@gmail.com <zeo...@gmail.com> > wrote: > > > Okay great, thanks you. I've sent an email out to general@ to discuss. > > > > It looks like things are all set up on asf > > <https://git-wip-us.apache.org/repos/asf?p=incubator- > > metron-bro-plugin-kafka.git> > > for > > that new repo - would somebody be willing to setup a read-only git mirror > > to github <https://www.apache.org/dev/git.html#git-mirrors>? My > > understanding is that I'm unable to make this request myself, as I am > not a > > PMC member. The documentation that I've been able to find says: > > > > Please file an INFRA <https://issues.apache.org/jira/browse/INFRA> issue > > (component: Git) to request a new codebase to be mirrored or to change > the > > settings of an existing mirror. When requesting a new mirror, please > > include the following information: > > > > - > > > > Name of the codebase, for example "Apache Tika" > > - > > > > Name of the requested Git mirror, for example "tika.git" > > - > > > > Subversion path of the codebase, for example "/lucene/tika" > > - > > > > Subversion layout, in case it is different from the standard "trunk, > > branches, tags" structure. > > > > > > If this is something that I should be able to do I would be more than > happy > > to, just let me know. Thanks! > > > > Jon > > > > On Mon, Apr 10, 2017 at 4:19 PM P. Taylor Goetz <ptgo...@gmail.com> > wrote: > > > > > 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. > > > > > > -Taylor > > > > > > > On Apr 5, 2017, at 4:50 PM, zeo...@gmail.com <zeo...@gmail.com> > wrote: > > > > > > > > *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 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 > > > > <https://github.com/bro/bro-plugins/blob/master/kafka/COPYING>, and > > > > some important > > > > enhancements > > > > < > > > > https://github.com/bro/bro-plugins/commit/b9f1f35415cb0db065348da0a5043a > > 8353b4a0a8 > > > > > > > > have been made to it in that separate community, which we would like > to > > > > include, in addition to 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/c92acd125dae05f0537d4505e0254d > > fa6382ca9f40edba7d2f4c6224@%3Cdev.metron.apache.org%3E > > > > > > > > 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 > > > > < > > > https://lists.apache.org/thread.html/7468692c96ed0cb012ac9014229694 > > ba8edf3a3b3b55d346eec57019@%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? > > > > > > > > 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 > > > > > > -- > > > > Jon > > > -- Jon
