[HTTPS-Everywhere] Call for volunteers: ruleset bug triage!

Yan Zhu yan at eff.org
Mon Feb 3 13:17:44 PST 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi HTTPS Everywhere lists,

It would be great if we had some volunteers to do ruleset bug triage
for HTTPS Everywhere. This is going to be especially important because
we're planning to make the development branch stable in the next few
months, so every reported bug in development needs to get fixed by
then. (FYI, the dev branch has about 3x the number of rules in stable!)

Here's the tasks that I need help with before 4.0 can become stable:

1. Go through HTTPS Everywhere mailing list archives from the last
couple months and look for ruleset bug reports / new rulesets /
patches. Copy all of these to the Github bug tracker [1] or
trac.torproject.org [2], whichever you prefer.

2. Go through the two bug trackers and do the following triage tasks:
* Mark duplicated ruleset bugs as duplicates.
* Delete old ruleset bugs that have been fixed or are irrelevant.
* Verify that ruleset bugs are reproducible. If so, leave a comment
saying that you've reproduced it with any relevant system info.
* Change the category/priority of bugs if necessary.

(For more info on how to be good at bug triage, see
http://www.chromium.org/getting-involved/bug-triage.)

I would prefer to have one person in charge of #1 (migrating bug
reports and new rulesets from email to a bug tracker), so ping me if
you'd like to take the lead on that.

#2 needs as many hands as possible. The Github bug tracker is under
control because it's so new, but trac.torproject.org has a long
backlog of tickets that need to be looked at. So help with bug triage
on trac would be greatly appreciated.

[1] Github: https://github.com/EFForg/https-everywhere/issues/

[2] Trac:
https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&groupdesc=1&group=type&max=200&component=EFF-HTTPS+Everywhere&component=HTTPS+Everywhere%3A+Chrome&order=priority&col=id&col=summary&col=component&col=status&col=owner&col=type&col=priority&col=milestone&report=19

Thanks for all your help in making the web a safer place!
- -Yan

- -- 
Yan Zhu                           yan at eff.org
Technologist                      Tel  +1 415 436 9333 x134
Electronic Frontier Foundation    Fax  +1 415 436 9993
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJS8Ad1AAoJENC7YDZD/dns2J4IAKGaUbDtJYlm+SB7zjoNe8vp
/h6/6yBX0sYIaf7YSHvIoP6VJrn5g0EzKHNj+9d/8b40167PnxmrAy+GZFaNy/jN
CmtpxjXI7LzO6YXEC5LyYLkBg3UFzB97/qIKvANLdUUDh6LGlDsaasgzP76xb9SF
l52TYeayo4/XtEf8X8DGktUd3YKqh2HWO/MLcwQ3nW6bbsZiK+ONGADyRV4YDfm/
8aznwuql/z6TYcoDWEB/lUaZXPH/7gn4VlUdRGZm1Fi+O0ZIAXR1oe0n7y6lJDwa
0vHTSaNB9qkbAdVGkIHFdua1bvbND4qkBxJAeB5ybt3IuckRgfYBhNgHSJupt9Q=
=bjBj
-----END PGP SIGNATURE-----


More information about the HTTPS-Everywhere mailing list