[License-review] Submission of the European Space Agency Public Licenses (ESA-PL) for approval

Tzeng, Nigel H. Nigel.Tzeng at jhuapl.edu
Tue Jan 10 18:38:31 UTC 2017

While we generate such a file to meet the NOSA 1.3 Section 1.C
requirements using:

git log  --all --pretty=format:"%ad %d %s (%aN)"

it would be more helpful if one could simply provide the git repo of all
the source changes and allow the user to peruse the change history in any
manner they wish.

Even with the log it doesn¹t identify which lines we changed in what
files.  If anyone wishes to determine the provenance of any given
file/line/class the log file by itself wouldn¹t let them do soŠthey¹d
still want a copy of the repo.  Or an annoying diff file.

I understand the desire and need to document these changes.  I would
prefer a less prescriptive manner in fulfilling these requirements.

I assume that when we deliver flight or instrument software that we don¹t
have to include the changelog file with the copy of the software aboard
the spacecraft itself. :)

On 1/10/17, 10:44 AM, "License-review on behalf of Carsten Gerlach"
<license-review-bounces at opensource.org on behalf of cgerlach at tcilaw.de>

>On 21.12.2016 22:32, Tzeng, Nigel H. wrote:
>> I wonder if 4.3 is met with simply providing a git repo of the
>> modified source.
>No, unless the git repo includes a changelog file.
>License-review mailing list
>License-review at opensource.org

More information about the License-review mailing list