I would like to create a github repository with this edited and in a special presentation format. How should I do it? What files the repository should contain and with what contents.

1 Answer 1


Copyright licenses are based on copyright law. As far as copyright is concerned, a repository isn't a thing and copyright licenses generally don't mention the term 'repository' at all or even a term that is similar.
For copyright purposes, a file is a computer term for how data is organized and which typically holds (part of) a copyrightable work.

Thus, copyright licenses generally have very little requirements about what files are present in a repository. They mainly have requirements about what information is given to the recipients of the work.

For software, there are certain conventions about what files to include in your repository, but those conventions are not universally accepted nor is there a legal reason to follow them.

For non-software works (which the "Git Internals PDF" is and which the CC licenses target) the use of a repository is not a given, nor that a work might consist of multiple files. For that reason, it is sufficient if your repository contains just a single file with the final rendered version of the document, as long as that document contains an attribution of "Git Internals PDF" and is under the CC BY-SA 3.0 license itself. As explained by Creative Commons itself, an ideal attribution contains the title, a link to where the original can be obtained, the author of the original and the license (with a link) under which you obtained the original work.

If you decide to treat your work more like software, with a source code that the final document can be rendered from, that final rendered document should meet the requirements of the CC BY-SA 3.0 license without the need for a separate "license file" because that is the common expectation with literary works.

  • 1
    The CC licenses don't require a particular form unless it's the no-derivative license... then you may distribute but not alter it. It's important that the recipeients get a clear indication of the license status and authors of the work. It does not need to be a PDF. It could be in the readme or a license file which accompanies the software. It could be in the splash of a title screen, in the about section... Sep 18, 2020 at 9:24
  • 1
    Especially with the CC licenses it's often a good idea to think about "how would I want to see myself credited in the work shipped, if I were the author of the work I use and require to get attribution" Sep 18, 2020 at 9:26
  • 2
    A good guide is also: where you put your copyright notices, put also the copyright notices of everything you depend on - like these CC assets Sep 23, 2020 at 13:21
  • 1
    I guess the last portion of the README.md is intended as the attribution, but without the knowledge of this question, I would have thought that it identifies you as original author. A better attribution would be a sentence like "Based on Git Internals by Scott Chacon, licensed under CC BY-SA" with the parts marked as italics here being links as you used them. Oct 4, 2020 at 6:10
  • 1
    @xralf I can only agree with Bart van Ingen Schenau: it reads now like you are Scott Chacon. Write it as "Based on 'Git Internals' by Scott Chacon, licensed under CC-BY-SA" with the links as set. Oct 4, 2020 at 11:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.