I think Max's quote from pjfanning clarifies the distinction. My understanding is that the top-level LICENSE/NOTICE should cover the contents of the *source release*, not the binary dependencies that will later be included in the Docker images.
So it is not simply the LICENSE/NOTICE of the CLI, but neither is it the aggregation of the LICENSE files we put next to each Dockerfile, since those are meant to cover the contents of the corresponding Docker images. This also seems consistent with PJ's issue #246: third-party *source code actually included in the source release* must be accounted for in the top-level LICENSE (and retain the appropriate headers, e.g. the missing license headers in the Scala files derived from OpenWhisk, compared to the original upstream files), while binary dependencies included in the Docker images are accounted for by the image-specific LICENSE/NOTICE files. Antonino Il giorno dom 13 set 2026 alle ore 18:22 Massimo Tozzi < [email protected]> ha scritto: > Hi Michele > My 2cent as you know i am not aware about code: > But PJ has wrote > > The LICENSE for the source release is about the code and should make no > mention of binary dependencies. > The LICENSE for docker images should contain inside the docker image a > specific LICENSE that does mentions the binary dependencies included in the > docker image. > There are different LICENSE files - one for the source release (which > contains just code) and separate ones from the convenience binaries that > you release like docker images. > > could help you? > br/max > > Il giorno dom 13 set 2026 alle ore 18:09 Michele Sciabarra < > [email protected]> ha scritto: > >> I am seriously confused here of this source vs image licensing issue >> >> OpenServerless is a kubernetes application, so, except the cli, >> everything is the source builds a docker image >> >> So we place the LICENSE and NOTICE for the Dockerfile >> >> See admin-api/LICENSE and admin-api/NOTICE for the admn-api/Dockerfile >> and also those in the runtimes under >> runtimes/runttime/python/sys/LICENSE and NOTICE for that Docerfile >> >> But WHAT we have to put in the top level? My guess was: the >> aggregation of the licenses of the submodules... >> >> If not, what? Only the license and notice for the cli? >> >> Please help me to understand... >> >> >> Michele Sciabarra | CTO >> m: +44 747 984 8388 >> e: [email protected] >> l: https://linkedin.com/in/msciab >> Nuvolaris Inc | 1209 Orange Street >> <https://www.google.com/maps/search/1209+Orange+Street?entry=gmail&source=g>, >> 19801Wilmington DE - US >> > > > -- > Massimo Tozzi > CRO @Nuvolaris > > mail: [email protected] > mobile: +39 348 262 7433 <+39%20348%20262%207433> > www: https://www.nuvolaris.io >
