> Can we agree that REUSE-compliance (or otherwise making sure mixxx is properly open-source licensed) is something worth caring about?
Yes, if we keep the maintenance burden at a minimum.
To be "correct" we need to put the legal name of the copy right holders into the file. I don't think we can effort that. Copying the email address from the git commit to the file is a reference to the list of copyright holders.
> Can we agree that REUSE-compliance (or otherwise making sure mixxx is properly open-source licensed) is something worth caring about?
Yes, if we keep the maintenance burden at a minimum.
To be "correct" we need to put the legal name of the copy right holders into the file. I don't think we can effort that. Copying the email address from the git commit to the file is a reference to the list of copyright holders.
Why not follow the pattern from: /github. com/mixxxdj/ mixxx/blob/ main/COPYING
https:/
// SPDX-FileCoprig htText: 2000-2022 The respective Mixxx authors
The maintanace burden is to advance the year when editing the file. That can be done by a commit hook
How will the licence identifier look like?