On Mon, Sep 19, 2016 at 8:51 AM, Mark Struberg <strub...@yahoo.de.invalid> wrote: > I tend to agree with Alex' interpretation.
Makes two of us. > But we don't yet know what is part of the hg repo and what is part of the > Oracle contribution. > > What would happen if someone e.g. did commit some GPL licensed jar to the > repo a few years ago? > It's easy to catch such things if they are still in the latest version. > But what if they got added and later removed? Do we need to filter them out? No we don't. What ASF stands behind is a release (which is a source tarball and optional binary convenience artifacts) that we distribute via our own infrastructure. While we try to keep our repos clean, we are not forced to have them at the same level of IP hygene that we need for our official releases. Case in point: Apache Geode (incubating). We entered incubation (and ingested the source) with a known LGPL dependency embedded in our tree. Getting rid of if via refactoring was a pre-requisite for our first release, but you can still find history in our Git repo of it being there before the first release was done. Thanks, Roman. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
