Remove a few ideas from the Projects list
Sebastian Hahn commited on 2010-03-08 15:27:41
Zeige 1 geänderte Dateien mit 6 Einfügungen und 6 Löschungen.
Removed ideas are: - New Thandy features, because I think we need to get someone dedicated to work on Thandy first so that we can give a student realistic support. - Auto-update framework, because that's Thandy's job - Useability testing of Tor, because that isn't a gsoc project (gsoc requires that code be written)
- en/volunteer.wml 7b40668f2..778c6ed27
| ... | ... |
@@ -411,7 +411,7 @@ href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>, |
| 411 | 411 |
with not too much involvement in the Tor internals. |
| 412 | 412 |
</li> |
| 413 | 413 |
|
| 414 |
-<li> |
|
| 414 |
+<!-- <li> |
|
| 415 | 415 |
<b>New Thandy Features</b> |
| 416 | 416 |
<br /> |
| 417 | 417 |
Priority: <i>Medium</i> |
| ... | ... |
@@ -439,7 +439,7 @@ Familiarity with Windows codepages, unicode, and other character sets |
| 439 | 439 |
is helpful in addition to general win32 and posix API experience and |
| 440 | 440 |
Python proficiency.</li> |
| 441 | 441 |
</ol> |
| 442 |
-</li> |
|
| 442 |
+</li> --> |
|
| 443 | 443 |
|
| 444 | 444 |
<li> |
| 445 | 445 |
<b>Simulator for slow Internet connections</b> |
| ... | ... |
@@ -617,7 +617,7 @@ Debian package management and some C++ development experience. Previous |
| 617 | 617 |
experience with Qt is helpful, but not required. |
| 618 | 618 |
</li> |
| 619 | 619 |
|
| 620 |
-<li> |
|
| 620 |
+<!--<li> |
|
| 621 | 621 |
<b>Tor/Polipo/Vidalia Auto-Update Framework</b> |
| 622 | 622 |
<br /> |
| 623 | 623 |
We're in need of a good authenticated-update framework. |
| ... | ... |
@@ -649,7 +649,7 @@ practices, such as package signature verification. Good writing ability |
| 649 | 649 |
is also important for this project, since a vital step of the project |
| 650 | 650 |
will be producing a design document to review and discuss |
| 651 | 651 |
with others prior to implementation. |
| 652 |
-</li> |
|
| 652 |
+</li>--> |
|
| 653 | 653 |
|
| 654 | 654 |
<li> |
| 655 | 655 |
<b>Improving the Tor QA process: Continuous Integration for builds</b> |
| ... | ... |
@@ -679,7 +679,7 @@ network either on a single machine, or across several, so we can test |
| 679 | 679 |
changes in performance on machines in different roles automatically. |
| 680 | 680 |
</li> |
| 681 | 681 |
|
| 682 |
-<li> |
|
| 682 |
+<!--<li> |
|
| 683 | 683 |
<b>Usability testing of Tor</b> |
| 684 | 684 |
<br /> |
| 685 | 685 |
Priority: <i>Medium</i> |
| ... | ... |
@@ -694,7 +694,7 @@ Especially the browser bundle, ideally amongst our target demographic. |
| 694 | 694 |
That would help a lot in knowing what needs to be done in terms of bug |
| 695 | 695 |
fixes or new features. We get this informally at the moment, but a more |
| 696 | 696 |
structured process would be better. |
| 697 |
-</li> |
|
| 697 |
+</li>--> |
|
| 698 | 698 |
|
| 699 | 699 |
<li> |
| 700 | 700 |
<b>An authenticating IRC proxy</b> |
| 701 | 701 |