Opened 2 months ago

Last modified 2 months ago

#30971 new task

Rebuild the fallback list in late 2019 or early 2020

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.4.2.x-final
Component: Core Tor/Fallback Scripts Version:
Severity: Normal Keywords: 042-should-maybe, fallback
Cc: gus, teor Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by teor)

Late in 2019, or early in 2020, we should rebuild the fallback list again.

We usually do this when 25% or more go down.
(When 25% of fallbacks are down, a warning is logged daily in #tor-bots on IRC, and via email to the fallback maintainers.)

Here are the instructions for running a rebuild:
https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors

See the child tickets for each step.

Child Tickets

TicketStatusOwnerSummaryComponent
#28863needs_informationupdateFallbackDirs.py thinks it is python 3 compatible but it is notCore Tor/Fallback Scripts
#28987newAdd a log level option to the fallback scriptCore Tor/Fallback Scripts
#30972new0-1. Run an opt-in process for relay operators to become fallbacks in 2019-2020Core Tor/Fallback Scripts
#30973new2-3. Generate a new fallback list in 2019-2020 and backport it to all supported Tor versionsCore Tor/Fallback Scripts
#30974new4-5. Announce the new fallback list, and tell downstream maintainers that it has changedCore Tor/Fallback Scripts
#31305closedteorAdd more useful logging to fallback scripts variable configCore Tor/Fallback Scripts

Change History (2)

comment:1 Changed 2 months ago by teor

Description: modified (diff)

comment:2 Changed 2 months ago by teor

Description: modified (diff)
Note: See TracTickets for help on using tickets.