There is an MIT-licensed project, FooSoftware, which I have done some work to make work in a Docker container . I would like to publish that work so that others can use FooSoftware in Docker without doing the work to adapt it themselves.
This would involve publishing a project including a
Dockerfile and some simple associated scripts, for example through GitHub. It may also involve making the built image available, for example via Docker Hub. The Docker project does not itself provide the source code to FooSoftware, though it fetches it from the upstream repository when building, ie when a command such as
docker build is issued.
However, I am slightly unclear as to what precisely to include in the
LICENSE file. The original project lists contributors, eg:
(C)opyright 2018-2019 Joe Bloggs <jbloggs at example dot org> (C)opyright 2015-2016 Tracey Beaker <tbeaker at example dot org> (C)opyright 2005-2012 A Dent <arthurd at example dot org>
I am unsure whether to include these in the
LICENSE file I create. On the one hand, I want to properly credit the upstream authors and do not want to make it seem as if I am claiming credit for the whole project. On the other hand, I do not want to make upstream responsible for downstream Docker adaptations.
Given that the MIT license includes the clause:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
I believe including the copyright notices is required, even though the Docker project does not directly include the upstream project's code. Should I add my name to the top, and include previous names below?
I would like to clear on this before making a FOSS faux pas!
1: In the real case this is indeed dealing with the MIT license, but if the answers would be applicable to the broader case of all FOSS licenses which permit redistribution of derivative works I can change the question to the more general case