Evaluate feasibility of a Python obfsproxy and possibly get it started
Item 19 from org/sponsors/SponsorF/Year2 is: "evaluate feasibility of a python equivalent to obfsproxy, to make it easier for people to write transports in python. See also Brandon Wiley's "dust". If we decide it's smart, get it started."
There are a few substeps here: first, we should discuss feasibility of a Python obfsproxy; maybe we need some proof-of-concept implementation to further evaluate things we cannot solve by discussion; then we need to make a decision; and finally, if we decide that having a Python obfsproxy is a good idea, we'll have to get it started.
Creating a child ticket for the discussion part. Further substeps should get their own child tickets.
We need to decide whether this is a July or November deliverable (optimistically assigning to July), and we need somebody to lead the deliverable.
There are quite a few people who I've heard might be interested in this topic and who I'm cc'ing: nickm, asn, aagbsn, blanu, zwol, xmux. If more people are interested, please cc yourself.