- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 63.8k
Open
Labels
👥 discussionThis Repo is guided by its community! Let's talk!This Repo is guided by its community! Let's talk!PR requestedIssues that can be addressed with a new PRIssues that can be addressed with a new PRgood first issueA good starting point for newcomersA good starting point for newcomers
Description
#11260 proposed adding licence notations.
#11269 gave an example, passing the linter tests.
We are now requesting PRs to add this info to our repo!
In preparation for beginning to accept PR's which add licenses, This issue proposes a step-by-step workflow to make clear how these are to be added.
- Select an item, preferably a book. (I found a bunch by searching merged PRs for "Creative Commons")
- Access the book, and look for a license statement. For example, in the book added in Update free-programming-books-langs.md with "Computational and Inferential Thinking" #9010 the contributor found the text:
"The contents of this book are licensed for free consumption under the following license:
[Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0)](https://creativecommons.org/licenses/by-nc-nd/4.0/)."
- We're ignoring license variants, so the text to be added to our listing should be
(CC BY-NC-ND)
(note the leading space) At this time we are NOT accepting notations for licenses other than Creative Commons (CC) and the Gnu Free Documentation License (GFDL). - For each item you're adding a license to, write a sentence in your PR about where you found the license statement.
- Don't add license notes for more than one section at at time, and it's ok to do one item for a PR. If you add more than 5 license additions at a time, it will discourage PR reviewers from checking the PR.
Comments, questions and test PRs welcome!
kamranzafar4343, opticaldrive and Enemuo1
Metadata
Metadata
Assignees
Labels
👥 discussionThis Repo is guided by its community! Let's talk!This Repo is guided by its community! Let's talk!PR requestedIssues that can be addressed with a new PRIssues that can be addressed with a new PRgood first issueA good starting point for newcomersA good starting point for newcomers
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
manvith12 commentedon Oct 10, 2024
hey! , i was working on this.
i found a few books where no copyright was mentioned any idea what to do about them?
for example : a beginners guide to matlab
9 remaining items
eshellman commentedon Oct 22, 2024
The reason we are not accepting GPL, LGPL or AGPL license notations is that they are inappropriate for textual works that are not software. BSD, Mozilla, and MIT licenses have similar problems and don't have standard abbreviations.
AkshayTiwari27 commentedon Oct 22, 2024
@eshellman can you please mention the name of acceptable licences.
eshellman commentedon Oct 22, 2024
have added comments in #11315. Sorry for the confusion. I thought it had been specified there.
dhirajchaurasiya commentedon Oct 23, 2024
@eshellman I have added few license notes to Machine Learning books. Please do check and share your review.
Thanks.
Enemuo1 commentedon Apr 9, 2025
Hello, I would like to contribute as well. Is the opportunity still available?
eshellman commentedon Apr 10, 2025
PRs are always welcome, but please follow instructions
WassCodeur commentedon Jun 18, 2025
Hello
My name is Wachiou (pronounced Wasiu in English), I am a backend developer and open source contributor. I have participated in several open source initiatives such as Google Summer of Code 2024 under the auspices of the Python Software Foundation.
I am passionate about free access to knowledge, especially in disadvantaged communities. That's why this issue is particularly close to my heart: adding information about licences helps ensure that resources remain free and clearly usable by everyone.
I would be delighted to contribute by helping to document the licences for these excellent books. I already know how to work with PRs and I carefully follow the contribution guidelines. I look forward to helping you!
Thank you for this opportunity.