Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P pluggable transports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • pluggable transports
  • Issues
  • #16756
Closed (moved) (moved)
Open
Created Aug 10, 2015 by Yawning Angel@yawning

Formalize and document what it takes for a PT to get deployed.

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?
Assignee
Assign to
Time tracking