Support the REUSE spec for license information #173173
-
Select Topic AreaQuestion BodyThe Free Software Foundation Europe created a fairly nice specification called REUSE.
It is becoming somewhat common in projects, one example being cURL which is hosted here on GitHub. cURL seems to work around GitHub's lack of support through just mirroring the license information in the root of the repository. https://github.com/curl/curl/blob/master/COPYING I think the answer to my question is no, but I am wondering if it is on GitHub's roadmap. At least one other forge software supports REUSE (SourceHut). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
At the moment, GitHub does not have native support for the REUSE specification from FSFE. Licensing detection on GitHub primarily relies on the presence of standard license files (e.g., LICENSE or COPYING) and the licensee There’s no public information indicating that REUSE support is on GitHub’s roadmap. If you’d like to see it implemented, the best path is to open a feature request through GitHub Feedback For now, projects that want to follow REUSE can still include the recommended files and headers in their repositories, but GitHub will not interpret them beyond the usual license detection. |
Beta Was this translation helpful? Give feedback.
At the moment, GitHub does not have native support for the REUSE specification from FSFE. Licensing detection on GitHub primarily relies on the presence of standard license files (e.g., LICENSE or COPYING) and the licensee
library, which can identify many common open source licenses.
There’s no public information indicating that REUSE support is on GitHub’s roadmap. If you’d like to see it implemented, the best path is to open a feature request through GitHub Feedback
so that the product team can review community interest.
For now, projects that want to follow REUSE can still include the recommended files and headers in their repositories, but GitHub will not interpret them beyond the usu…