Clarification on Forking/Attributing? about blue-book

[lyz-code]

Hi @supertylerc thanks for the efforts on giving back attribution.

You explicitly request that the fork not happen via the GitHub forking process. What is the preferred way for one to provide original attribution and credit?

I don't mind if you fork it directly, the only drawback is that you'll always see a message in your repo similar to This branch is 909 commits ahead, 1030 commits behind lyz-code:master. like you can see in this fork. Also if you don't want to keep all the content I've made so far and want to start from scratch then the only thing that is useful for you is the skeleton I've made, and I don't need any attribution or credit for that :P.

If on the other hand you do want to keep all my content, then wouldn't it be better to just make contributions to this repository instead?

Therefore the best way to give credit and attribution is by building your garden (the more we are writing the merrier :) ), and then if you want to spread the word that my garden exists within your content then that would be awesome.

If you do, remember to add yourself to the digital garden's list

If one wants to keep some content but remove other content, is this ok? If so, what's the preferred way to provide appropriate credit on a per-page/article basis?

Of course! use whatever you want of my content. What I usually do to provide credit to the sources is to link each section of a document from wherever I took it from, or add it to the bottom of the documents under a References section.

Take for example the Python snippets document, each section has a link to where I took the info from. You could do the same on the articles you got from my book by linking to them.

I hope to have answered your question, if not tell me and/or reopen the issue.

And please contact me once you have it up!