Thanks for the reminder, Alexander. I try to find all pull requests that fix open issues before each release, and intermittently between releases, and merge them. If there are particular ones that stand out to you, please link to them and I will make sure to get them merged.
As I've said before, a lot of my time is pulled into Let's Encrypt right now, and I've been economizing by spending less time reviewing new rulesets, since I worry they are likely to introduce more issues, which will increase the maintenance time for HTTPS Everywhere further. One open issue that would make it easier to review new rulesets with confidence: https://github.com/EFForg/https-everywhere/issues/1125 (run fetch test automatically on Travis, for changed rules). All that said, I'll look into adding some contributors to the repository in a more formal fashion. On 08/21/2015 05:10 AM, Alexander Buchner wrote: > Hi, > > on github there are many open pull requests, many of them are several > months old. Many of these pull requests fix open issues. > > It would be nice if someone could merge them or write what's the problem > with a specific pull request so that the author could perhaps work on > the issues. > > For the contributors it's quite frustrating to see that their (needed!) > work was just a waste of time. > > Regards > Alexander > > > > _______________________________________________ > HTTPS-Everywhere mailing list > [email protected] > https://lists.eff.org/mailman/listinfo/https-everywhere
_______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
