To fix the following offense
```sh
Offenses:
Gemfile:11:5: C: Style/StringLiterals: Prefer single-quoted strings when you don't need string interpolation or special symbols. (https://github.com/rubocop-hq/ruby-style-guide#consistent-string-literals)
gem "jekyll-github-metadata"
^^^^^^^^^^^^^^^^^^^^^^^^
14 files inspected, 1 offense detected
```
Added comments
This link will direct anyone who wants to edit this page directly to the Github path which contains the file.
CHANGELOG :
1. Added the [GitHub Metadata] (http://jekyll.github.io/github-metadata/) plugin to Gemfile and Plugins
2. Added the link to the sidebar for license pages.
Github issue #433
Claiming open source licenses need to be demystified is a claim
that they are mysterious. Choosealicense.com is not *Capital*; its
topic does not need to be mystified and demystified at once.
http://robertpaulwolff.blogspot.com/2014/09/more-on-language-and-social-reality.html
Someone encountering open source licenses for the first time at
choosealicense.com should have zero reason to think open source
licensing is mysterious.
Remove "If you have questions or issues, it is always best to consult
a legal professional."
It's not always best, especially considering it's costly and for
most finding one knowledgable about open source licensing will be
difficult.
If it were always best, the site should consist of
<h1>Consult a legal professional.</h1>
But seriously, claiming one should consult a legal professional is
no way to make choosing an open source license non-scary.
and are structured
grant (permissions)
conditioned on (conditions)
with limitations
Permissions coming first combats mistaken but apparently widespread
impression that licenses impose conditions, even such that without
a license, there would be no conditions/work would be in the public
domain.
Requirements->Conditions emphasizes that they are pertinent if one
wants to take advantage of permissions.
Forbiddens->Limitations is more accurate: in most cases licenses
don't give permission to hold licensors liable, in some cases to
use licensors' trademarks or patents, but a licensee does not lose
the permissions granted by the license if the licensee holds licensor
liable, etc. Also emphasizes that there are limitatations on the
license grant, not that the license imposes prohibitions.
The most concise place to see both the rename and reorder is in
_includes/license-overview.html
I did not reorder the appearance of the groups of properties in
license source files (.txt files in _licenses) as those orderings
are not used to render anything on the webiste. Might do so later.
