Browse code

Order task ideas by project

Most intuitive order I could think of was to list project ideas in the same
order that we list the projects above. Really doesn't matter (most ideas don't
apply to any of them).

Damian Johnson authored on02/02/2017 18:58:45
Showing1 changed files
... ...
@@ -838,6 +838,69 @@ ideas.
838 838
     </p>
839 839
     </li>
840 840
 
841
+    <a id="feedbackExtension"></a>
842
+    <li>
843
+    <b>Feedback Extension for Tor Browser</b>
844
+    <br>
845
+    Likely Mentors: <i>Nima (mrphs)</i>, <i>Sukhbir (sukhe)</i>
846
+    <p>
847
+    Design and implement an extension for Tor Browser that can be used to gather
848
+    end-user UI/UX feedback on an opt-in basis. While the design and
849
+    implementation is left as an exercise for the applicant (and also serves as
850
+    the qualification task), examples of the information we are looking to gather
851
+    can include troubleshooting network connectivity issues, testing the various
852
+    pluggable transports, or gathering information about the network of the users.
853
+    </p>
854
+
855
+    <p>
856
+    Please propose the extension design in a way that the information is strictly
857
+    on an opt-in basis and scrubs any information that can be used to identify a
858
+    user, and also come up with a way to send the gathered information to a
859
+    central server, whether to an onion address (if the user has Tor running), or
860
+    otherwise. To start with, we are looking to gather only text as part of the
861
+    feedback process.
862
+    </p>
863
+    </li>
864
+
865
+    <a id="torBrowserCrashReport"></a>
866
+    <li>
867
+    <b>Crash Reporter for Tor Browser</b>
868
+    <br>
869
+    Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>
870
+    <p>
871
+    Currently Tor Browser disables the Crash Reporter. We would like to
872
+    build it reproducible, enable it, and configure it to report crashes
873
+    containing non-detailed and impersonal information to Tor, on a .onion
874
+    submission platform that would allow us to view and explore the
875
+    crashes.
876
+    </p>
877
+
878
+    <p>
879
+    The project will entail enabling the Crash Report on Tor Browser and
880
+    creating a backend to receive reports from it. Once created, the crash
881
+    reporter data will be analyzed and modified to fit Tor's requirements
882
+    for personal data collection. As time permits, we will update the
883
+    build system to ensure the crash reporter is built reproducibly and
884
+    add data analysis tools for the crash report database to visualize top
885
+    crashers and similar statistics.
886
+    </p>
887
+    </li>
888
+
889
+    <a id="fasterTorBrowser"></a>
890
+    <li>
891
+    <b>Make Tor Browser Faster</b>
892
+    <br>
893
+    Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>
894
+    <p>
895
+    This project will enable and take advantage of HTTP/2, the Alt-Srv
896
+    header, and tor's new single hop .onion mode to enable websites to
897
+    transparently move their traffic to a .onion address. In addition to
898
+    improvements in security, we will benchmark page load and paint times
899
+    under normal HTTP/1.1, HTTP/2, and when taking advantage of features
900
+    such as Server Push.
901
+    </p>
902
+    </li>
903
+
841 904
     <a id="stegotorus"></a>
842 905
     <li>
843 906
     <b>Make Stegotorus deployment ready</b>
... ...
@@ -1051,69 +1114,6 @@ ideas.
1051 1114
     </p>
1052 1115
     </li>
1053 1116
 
1054
-    <a id="feedbackExtension"></a>
1055
-    <li>
1056
-    <b>Feedback Extension for Tor Browser</b>
1057
-    <br>
1058
-    Likely Mentors: <i>Nima (mrphs)</i>, <i>Sukhbir (sukhe)</i>
1059
-    <p>
1060
-    Design and implement an extension for Tor Browser that can be used to gather
1061
-    end-user UI/UX feedback on an opt-in basis. While the design and
1062
-    implementation is left as an exercise for the applicant (and also serves as
1063
-    the qualification task), examples of the information we are looking to gather
1064
-    can include troubleshooting network connectivity issues, testing the various
1065
-    pluggable transports, or gathering information about the network of the users.
1066
-    </p>
1067
-
1068
-    <p>
1069
-    Please propose the extension design in a way that the information is strictly
1070
-    on an opt-in basis and scrubs any information that can be used to identify a
1071
-    user, and also come up with a way to send the gathered information to a
1072
-    central server, whether to an onion address (if the user has Tor running), or
1073
-    otherwise. To start with, we are looking to gather only text as part of the
1074
-    feedback process.
1075
-    </p>
1076
-    </li>
1077
-
1078
-    <a id="torBrowserCrashReport"></a>
1079
-    <li>
1080
-    <b>Crash Reporter for Tor Browser</b>
1081
-    <br>
1082
-    Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>
1083
-    <p>
1084
-    Currently Tor Browser disables the Crash Reporter. We would like to
1085
-    build it reproducible, enable it, and configure it to report crashes
1086
-    containing non-detailed and impersonal information to Tor, on a .onion
1087
-    submission platform that would allow us to view and explore the
1088
-    crashes.
1089
-    </p>
1090
-
1091
-    <p>
1092
-    The project will entail enabling the Crash Report on Tor Browser and
1093
-    creating a backend to receive reports from it. Once created, the crash
1094
-    reporter data will be analyzed and modified to fit Tor's requirements
1095
-    for personal data collection. As time permits, we will update the
1096
-    build system to ensure the crash reporter is built reproducibly and
1097
-    add data analysis tools for the crash report database to visualize top
1098
-    crashers and similar statistics.
1099
-    </p>
1100
-    </li>
1101
-
1102
-    <a id="fasterTorBrowser"></a>
1103
-    <li>
1104
-    <b>Make Tor Browser Faster</b>
1105
-    <br>
1106
-    Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>
1107
-    <p>
1108
-    This project will enable and take advantage of HTTP/2, the Alt-Srv
1109
-    header, and tor's new single hop .onion mode to enable websites to
1110
-    transparently move their traffic to a .onion address. In addition to
1111
-    improvements in security, we will benchmark page load and paint times
1112
-    under normal HTTP/1.1, HTTP/2, and when taking advantage of features
1113
-    such as Server Push.
1114
-    </p>
1115
-    </li>
1116
-
1117 1117
     <a id="ahmiaSearch"></a>
1118 1118
     <li>
1119 1119
     <b>Ahmia - Hidden Service Search</b>