License parsing with GitHub

[TechnologyClassroom]

If you move the file /LICENSES/GPL-2.0-or-later.txt to /LICENSE, GitHub will be able to parse the license and display the license for timeshift within the first page view. I did not see the license on the first page and had to search in the contents of the repo to find it.

[mtwebster]

But, putting them in LICENSES is recommended isn't it? (we just put it there 5 months ago): 0b21b1e

https://reuse.software/spec/#license-files

[TechnologyClassroom]

That is one way to do it typically when the project includes several licenses. The parsing engines for GitHub, GitLab, and other forges do not seem to be able to pickup that method. LICENSE and COPYING files seem to be the first place that they look.

I'm now curious about the GPLv3 license that was in COPYING.

[github-actions]

This issue has been automatically marked as stale because it has not had
any activity in over 2 years.

If this issue is still relevant:

• Please test on a current version of this package.
• Add a comment with your findings

If no activity occurs in the next 30 days, this issue will be
automatically closed. Issues can be reopened if needed.

[TechnologyClassroom]

Still relevant.

[ygerlach]

is github happy when we create a symlink?

Do we care?

[TechnologyClassroom]

is github happy when we create a symlink?

I am not sure, but it would be easy enough to try.