Does GitHub have any support for FSFE's REUSE for managing licensing information #44922
Replies: 7 comments 3 replies
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
I personally find the lack of attention on this issue very annoying. GitHub is supposed to be a home of free of open source software, but can't support those of us that are trying to use a standard licensing layout to make licensing easy to understand when generating bills of material, etc. |
Beta Was this translation helpful? Give feedback.
-
Duplicate of #15033 |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Still relevant |
Beta Was this translation helpful? Give feedback.
-
If any GitHub employee ever sees this, please know that I will never try to ever make another post on this board. You people are just wasting the time of open source contributors with this stupid fucking stalebot. Stalebots are not valid ways to manage projects, and the fact that a trillion+ dollar company cannot manage a project is simply comical. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
The 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.
All reactions