tor-webwml.git

@@ -792,6 +792,11 @@ meetings around the world.</li>

     been inactive.

     </p>

+    <p>

+    <b>Project Ideas:</b><br />

+    <i><a href="#stemUsability">Stem Usability and Porting (this includes an idea for finishing off TorBEL)</a></i>

+    </p>

+

     <a id="project-tor2web"></a>

     <h3><a

     href="http://wiki.tor2web.org/index.php/Main_Page">Tor2web</a> (<a

@@ -1023,7 +1028,7 @@ meetings around the world.</li>

     <br>

     Skill Level: <i>Medium</i>

     <br>

-    Likely Mentors: <i>Damian (atagar)</i>

+    Likely Mentors: <i>Damian (atagar), Sebastian</i>

     <p>

     <a href="https://stem.torproject.org/">Stem</a> is a

     python controller library for tor. Like it's predecessor, <a

@@ -1044,14 +1049,14 @@ meetings around the world.</li>

     <p>

     Stem has largely met these goals but there's still plenty of low hanging

     fruit in terms of usability improvements. Also, we have clients still using

-    TorCtl that need to be ported over. This project includes several subtasks,

-    see the tickets for additional context...

+    TorCtl that need to be ported over. This project would include several

+    subtasks. Some ideas for instance are...

     </p>

     <ol>

       <li>Come up with a better, more developer friendly "Module Overview" for our documentation (<a href="https://stem.torproject.org/api/control.html">example page</a>). For instance, it would be nice to provide interlinking between the overview and the classes/methods that it lists. This will probably involve asking for help from the <a href="http://sphinx-doc.org/">Sphinx user list</a>. (<a href="https://trac.torproject.org/7632">ticket</a>)</li>

       <li>Navigation of <a href="https://stem.torproject.org">stem's site</a> is clunky, in large part due to the linear page flow supported by sphinx. One possible fix for this would be css-only menus, ideally as a sphinx plugin so we could contribute it back upstream.(<a href="https://trac.torproject.org/8431">ticket</a>)</li>

-      <li>After getting some exposure to stem it would be time to give using it a try. Tor has a couple clients (<a href="https://trac.torproject.org/8263">TorBEL</a> and <a href="https://trac.torproject.org/8264">Tor Weather</a>) that are ready to be moved to stem. Hopefully porting these will also provide us with some lessons on how we can further improve stem's API.</li>

+      <li>After getting some exposure to stem it would be time to give using it a try. Tor has a couple clients (<a href="https://trac.torproject.org/8263">TorBEL</a> and <a href="https://trac.torproject.org/8264">Tor Weather</a>) that are ready to be moved to stem. Hopefully porting these will also provide us with some lessons on how we can further improve stem's API. <b>Note that this would also involve polishing off <a href="#project-torbel">TorBEL</a>, including the <a href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&group=component&component=TorDNSEL%2FTorBEL&order=priority">issues that prevent us from deploying it</a></b>. This later portion would be primarily mentored by Sebastian.</li>

       <li><b>... other ideas?</b> The above are just some ideas I've come up with to improve usability and likely not enough to fill the summer. Feel free to suggest some of your own! For instance, one option would be to expand <a href="https://stem.torproject.org/tutorial.html">stem's tutorials</a> with more examples, maybe <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev/">contacting tor-dev@</a> to brainstorm ideas. This last bit is pretty open so I look forward to seeing what you come up with!</li>

     </ol>