idleberg / creative-commons-markdown Goto Github PK

Markdown-formatted Creative Commons licenses

License: Other

creative-commons-markdown's Introduction

Creative Commons Markdown

On November 25th, 2013, Creative Commons announced their next generation licenses: Creative Commons 4.0. By default, these are available as HTML or plaintext. This project adds Markdown-formatted licenses to that list, while aiming for best compatibility on GitHub.

Licenses

BY – Attribution
BY-NC – Attribution-NonCommercial
BY-NC-ND – Attribution-NonCommercial-NoDerivatives
BY-NC-SA – Attribution-NonCommercial-ShareAlike
BY-ND – Attribution-NoDerivatives
BY-SA – Attribution-ShareAlike
CC0 – CC0

File extension

There's a plethora of Markdown file extensions, but I have decided to go with markdown. Read why:

"We no longer live in a 8.3 world, so we should be using the most descriptive file extensions. It’s sad that all our operating systems rely on this stupid convention instead of the better creator code or a metadata model, but great that they now support longer file extensions."

– Hilton Lipschitz (via)

"…the only file extension I would endorse is “.markdown”, for the same reason offered by Hilton Lipschitz"

– John Gruber, creator of Markdown (via)

Usage

There are other ways to get the licenses than downloading the latest release in your browser:

# Use git
$ git clone https://github.com/idleberg/Creative-Commons-Markdown cc-md

# npm
$ npm install cc-md

Contribute

If you notice any mistakes in content or formatting, please send a pull request with your correction.

creative-commons-markdown's People

Contributors

Stargazers

Watchers

Forkers

xkraty cheebow upisfree tulio joshuavial mojoaxel matthewmccullough dosumis unboundhuman jakl tomburtonwood stevenblenkinsop jmatsushita indolering melvin0008 eduac mrjohannchang volker-e captn3m0 ymarcon jasimpson polosson suspectpart edwardpmorris spikeheap storagebot lipki retrography awickert turnrye arcanneero newopenbible masasin rungee f-jennings jakuza randylubin eschnett cliffordanderson a0726h77 nlwashington mbauman jcc10 platisd rafacouto siemvaessen hasimir kyyberi mithro ellysh deastiny martindsouza smckeown fhcflx nicoboss mathieunls rynehager georgjaehnig jmaupetit allmende raychou spidy88 riordan gdonval developerdocs mikecroucher fuddl bonzi veeara282 atruskie fizzl spiderbaby jaaamessszzz persn peppy runarbu pral2a sadv1r etolstoy maxkfranz oberhauserg oeway jakevdp tarebyte dalekunce ares566 migleorange crazypython echopenhq drcjar smddzcy raymelon couby casutton davidnuon mrchristian oatycreates openfab-lab dasch124 opentnf

creative-commons-markdown's Issues

Do we still need two branches/versions?

Now that CommonMark is up live on all of GitHub, does the tab version look correctly rendered? If so, do we need two branches/versions still?

I would volunteer to clean up the repo, but I am unsure on the answers.

Missing License

Ironically, this repo doesn't include a LICENSE file, so technically we cannot reuse these formats of the CC license you've created :)

Missing boldface

According to Legal Code Defined, the "Formatting of license text (bold, italic, underline, etc.)" is part of the legal code. It should therefore be reproduced exactly. I found at least one deviation (haven't searched for others) at CC BY 4.0, Section 1, letter k.

The correct emphasis should be ("Your" in boldface):

You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning.

This probably should also be fixed in the other CC BY-* licenses.

Title Hierarchy

Hi,

Maybe more of a question that an issue per se.

Your files start with

## creative commons

# Attribution-NonCommercial-NoDerivatives 4.0 International

or similarly.

Why are you starting with a level 2 header (##) and then following with a level 1 header (#)?

As far as I know, and e.g. Mozilla says the same, we should

Avoid skipping heading levels: always start from <h1>, next use <h2> and so on.

So, why this choice?

rename "creative-commons-markdown" to "awesome-creative-commons-markdown"

Hi.

An initial suggestion would be to change the name of the repository to "awesome-creative-commons-markdown". This can make it easier to search for the repository on Google and GitHub.

Does it make sense or not?