Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

step-by-step for adding license notes #11355

Open
eshellman opened this issue Oct 3, 2024 · 6 comments
Open

step-by-step for adding license notes #11355

eshellman opened this issue Oct 3, 2024 · 6 comments
Labels
👥 discussion This Repo is guided by its community! Let's talk! good first issue A good starting point for newcomers PR requested Issues that can be addressed with a new PR

Comments

@eshellman
Copy link
Collaborator

eshellman commented Oct 3, 2024

#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.

  1. Select an item, preferably a book. (I found a bunch by searching merged PRs for "Creative Commons")
  2. 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/)."
  1. 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).
  2. For each item you're adding a license to, write a sentence in your PR about where you found the license statement.
  3. 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!

@manvith12
Copy link
Contributor

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

@eshellman
Copy link
Collaborator Author

if there is no copyright notice or license, don't do anything.

@eshellman
Copy link
Collaborator Author

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
Copy link
Contributor

@eshellman can you please mention the name of acceptable licences.

@eshellman
Copy link
Collaborator Author

have added comments in #11315. Sorry for the confusion. I thought it had been specified there.

@dhirajchaurasiya10
Copy link
Contributor

@eshellman I have added few license notes to Machine Learning books. Please do check and share your review.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👥 discussion This Repo is guided by its community! Let's talk! good first issue A good starting point for newcomers PR requested Issues that can be addressed with a new PR
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants