[tor-commits] r26585: {website} Dropping 'Automated Reporting of Buggy Rulesets' Yan reports (website/trunk/getinvolved/en)

[Damian Johnson]

Author: atagar
Date: 2014-02-04 16:42:27 +0000 (Tue, 04 Feb 2014)
New Revision: 26585

Modified:
   website/trunk/getinvolved/en/volunteer.wml
Log:
Dropping 'Automated Reporting of Buggy Rulesets'

Yan reports that this was part of her OPW project last year. It's mostly done.



Modified: website/trunk/getinvolved/en/volunteer.wml
===================================================================
--- website/trunk/getinvolved/en/volunteer.wml	2014-02-04 16:41:30 UTC (rev 26584)
+++ website/trunk/getinvolved/en/volunteer.wml	2014-02-04 16:42:27 UTC (rev 26585)
@@ -1069,39 +1069,6 @@
     </p>
     </li>
 
-    <a id="reportingBuggyRulesets"></a>
-    <li>
-    <b>Automated Reporting of Buggy Rulesets</b>
-    <br>
-    Effort Level: <i>Medium</i>
-    <br>
-    Skill Level: <i>Medium</i>
-    <br>
-    Likely Mentors: <i>Peter Eckersley (pde), Micah Lee</i>
-    <p>
-When users manually disable an HTTPS Everywhere ruleset via the toolbar menu,
-that's a strong hint that that ruleset might be buggy.  If we could obtain
-statistics about which rulesets are manually disabled by the users of which
-HTTPS E versions, we could get a statistical picture of which rulesets need
-the most urgent debugging and/or disablement.  This would enormously improve
-the quality of the HTTPS Everywhere user experience.
-    </p>
-
-    <p>
-HTTPS Everywhere already includes a pipeline for anonymised user submissions
-(via Tor where available) that is used for the Decentralized SSL Observatory.
-We should do a popup that asks the users to submit anonymous reports of
-disabled rules, when they manually disable one for the first time.
-    </p>
-
-    <p>
-Perhaps this feature could optionally let users submit the URL of the page
-they were looking at when the bug occurred, although we would need to take
-care in handling those, and perhaps implement some countermeasures against
-sending passwords or auth tokens when URLs contain those.
-    </p>
-    </li>
-
     <a id="httpsEverywhereRulesetTesting"></a>
     <li>
     <b>Incorporate Ruleset Testing into the HTTPS Everywhere release process</b>