Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
MIME-Version: 1.0
From: Michael Miklavcic <michael.miklavcic@gmail.com>
Date: Thu, 2 Feb 2017 12:22:40 -0700
Message-ID: <CAEVc+k__FuZ1Hk0zsYWfrrXwF_h3Br3R7PyLxPV2wpP2R4aTAg@mail.gmail.com>
Subject: Apache Metron (Incubating) - copying Apache licensed code into codebase
To: legal-discuss@apache.org
Content-Type: multipart/alternative; boundary=94eb2c1903a0b8f3040547911672
archived-at: Thu, 02 Feb 2017 19:22:52 -0000

--94eb2c1903a0b8f3040547911672
Content-Type: text/plain; charset=UTF-8

Hi Apache community,

My name is Michael Miklavcic. I'm a committer on the Apache Metron
(Incubating) project and we have a dependency that we would like to copy
into the Metron codebase. The project in question is an Apache V2 licensed
project that has not been maintained in a couple years, and the artifacts
are not in Maven Central. https://github.com/nchovy/kraken

The motivation for doing so is that we are currently depending on another
third party for hosting the packaged jar files. This may be fine for the
short-term, however we would like stronger guarantees that every build of
our project will be able to access those libraries. In addition, we would
like reliable access to the source code in the event that any bugs or
security issues are found that need fixing.

Per this thread -
http://mail-archives.apache.org/mod_mbox/incubator-metron-dev/201701.mbox/browser
- our mentor, Billie Rinaldi, has stated that an IP clearance process
requires permission from the original authors. I reached out to the Kraken
developers about a month ago and have not received any response. What steps
do we need to take in order to comply with any legal requirements to
copy/fork this project into our codebase?

Thanks,
Michael Miklavcic
Apache Metron (Incubating) committer

--94eb2c1903a0b8f3040547911672
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Apache community,<div><br></div><div>My name is Michael=
 Miklavcic. I&#39;m a committer on the Apache Metron (Incubating) project a=
nd we have a dependency that we would like to copy into the Metron codebase=
. The project in question is an Apache V2 licensed project that has not bee=
n maintained in a couple years, and the artifacts are not in Maven Central.=
 <a href=3D"https://github.com/nchovy/kraken">https://github.com/nchovy/kra=
ken</a></div><div><br></div><div>The motivation for doing so is that we are=
 currently depending on another third party for hosting the packaged jar fi=
les. This may be fine for the short-term, however we would like stronger gu=
arantees that every build of our project will be able to access those libra=
ries. In addition, we would like reliable access to the source code in the =
event that any bugs or security issues are found that need fixing.</div><di=
v><br></div><div>Per this thread -=C2=A0<a href=3D"http://mail-archives.apa=
che.org/mod_mbox/incubator-metron-dev/201701.mbox/browser">http://mail-arch=
ives.apache.org/mod_mbox/incubator-metron-dev/201701.mbox/browser</a> - our=
 mentor, Billie Rinaldi, has stated that an IP clearance process requires p=
ermission from the original authors. I reached out to the Kraken developers=
 about a month ago and have not received any response. What steps do we nee=
d to take in order to comply with any legal requirements to copy/fork this =
project into our codebase?</div><div><br></div><div>Thanks,</div><div>Micha=
el Miklavcic</div><div>Apache Metron (Incubating) committer</div></div>

--94eb2c1903a0b8f3040547911672--