Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards

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.

  • The Tor Project
  • Anti-censorship
  • trac
  • Issues
  • #31523

Closed
Open
Opened Aug 26, 2019 by Philipp Winter@phwOwner

Recruit potential default bridges from set of long-running bridges

We would like to set up more default bridges. One way to recruit more is to look for non-default bridges that have 1) high capacity, 2) have been around for a long time, and 3) have a stable uptime. Ideally, we should also know the person who runs the bridge, as stated in our list of criteria for setting up a new default bridges.

Let's have a look at archived bridge data and extract a list of default bridge candidates.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/anti-censorship/trac#31523