Change some priorities and requirements. Merge usability idea with TBB for Linux/Mac OS X idea.
Karsten Loesing

Karsten Loesing commited on 2009-03-12 22:05:06
Zeige 1 geänderte Dateien mit 26 Einfügungen und 18 Löschungen.

... ...
@@ -151,7 +151,7 @@ Effort Level: <i>Medium</i>
151 151
 <br />
152 152
 Skill Level: <i>Medium</i>
153 153
 <br />
154
-Likely Mentors: <i>Karsten</i>
154
+Likely Mentors: <i>Karsten, Roger</i>
155 155
 <br />
156 156
 It would be great to set up an automated system for tracking network
157 157
 health over time, graphing it, etc. Part of this project would involve
... ...
@@ -221,13 +221,13 @@ experience with Qt is helpful, but not required.
221 221
 <li>
222 222
 <b>Improving Tor's ability to resist censorship</b>
223 223
 <br />
224
-Priority: <i>High</i>
224
+Priority: <i>Medium to High</i>
225 225
 <br />
226
-Effort Level: <i>High</i>
226
+Effort Level: <i>Medium</i>
227 227
 <br />
228 228
 Skill Level: <i>High</i>
229 229
 <br />
230
-Likely Mentors: <i>Nick</i>
230
+Likely Mentors: <i>Nick, Roger, Steven</i>
231 231
 <br />
232 232
 The Tor 0.2.0.x series makes <a
233 233
 href="<svnsandbox>doc/design-paper/blocking.html">significant
... ...
@@ -292,7 +292,7 @@ with others prior to implementation.
292 292
 <li>
293 293
 <b>An Improved and More Usable Network Map in Vidalia</b>
294 294
 <br />
295
-Priority: <i>Medium</i>
295
+Priority: <i>Low to Medium</i>
296 296
 <br />
297 297
 Effort Level: <i>Medium</i>
298 298
 <br />
... ...
@@ -330,7 +330,7 @@ Priority: <i>Medium</i>
330 330
 <br />
331 331
 Effort Level: <i>Medium</i>
332 332
 <br />
333
-Skill Level: <i>Medium</i>
333
+Skill Level: <i>Low to Medium</i>
334 334
 <br />
335 335
 Likely Mentors: <i>Matt</i>
336 336
 <br />
... ...
@@ -459,13 +459,13 @@ Also tricky will be adding rate-limiting to Libevent.
459 459
 <li>
460 460
 <b>Tuneup Tor!</b>
461 461
 <br />
462
-Priority: <i>Medium</i>
462
+Priority: <i>Medium to High</i>
463 463
 <br />
464
-Effort Level: <i>Medium</i>
464
+Effort Level: <i>Medium to High</i>
465 465
 <br />
466
-Skill Level: <i>Medium to High</i>
466
+Skill Level: <i>High</i>
467 467
 <br />
468
-Likely Mentors: <i>Nick, Roger, Mike</i>
468
+Likely Mentors: <i>Nick, Roger, Mike, Karsten</i>
469 469
 <br />
470 470
 Right now, Tor relays measure and report their own bandwidth, and Tor
471 471
 clients choose which relays to use in part based on that bandwidth.
... ...
@@ -526,7 +526,7 @@ Effort Level: <i>Medium</i>
526 526
 <br />
527 527
 Skill Level: <i>Medium</i>
528 528
 <br />
529
-Likely Mentors: <i>Nick</i>
529
+Likely Mentors: <i>Nick, Roger</i>
530 530
 <br />
531 531
 Tor needs to be far more tested. This is a multi-part effort. To start
532 532
 with, our unit test coverage should rise substantially, especially in
... ...
@@ -577,7 +577,7 @@ to a small degree about design.
577 577
 <li>
578 578
 <b>Bring moniTor to life</b>
579 579
 <br />
580
-Priority: <i>Medium</i>
580
+Priority: <i>Low</i>
581 581
 <br />
582 582
 Effort Level: <i>Medium</i>
583 583
 <br />
... ...
@@ -625,9 +625,9 @@ with not too much involvement in the Tor internals.
625 625
 <li>
626 626
 <b>Improving Polipo on Windows</b>
627 627
 <br />
628
-Priority: <i>Medium</i>
628
+Priority: <i>Medium to High</i>
629 629
 <br />
630
-Effort Level: <i>Low</i>
630
+Effort Level: <i>Medium</i>
631 631
 <br />
632 632
 Skill Level: <i>Medium</i>
633 633
 <br />
... ...
@@ -644,7 +644,7 @@ natively (i.e. in Unix-like OSes, Polipo defaults to 25% of ram, in
644 644
 Windows it's whatever the config specifies). 3) some sort of GUI config
645 645
 and reporting tool, bonus if it has a systray icon with right clickable
646 646
 menu options. Double bonus if it's cross-platform compatible.
647
-3) allow the software to use the Windows Registry and handle proper Windows directory locations, such as "C:\Program Files\Polipo"
647
+4) allow the software to use the Windows Registry and handle proper Windows directory locations, such as "C:\Program Files\Polipo"
648 648
 </li>
649 649
 
650 650
 <!-- Is Blossom development still happening?
... ...
@@ -701,7 +701,7 @@ the core of the Blossom effort.
701 701
 <li>
702 702
 <b>Implement a torrent-based scheme for downloading Thandy packages</b>
703 703
 <br />
704
-Priority: <i>Medium</i>
704
+Priority: <i>Medium to High</i>
705 705
 <br />
706 706
 Effort Level: <i>High</i>
707 707
 <br />
... ...
@@ -724,7 +724,7 @@ there should be an easy way for them to help distributing the packages.
724 724
 <li>
725 725
 <b>Torbutton equivalent for Thunderbird</b>
726 726
 <br />
727
-Priority: <i>Medium</i>
727
+Priority: <i>Low</i>
728 728
 <br />
729 729
 Effort Level: <i>High</i>
730 730
 <br />
... ...
@@ -773,6 +773,7 @@ href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>,
773 773
 with not too much involvement in the Tor internals.
774 774
 </li>
775 775
 
776
+<!-- not really suited for GSoC; integrated into TBB for Linux/Mac OS X
776 777
 <li>
777 778
 <b>Usability testing of Tor</b>
778 779
 <br />
... ...
@@ -789,6 +790,7 @@ That would help a lot in knowing what needs to be done in terms of bug
789 790
 fixes or new features. We get this informally at the moment, but a more
790 791
 structured process would be better.
791 792
 </li>
793
+-->
792 794
 
793 795
 <li>
794 796
 <b>Translation wiki for our website</b>
... ...
@@ -866,7 +868,7 @@ Effort Level: <i>High</i>
866 868
 <br />
867 869
 Skill Level: <i>Medium</i>
868 870
 <br />
869
-Likely Mentors: <i>Steven</i>
871
+Likely Mentors: <i>Steven, Andrew</i>
870 872
 <br />
871 873
 The Tor Browser bundle incorporates Tor, Firefox, and the Vidalia user
872 874
 interface (and optionally Pidgin IM). Components are pre-configured to
... ...
@@ -883,6 +885,12 @@ operating system versions and configurations to verify portability.
883 885
 Students should be familiar with application development on one or
884 886
 preferably both of Linux and Mac OS X, and be comfortable with C/C++
885 887
 and shell scripting.
888
+<br />
889
+Part of this project could be usability testing of Tor Browser Bundle,
890
+ideally amongst our target demographic.
891
+That would help a lot in knowing what needs to be done in terms of bug
892
+fixes or new features. We get this informally at the moment, but a more
893
+structured process would be better.
886 894
 </li>
887 895
 
888 896
 <li>
889 897