Nick, TBH, I don’t get it. If we ship the “Dockerfile” we are simply shipping text file, code. Under a license. If we create a “docker image” and then publish it to the ASF hub then I agree with you.
My suggestion and my interpretation of Tim’s is to ship a standard “Dockerfile”. Do you agree with this? It should be air covered (as former VP, Legal, at least it would have been with me). Cheers, Chris From: Nick Burch <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, November 20, 2019 at 3:57 PM To: "Allison, Timothy B (US 1760-Affiliate)" <[email protected]> Cc: "<[email protected]>" <[email protected]> Subject: [EXTERNAL] Re: Docker image along with 1.23? On Wed, 20 Nov 2019, Tim Allison wrote: Eric Pugh recently asked on another channel if we had any plans to release an official docker image for 1.23. Depending on what we put in the container, we do need to be a little careful. There's "platform dependencies" under non-compatible licenses that we can optionally use if people have installed them, which we ourselves can't directly ship under ASF rules. (Tesseract is fine as that's Apache Licenses, Java itself is trickier, see the Netbeans discussions on legal-discuss@ and LEGAL jira) Shipping an official docker container with the Tika Server on seems to me to be a helpful step for users, but we just need to make sure we're following ASF policies. (The Apache Software Foundation mission is to "provide software for the public good", but source code is the main focus for the mission, binaries are trickier!) Nick
