Opened 3 years ago

Closed 3 years ago

#20173 closed task (fixed)

Tell 0.2.9 fallback directory operators that their relays are on the list

Reported by: teor Owned by: teor
Priority: Medium Milestone:
Component: Core Tor/Fallback Scripts Version:
Severity: Normal Keywords: fallback
Cc: Actual Points: 2
Parent ID: #18828 Points: 2
Reviewer: Sponsor:

Description

Thank them, and remind them to keep their relay details the same.

I am hoping the community team can help me out with this, if I provide a list.

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by teor

Actual Points: 0.3
Component: CommunityCore Tor/Tor
Milestone: Tor: 0.3.0.x-final
Owner: set to teor
Parent ID: #20172#18828
Status: newassigned

I plan to send out an email with a draft list this weekend:

  • BCC all the operators in an email, then forward that email to tor-relays with a note in the header. This helps operators know whether they are in or not.
    • (This is a copy of the email I BCC'd to each relay operator on the draft list. You can still opt-in your relays any time. The list will be rebuilt with any new relays in a week, and then in 6-12 months time.)
  • if you are receiving this email, your relay(s) have been selected as fallback directory mirrors for tor
  • we are taking 3 relays per operator, if you only have 1 or 2 on the list, please feel free to opt-in more
  • make a list of those factors that operators can fix
  • if they can't fix it straight away, we will rebuild the list again in 6-12 months, so maintain stability and flags during that time
  • email me to have your relay taken off, if you know it will move or go down in the next 2 years
  • include a copy of the original tor-relays email forwarded at the bottom of that email
  • try not to repeat myself or be too verbose

comment:2 Changed 3 years ago by teor

I also want to compare the old fallback network diversity in
https://trac.torproject.org/projects/tor/ticket/18749#comment:12
with the network diversity for the new fallbacks.

comment:3 Changed 3 years ago by teor

Actual Points: 0.31

The network diversity still looks pretty good, even though we've added 3 per operator.

I just sent this email with the draft list:
https://lists.torproject.org/pipermail/tor-relays/2016-December/011330.html

I'll send out one more email after I create the final list, but only to the operators who have been added or removed.

comment:4 Changed 3 years ago by nickm

Component: Core Tor/TorCore Tor/Fallback Scripts
Milestone: Tor: 0.3.0.x-final

Batch-move updateFallbackDirs.py tickets into a new component, and remove them from maint-0.3.0.

I'm doing this as a separate component, after discussion with teor, mainly because development here seems to be decoupled from development on tor itself: they don't need to have the same release schedules, for example.

comment:5 Changed 3 years ago by teor

Actual Points: 12
Resolution: fixed
Status: assignedclosed

This is done, but it would have been much better to do it by sending a group email, and CC'ing tor-relays.

Note: See TracTickets for help on using tickets.