[HTTPS-Everywhere] HTTPS Everywhere licensing and GitHub repositories

[Seth Woodworth]

When I tried to contribute a patch a year and a half ago, I had a hard time
finding the source tree.
I ended up submitting a pull request via github to aaronsw's
repo<https://github.com/aaronsw/https-everywhere>,
which is the first result on github for
'https-everywhere'<https://github.com/search?q=https-everywhere>
.

Would the EFF be amenable to a github fork of https-everywhere?  It would
lower the overhead of contributors finding the project and submitting
rules.   There are already a dozen or so forks on github, and all of them
out of date.

--S


On Fri, Feb 15, 2013 at 2:41 AM, <mezzanine at safe-mail.net> wrote:

> 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
>
> _______________________________________________
> HTTPS-everywhere mailing list
> HTTPS-everywhere at mail1.eff.org
> https://mail1.eff.org/mailman/listinfo/https-everywhere
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.eff.org/pipermail/https-everywhere/attachments/20130218/677133c9/attachment.html>