[HTTPS-Everywhere] HTTPS Everywhere licensing and GitHub repositories

[mezzanine at Safe-mail.net]

Late last year, there was an InfoWorld article, "GitHub needs to take open source seriously" about
licensing information being unclear for GitHub repositories.

GitHub needs to take open source seriously
http://www.infoworld.com/d/open-source-software/github-needs-take-open-source-seriously-208046?page=0,1

Perhaps it would be useful to add a blurb about HTTPS Everywhere licensing to the README file that is
already present in the source tree. (According to the https://www.eff.org/https-everywhere/development
page, the HTTPS Everywhere code is licensed under GPLv3+ with most of the code being GPLv2 compatible;
presumably, the contributed rulesets are also licensed under GPLv3+.) In addition, there might be
something to be said for including a text copy of the GPLv3 license file in case someone comes across
the HTTPS Everywhere code in the future and is interested in reusing it.

--Richard