What are requirements regarding "awesome" lists and licenses? #350

Closed
opened 2025-11-06 15:13:22 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @hesreallyhim on GitHub (Apr 20, 2025).

I'm starting a new list of awesome Claude Code stuff, and I'm poking around GitHub for people who've posted their files publicly.

Can you clarify what are the rules regarding inclusion on an "awesome" list and licenses? If I'm just linking to a public file in a public repo, does this even count as re-distribution (i.e., does the license even matter)? I'd prefer to get willing and enthusiastic contributors, but I would like any info you can share about whether it's OK to post or at least link to public files on github regardless of/depending on the license type for the repo.

Thanks.

Originally created by @hesreallyhim on GitHub (Apr 20, 2025). I'm starting a new list of [awesome Claude Code stuff](https://github.com/hesreallyhim/awesome-claude-code), and I'm poking around GitHub for people who've posted their files publicly. Can you clarify what are the rules regarding inclusion on an "awesome" list and licenses? If I'm just linking to a public file in a public repo, does this even count as re-distribution (i.e., does the license even matter)? I'd prefer to get willing and enthusiastic contributors, but I would like any info you can share about whether it's OK to post or at least link to public files on github regardless of/depending on the license type for the repo. Thanks.
Author
Owner

@larsenv commented on GitHub (Apr 20, 2025):

they have to be considered awesome, if its lame it doesnt count. just make a list with everything you think is awesome

@larsenv commented on GitHub (Apr 20, 2025): they have to be considered awesome, if its lame it doesnt count. just make a list with everything you think is awesome
Author
Owner

@hesreallyhim commented on GitHub (Apr 20, 2025):

OK, thanks, so I take it from your response that there are no issues around licenses and lists. Regardless of the "official" awesome lists, do you know if this is true in general? Just want to make sure I'm compliant. Surely, if someone decides to take a file I've shared/linked-to and modify it, then licensing would come up? Also, is there a difference to you knowledge between linking and re-posting?

@hesreallyhim commented on GitHub (Apr 20, 2025): OK, thanks, so I take it from your response that there are no issues around licenses and lists. Regardless of the "official" awesome lists, do you know if this is true in general? Just want to make sure I'm compliant. Surely, if someone decides to take a file I've shared/linked-to and modify it, then licensing would come up? Also, is there a difference to you knowledge between linking and re-posting?
Author
Owner

@sindresorhus commented on GitHub (Apr 20, 2025):

Mentioned in https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md

@sindresorhus commented on GitHub (Apr 20, 2025): Mentioned in https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md
Author
Owner

@hesreallyhim commented on GitHub (Apr 20, 2025):

OK thanks, I did notice the requirement about awesome-lists, but my question was about the repos that are actually part of the list - i get the impression that if you're just linking to something, the license is irrelevant, but may matter if i wanted to re-post the code from the other repo in my list. anyway, thanks for the info

@hesreallyhim commented on GitHub (Apr 20, 2025): OK thanks, I did notice the requirement about awesome-lists, but my question was about the repos that are actually part of the list - i get the impression that if you're just linking to something, the license is irrelevant, but may matter if i wanted to re-post the code from the other repo in my list. anyway, thanks for the info
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#350