Has anyone used git's sub-modules before? My understanding is you just point to an external repository. So *technically* I do not think the code would be hosted in the main repo. Even if that was allowed, I have concerns about how inactive the repo is. Could we fork this, make our changes, and submit it to another apache project that it may make sense under? Is that even allowed under their license?
On Fri, Jan 13, 2017 at 5:35 PM, Matt Foley <ma...@apache.org> wrote: > Perhaps it would be more appropriate to put it under > https://dist.apache.org/repos/dist/release/incubator/metron/ , perhaps as > https://dist.apache.org/repos/dist/release/incubator/metron/mvn-repo ? > > We should not host anything with a license that isn’t compatible with > inclusion in an Apache project. If we post only non-source artifacts, then > that would include packages with “Category B List” licenses (that is, > ‘"WEAK COPYLEFT" LICENSES’) as well as “Category A List” licenses (those > “SIMILAR IN TERMS TO THE APACHE LICENSE 2.0”) -- per > https://www.apache.org/legal/resolved . For versioning, we could simply > structure as a maven repo, and in fact that’s what I think we should do. > > Hosting the source code is not, I think, something we are supposed to do > for non-Apache projects: https://www.apache.org/legal/resolved again, > this time the very first question: > > CAN ASF PMCS HOST PROJECTS THAT ARE NOT UNDER THE APACHE LICENSE? > No. See the Apache Software Foundation licenses page for more details, > and the Apache Software Foundation page for additional background. > > > On 1/13/17, 8:11 AM, "Billie Rinaldi" <bil...@apache.org> wrote: > > No, we can't host artifacts in a git repo, or on a website. It would be > like distributing a release that hasn't been voted upon. > > Regarding message threading, in Gmail adding a [tag] to the subject > does > not create a new thread. So the change is not visible in my mailbox > unless > the rest of the subject is changed as well. > > On Mon, Jan 9, 2017 at 1:00 PM, Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > > > This is a question primarily for the mentors. > > > > *Background* > > metron-common is currently depending on the openSOC github repo for > hosting > > kraken artifacts. The original reason for this was that these jars > are not > > hosted in Maven Central, and they were not reliably available in the > Kraken > > repo. https://issues.apache.org/jira/browse/METRON-650 is tracking > work > > around copying these artifacts to the Metron repo. > > > > Kraken source on openSOC - https://github.com/OpenSOC/kraken > > Krake maven repo on openSOC - > > https://github.com/OpenSOC/kraken/tree/mvn-repo > > > > *Ask* > > Create a new branch in incubator-metron to host any necessary maven > > artifacts. This branch would simply be incubator-metron/mvn-repo. > This is > > similar to how we've hosted the asf-site. > > > > *Concerns/Questions* > > > > 1. Can we host these jars/artifacts in this manner? > > 2. Concerns regarding licensing? > > 3. Do we need to also grab and host the source code? > > > > > > >
