Author: atagar Date: 2013-03-08 17:00:50 +0000 (Fri, 08 Mar 2013) New Revision: 26093

Modified: website/trunk/getinvolved/en/volunteer.wml Log: Dropping stem's PathSupport project from the page

Last year I proposed a stem counterpart for PathSupport as a project for GSoC. This did not go very well since we really haven't a clue *what* we want from such a project. Since then this has not changed and there's little reason to leave it on the page (even commented out).

Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2013-03-08 16:57:52 UTC (rev 26092) +++ website/trunk/getinvolved/en/volunteer.wml 2013-03-08 17:00:50 UTC (rev 26093) @@ -1650,68 +1650,6 @@ </li> -->

- <!-- - <a id="stemPathsupport"></a> - <li> - <b>Stem PathSupport Capabilities</b> - <br> - Effort Level: <i>High</i> - <br> - Skill Level: <i>Medium</i> - <br> - Likely Mentors: <i>Damian (atagar)</i> - <p><a - href="https://trac.torproject.org/projects/tor/wiki/doc/stem">Stem</a> is a - python controller library for tor. Like it's predecessor, <a - href="#project-torctl">TorCtl</a>, it uses tor's <a - href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt">control - protocol</a> to help developers program against the tor process, enabling - them to build things similar to <a href="#project-vidalia">Vidalia</a> and - <a href="#project-arm">arm</a>.</p> - - <p>While TorCtl provided a fine first draft for this sort of functionality, - it has not proved to be extensible nor maintainable. Stem is a rewrite of - TorCtl with a heavy focus on testing, documentation, and providing a - developer friendly API.</p> - - <p>At the moment stem is still very much incomplete, missing several pieces - of functionality that TorCtl provides. This is a project to fix that by - porting TorCtl's <a - href="https://gitweb.torproject.org/pytorctl.git/blob/HEAD:/PathSupport.py">PathSupport - module</a> to stem, writing tests for it, and migrate a couple clients to - use it.</p> - - <p>PathSupport provides applications with programmatic control over how - tor's circuits are built, for instance letting you exit from particular - relays. This is used by projects like <a href="#project-torbel">TorBEL</a>, - <a href="#project-torflow">the Bandwidth Scanners, and SoaT</a>.</p> - - <p>This project can be broken into three parts...</p> - - <ol style="list-style-type: decimal"> - <li><p>Look at PathSupport's clients to figure out how it is used and - come up with the API that we will use for stem. Note that the goal if - this project is <b>not</b> to simply copy PathSupport, but to make it - better. This task would ideally be done as part of writing the GSoC - application.</p></li> - <li><p>Implement the PathSupport counterpart for stem. This should be - done in an incremental fashion, writing the feature, tests, and going - through a code review before moving on. I'll be pretty anal about making - it as good as we can during these code reviews so plan for this to take a - while. ;)</p></li> - <li><p>The real test of the API that you've developed will come when we - use it in some real applications. Try to migrate a TorCtl client or two - to stem, filling in functionality that we're missing and improving our - API as we discover issues. A particularly good client to start with would - be TorBEL.</p></li> - </ol> - - <p><b> - Upon reflection this is not an especially good project for this year's GSoC. You are still perfectly wecome to apply for this project, but <a href="https://trac.torproject.org/projects/tor/wiki/doc/stem">other stem related tasks</a> such as implementing a general controller, descriptor fetching, and client migrations would be better. For the discussion that lead to this see <a href="http://archives.seul.org/or/dev/Apr-2012/msg00006.html">this thread</a>. - </b></p> - </li> - --> - <a id="stemUsability"></a> <li> <b>Stem Usability and Porting</b>