[tor-bugs] #16756 [Pluggable transport]: Formalize and document what it takes for a PT to get deployed.

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#16756: Formalize and document what it takes for a PT to get deployed.
---------------------------------+-------------------------
 Reporter:  yawning              |          Owner:  yawning
     Type:  task                 |         Status:  new
 Priority:  normal               |      Milestone:
Component:  Pluggable transport  |        Version:
 Keywords:  SponsorS             |  Actual Points:
Parent ID:                       |         Points:
---------------------------------+-------------------------
 It would be good to formalize what it takes to get a PT to be considered
 for deployment beyond the rough guidelines we have as part of our Sponsor
 S/T draft.  I have some ideas here about things that should be considered
 that aren't, that other people are likely to disagree about, so discussion
 is needed.

 The last 3 PTs that got deployed were FTE, ScrambleSuit and obfs4.
  * What did we do?
  * Out of what we did, what was right?
  * Out of what we did, what was wrong?
  * What did we consider that we should ignore in the future?
  * What did we not consider that we should in the future?
  * Who's going to do all the evaluation work?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16756>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs