You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a project I am working on, I recently implemented the Free Software Foundation Europe's REUSE (repository) recommendations for licensing. The used licenses are the GNU GPL for code and CC0 for some other stuff, both listed as supported licenses.
In a nutshell, REUSE stores all licenses named as their SPDX identifier in a LICENSES directory. Furthermore, each file starts with a SPDX header.
Because GitHub does not handled this, I created a LICENSE symlink to the GPL file within the LICENSES directory. GitHub then at least detects the presence of a license. (Edit: GitHub only detects a LICENSE file exists, but does not follow the symlink. Thus, I removed the symlink.)
However, the pkg.go.dev page is currently not able to process this. Furthermore, the documentation is "not displayed due to license restrictions". Compared to this, the old GoDoc has no limitations in this regard. Sorry, this is annoying.
Would it be possible to adjust pkg.go.dev to
handle a LICENSES directory,
detect and follow symlinks, or (Edit: see edit above)
to parse SPDX headers?
Thanks a lot for all the great work!
The text was updated successfully, but these errors were encountered:
For legal reasons, we cannot consider SPDX headers authoritative. We must verify the license text itself.
The SPDX-headers list which license texts are to be verified in the first place.
E.g. there are many repositories, where the LICENCES file or COPYING file does not list all licenses used in the repository. So if you are believing this, from a legal point of view, you should also be able to believe the SPDX headers.
A LICENSES directory is a reasonable request. We'll look into it.
Yes, please make it reuse.software compatible. What would have to be done for this?