Author: atagar
Date: 2013-04-23 14:24:32 +0000 (Tue, 23 Apr 2013)
New Revision: 26167

Modified:
   website/trunk/getinvolved/en/volunteer.wml
Log:
Fixing stem tutorial urls

Stem's tutorial links pointed to the old location (I changed it a long while
back from '/tutorial' to '/tutorials'). Caught thanks to depierre.



Modified: website/trunk/getinvolved/en/volunteer.wml
===================================================================
--- website/trunk/getinvolved/en/volunteer.wml  2013-04-22 22:09:42 UTC (rev 
26166)
+++ website/trunk/getinvolved/en/volunteer.wml  2013-04-23 14:24:32 UTC (rev 
26167)
@@ -1125,11 +1125,11 @@
     <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>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>
+      <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/tutorials.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>
 
     <p>
-    <b>As part of your application for this project please write a script that 
does something interesting with stem.</b> Bonus points if this is something 
that we can <a href="https://stem.torproject.org/tutorial.html";>make a 
tutorial</a> around!
+    <b>As part of your application for this project please write a script that 
does something interesting with stem.</b> Bonus points if this is something 
that we can <a href="https://stem.torproject.org/tutorials.html";>make a 
tutorial</a> around!
     </p>
 
     <a id="stemTestingForTor"></a>

_______________________________________________
tor-commits mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

Reply via email to