<div dir="ltr">When I tried to contribute a patch a year and a half ago, I had a hard time finding the source tree.  <div>I ended up submitting a pull request via github to <a href="https://github.com/aaronsw/https-everywhere">aaronsw's repo</a>, which is the first result on github for <a href="https://github.com/search?q=https-everywhere">'https-everywhere'</a>.</div>
<div><br></div><div style>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.</div>
<div style><br></div><div style>--S</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Feb 15, 2013 at 2:41 AM,  <span dir="ltr"><<a href="mailto:mezzanine@safe-mail.net" target="_blank">mezzanine@safe-mail.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Late last year, there was an InfoWorld article, "GitHub needs to take open source seriously" about<br>
licensing information being unclear for GitHub repositories.<br>
<br>
GitHub needs to take open source seriously<br>
<a href="http://www.infoworld.com/d/open-source-software/github-needs-take-open-source-seriously-208046?page=0,1" target="_blank">http://www.infoworld.com/d/open-source-software/github-needs-take-open-source-seriously-208046?page=0,1</a><br>

<br>
Perhaps it would be useful to add a blurb about HTTPS Everywhere licensing to the README file that is<br>
already present in the source tree. (According to the <a href="https://www.eff.org/https-everywhere/development" target="_blank">https://www.eff.org/https-everywhere/development</a><br>
page, the HTTPS Everywhere code is licensed under GPLv3+ with most of the code being GPLv2 compatible;<br>
presumably, the contributed rulesets are also licensed under GPLv3+.) In addition, there might be<br>
something to be said for including a text copy of the GPLv3 license file in case someone comes across<br>
the HTTPS Everywhere code in the future and is interested in reusing it.<br>
<br>
--Richard<br>
<br>
_______________________________________________<br>
HTTPS-everywhere mailing list<br>
<a href="mailto:HTTPS-everywhere@mail1.eff.org">HTTPS-everywhere@mail1.eff.org</a><br>
<a href="https://mail1.eff.org/mailman/listinfo/https-everywhere" target="_blank">https://mail1.eff.org/mailman/listinfo/https-everywhere</a><br>
</blockquote></div><br></div>