Author: atagar Date: 2013-04-23 14:39:34 +0000 (Tue, 23 Apr 2013) New Revision: 26168 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Subtasks for txtorcon/stem project idea Meejah and I haven't come up with many ideas for additional subtasks, but adding what we got. Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2013-04-23 14:24:32 UTC (rev 26167) +++ website/trunk/getinvolved/en/volunteer.wml 2013-04-23 14:39:34 UTC (rev 26168) @@ -947,6 +947,19 @@ project would entail eliminating duplication by leveraging Stem's parsing in txtorcon while keeping txtorcon's API the same (or at least close).</p> + <p>Besides this you should identify some additional tasks to improve our + controller space across these two libraries. Some ideas are...</p> + <ul> + <li>Write a tutorial for <a + href="https://stem.torproject.org/tutorials.html">stem's tutorial + page</a> demonstrating cross txtorcon/stem usage.</li> + <li>Expand the txtorcon API to include functionality of <a + href="https://gitweb.torproject.org/stem.git/blob/HEAD:/stem/control.py">stem's + controller</a> that would be of interest to twisted users. All additions + should include tests!</li> + <li>Come up with some ideas of your own! We'd love to discuss them with + you.</li> + </ul> <p>This would very likely involve changes to both libraries, although most would be expected to be in txtorcon. meejah is available to mentor txtorcon changes, and Damian (atagar) can help with Stem.</p>