Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Wiki
    • Org
    • Roadmaps
  • CoreTor

Last edited by Alexander Færøy Jun 15, 2020
Page history

CoreTor

STATUS COLOR CODE:

  • GREEN = WILL GET DONE BY EOM
  • YELLOW = MOST OF IT DONE BUT NOT FINISHED BY EOM
  • RED = EITHER DECIDED TO DROP IT OR JUST STARTED THE TASK OR IS MOVING TO THE NEXT MONTH

Previous roadmaps

  • Valencia 2016 Winter Dev Meeting Roadmap
  • Tor Berlin 2015 Summer Dev Meeting Roadmap
  • Valencia 2015 Winter Dev Meeting Roadmap

Prep work for Core Tor 2016 Summer Roadmap

These proposals are submitted but not yet accepted, so the exact content (and funding status!) of any final version is in doubt. They might start as soon as 1 Nov, or some time after.

Nick helped write the deliverables; please get mad at him if they seem stupid. :)

Proposal 1:

Timeframe for proposal 1 - 12 months

Subobjective 1.1: Build a standardized software-to-software interface layer (API set) for Tor Networks

  • Activity 1: Investigate existing APIs in this space
  • Activity 2: Design an API
  • Activity 3: Investigate applications most in need of this functionality, reach out to developers in those spaces.
  • Activity 4: Implement and test API.
  • Activity 5: Document API.
  • Activity 6: Teach developers about it, making sure it looks good for them

Devs: 2

Time estimated: 6 to 9 months

Subobjective 2.1: Reduce Tor processing overhead for low-bandwidth scenarios.

  • Activity 1: Improve the Directory Authority consensus part of the Tor network in order to optimize low bandwidth users experience.

Devs: 2

Time estimated: 4.5 to 6 months


Proposal 2:

**Timeframe for proposal 2: ** 24 months

Objective 1: Modularize the Tor Network (“Core Tor”) architecture

  • Top-down redesign and documentation of modular interactions.
  • Refactor modules.
  • Revise module callgraph.
  • Create support for replacing modules with components written in higher level languages.
  • Create support for isolating existing modules into separate processes.

Devs:

Time estimated:


Proposal 3:

Timeframe for proposal 3: 24 months

Objective: Improve user experience for mobile users connected to Tor network.

  • Investigate if Tor Network sandboxing option works with mobile devices and
  • Implement network sandboxing for mobile, if possible.
  • Improve the Tor Network’s controller interface to allow mobile apps to better control bandwidth and battery use.

Devs:

Time estimated:

Clone repository
  • AnonOnWikiFavs
  • AppArmorForTBB
  • AutomationInventory
  • BadContent
  • BlockingBittorrent
  • CI
  • CamelCase
  • CrowdfundingHS2015
  • FlashProxyFAQ
  • FlashProxyHowto
  • FlashProxyUsability
  • HTTPSEverywhere
    • SSLObservatorySubmission
  • ImportantGoogleChromeBugs
  • InterMapTxt
  • InterTrac
View All Pages