On 2020-10-31 12:03:50 +0100 (+0100), Thomas Goirand wrote: [...] > On 10/31/20 3:07 AM, Jeremy Stanley wrote: > > I have to agree, though in the upstream projects with which I'm > > involved, those generated files are basically a lossy re-encoding of > > metadata from the Git repositories themselves: AUTHORS file > > generated from committer headers, ChangeLog files from commit > > subjects, version information from tag names, and so on. Some of > > this information may be referenced from copyright licenses, so it's > > important in those cases for package maintainers to generate it when > > making their source packages if not using the sdist tarballs > > published by the project. > > Unfortunately, the FTP masters do not agree with you. I've been told > that the OpenStack changelog is a way too big, and it's preferable to > not have it in the binary packages. PBR started creating much smaller changelogs years ago, after you asked ftpmaster. I get that you see no value in changelog files, but it seems like it would be worth revisiting. > Also, there's nothing in the Apache license that mandates having > an AUTHORS list as per what PBR builds. If we are to care that > much in OpenStack, then the license must be changed. [...] I agree, it's not commonplace in OpenStack other than this possible exception: https://opendev.org/openstack/python-openstackclient/src/branch/master/doc/source/cli/man/openstack.rst#user-content-copyright You do tend to find it in other Python projects however, for example: https://github.com/pygments/pygments/blob/master/LICENSE#L1 My point was that, in general, some Python projects do autogenerate an AUTHORS file from commit metadata at dist time rather than storing it directly in a file within their Git repositories, and some projects (including Python projects) refer to AUTHORS from copyright statements, so it's a good idea to build/keep it. -- Jeremy Stanley
Attachment:
signature.asc
Description: PGP signature