Adding a project for cross txtorcon/stem integration

Project proposal from meejah where I'd be the backup mentor.

getinvolved/en/volunteer.wml

@@ -660,6 +660,7 @@ meetings around the world.</li>
 
     <p>
     <b>Project Ideas:</b><br />
+    <i><a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a></i><br />
     <i><a href="#stemUsability">Stem Usability and Porting</a></i><br />
     <i><a href="#stemTestingForTor">Stem Tests for Tor</a></i>
     </p>
@@ -675,6 +676,11 @@ meetings around the world.</li>
     Used by OONI and APAF.
     </p>
 
+    <p>
+    <b>Project Ideas:</b><br />
+    <i><a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a></i>
+    </p>
+
     <a id="project-tlsdate"></a>
     <h3>Tlsdate (<a href="https://github.com/ioerror/tlsdate">code</a>)</h3>
 
@@ -920,6 +926,28 @@ meetings around the world.</li>
     </li>
     -->
 
+    <a id="txtorcon-stemIntegration"></a>
+    <li>
+    <b>Txtorcon/Stem Integration</b>
+    <br>
+    Effort Level: <i>Medium</i>
+    <br>
+    Skill Level: <i>Medium</i>
+    <br>
+    Likely Mentors: <i>meejah, Damian (atagar)</i>
+    <p>Txtorcon is a Twisted-based Python controller library, and Stem is a
+    synchronous (threaded) one, also in Python. There is no need to have
+    two implementations of (at least) the protocol parsing code. This
+    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>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>
+    <p>It would help if you're already familiar with event-based programming,
+    bonus points if it's Twisted.</p>
+    </li>
+
     <!--
     <a id="orbot-userInterface"></a>
     <li>