Thanks lumin, I did a check:
> Licensecheck attempts to determine the license that applies to each file passed to it, by searching the start of the file for text belonging to various licenses. I guess in such case, >90% of the contributors will be missed. By "contributors" I meant the people committed in code for enhancements/bug-fixes etc. I didn't try, but I think it won't work for the "contributors" case in my question, as I think > 90% of them will not put their names to the top of the file, despite how much improvement they made. The output in my OP was automatically generated from git log with a single command without installing any extra packages [1]. It won't miss any one. So if it even barely acceptable, I'm going to stick to it. Thanks [1] https://www.commandlinefu.com/commands/view/4519/list-all-authors-of-a-particular-git-project On Fri, Apr 19, 2019 at 2:39 AM Mo Zhou - lu...@debian.org <pkgoyq.xpt.05ee5440cd.lumin#debian....@ob.0sg.net> wrote: > > Hi, > > The simplest way is to modify automatically generated copyright file: > > $ licensecheck -r --deb-machine . >> debian/copyright > > On Thu, Apr 18, 2019 at 06:04:03PM -0400, Tong Sun wrote: > > Hi, > > > > What is the simplest way to put all contributors into the Debian copyright > > file? > > > > I know the hardest way is associate each with their corresponding > > change files, but for popular projects, the Debian copyright file > > would be unnecessarily HUGE. > > > > Would this be acceptable? Especially for those that contribute scarcely? > > > > Files: * > > Copyright: > > Alexandre Viau <alexan...@alexandreviau.net>, Copyright 2015 > > Alexandre Viau <alexan...@alexandreviau.net>, Copyright 2018 > > Anthony Fok <f...@debian.org>, Copyright 2015 > > Anthony Fok <f...@debian.org>, Copyright 2016 > > Anthony Fok <f...@debian.org>, Copyright 2018 > > ... > > zhsj <zsj950...@gmail.com>, Copyright 2017 > > zhsj <zsj950...@gmail.com>, Copyright 2019 > > > > Detailed example appreciated. thx. > >
