Drop txtorcon project ideas
Damian Johnson

Damian Johnson commited on 2017-01-30 08:21:50
Zeige 1 geänderte Dateien mit 0 Einfügungen und 60 Löschungen.


Meejah reports that the ideas are still relevant but that he doesn't have time
to mentor this summer.
... ...
@@ -578,12 +578,6 @@ meetings around the world.</li>
578 578
     Used by OONI and APAF.
579 579
     </p>
580 580
 
581
-    <p>
582
-    <b>Project Ideas:</b><br />
583
-    <i><a href="#txtorcon_use_txaio">Convert txtorcon to use txaio</a></i><br />
584
-    <i><a href="#txtorcon_use_pytest">Convert txtorcon to py.test</a></i>
585
-    </p>
586
-
587 581
     <a id="project-metrics"></a>
588 582
     <h3><a href="https://metrics.torproject.org/">Metrics</a> (<a
589 583
     href="https://gitweb.torproject.org/metrics-web.git">web</a>)</h3>
... ...
@@ -842,60 +836,6 @@ the codebase that you want to work on.
842 836
     </p>
843 837
     </li>
844 838
 
845
-    <a id="txtorcon_use_txaio"></a>
846
-    <li>
847
-    <b>Convert txtorcon to use txaio</b>
848
-    <br>
849
-    Language: <i>Python, asyncio, Twisted</i>
850
-    <br>
851
-    Likely Mentors: <i>meejah</i>
852
-    <br><br>
853
-    <p>
854
-    txtorcon is currently supports only Twisted users. Re-working txtorcon
855
-    to use the txaio library would allow users to choose between Twisted and
856
-    asyncio for the client code.
857
-    </p>
858
-
859
-    <p>
860
-    This would involve fairly extensive refactoring to txtorcon, as it
861
-    currently makes heavy use of @inlineCallbacks which doesn't work with
862
-    txaio. A prospective student should be very familiar with event-based
863
-    programming in general, and be familiar with one of Twisted or asyncio.
864
-    See also: https://github.com/meejah/txtorcon/issues/135
865
-    </p>
866
-    </li>
867
-
868
-    <a id="txtorcon_use_pytest"></a>
869
-    <li>
870
-    <b>Convert txtorcon to py.test</b>
871
-    <br>
872
-    Language: <i>Python, Twisted</i>
873
-    <br>
874
-    Likely Mentors: <i>meejah</i>
875
-    <br><br>
876
-    <p>
877
-    Currently txtorcon uses the built-in "unittest" module, as well as
878
-    Twisted's Deferred-respecting extensions on top. However, meejah has
879
-    found py.test's "fixture" approach to be much more powerful in other
880
-    situations.
881
-    </p>
882
-
883
-    <p>
884
-    This project would be to port at least part of txtorcon's test-suite to
885
-    use py.test style tests and fixtures and evaluate: are the tests easier
886
-    to read? are there fewer lines of code? If so, the rest of the suite
887
-    should be ported and txtorcon switched over to use py.test exclusively.
888
-    </p>
889
-
890
-    <p>
891
-    As some of txtorcon's tests aren't very well-written, this would take a
892
-    prospective student who is very strong in unit-testing knowledge. As
893
-    txtorcon is event-based, familiarity with that style of programming
894
-    (preferrably with Twisted) is ideal.
895
-    See also: https://github.com/meejah/txtorcon/issues/136
896
-    </p>
897
-    </li>
898
-
899 839
     <a id="stegotorus"></a>
900 840
     <li>
901 841
     <b>Make Stegotorus deployment ready</b>
902 842