Author: atagar
Date: 2013-04-09 03:48:32 +0000 (Tue, 09 Apr 2013)
New Revision: 26150
Modified:
website/trunk/getinvolved/en/volunteer.wml
Log:
Dropping the navbar menu from stem's gsoc idea
Project was too tasty, did it this last weekend. :P
Modified: website/trunk/getinvolved/en/volunteer.wml
===================================================================
--- website/trunk/getinvolved/en/volunteer.wml 2013-04-09 03:46:16 UTC (rev
26149)
+++ website/trunk/getinvolved/en/volunteer.wml 2013-04-09 03:48:32 UTC (rev
26150)
@@ -1096,7 +1096,6 @@
<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. <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>
_______________________________________________
tor-commits mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
