Decide the fate of MyFamily
See discussion on legacy/trac#5565 (moved) and legacy/trac#6676 (moved). It may be that the family declaration is making guard selection worse, and if so, maybe we should not do guard selection in the same way. Having some paths with all three nodes in the same family scares me, though.
We could do better than the current family system using certs as described in prop220. First we should decide whether we want to keep families at all, though.
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Nick Mathewson changed milestone to %Tor: unspecified in legacy/trac
changed milestone to %Tor: unspecified in legacy/trac
- Nick Mathewson added component::core tor/tor in Legacy / Trac milestone::Tor: unspecified in Legacy / Trac myfamily in Legacy / Trac needs-design in Legacy / Trac needs-proposal in Legacy / Trac network-health in Legacy / Trac priority::medium in Legacy / Trac severity::normal in Legacy / Trac status::new in Legacy / Trac tor-relay in Legacy / Trac type::enhancement in Legacy / Trac labels
added component::core tor/tor in Legacy / Trac milestone::Tor: unspecified in Legacy / Trac myfamily in Legacy / Trac needs-design in Legacy / Trac needs-proposal in Legacy / Trac network-health in Legacy / Trac priority::medium in Legacy / Trac severity::normal in Legacy / Trac status::new in Legacy / Trac tor-relay in Legacy / Trac type::enhancement in Legacy / Trac labels
- Author Owner
Trac:
Status: new to assigned Trac:
Username: tyseom
Cc: N/A to nusenu@openmailbox.org- Author Owner
Marking triaged-out items from first round of 0.2.7 triage.
Trac:
Keywords: N/A deleted, 027-triaged-1-out added - Author Owner
Make all non-needs_review, non-needs_revision, 027-triaged-1-out items belong to 0.2.???
Trac:
Milestone: Tor: 0.2.7.x-final to Tor: 0.2.??? - Author Owner
Bulk-replace SponsorU keyword with SponsorU field.
Trac:
Keywords: SponsorU deleted, N/A added
Sponsor: N/A to SponsorU - Reporter
Trac:
Sponsor: SponsorU to SponsorU-can - Author Owner
Remove the SponsorU status from these items, which we already decided to defer from 0.2.9. add the SponsorU-deferred tag instead in case we ever want to remember which ones these were.
Trac:
Keywords: N/A deleted, SponsorU-deferred added
Sponsor: SponsorU-can to N/A - Author Owner
Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.
Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified - Author Owner
Remove an old triaging keyword.
Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added - Author Owner
Trac:
Keywords: N/A deleted, 027-triaged-in added - Author Owner
Trac:
Keywords: 027-triaged-in deleted, N/A added - Author Owner
Trac:
Keywords: 027-triaged-1-out deleted, N/A added - Author Owner
Change the status of all assigned/accepted Tor tickets with owner="" to "new".
Trac:
Status: assigned to new - Author Owner
Trac:
Reviewer: N/A to N/A
Severity: N/A to Normal
Keywords: SponsorU-deferred deleted, needs-design myfamily tor-relay added - Reporter
Trac:
Keywords: N/A deleted, network-health added - Roger Dingledine mentioned in issue legacy/trac#21864 (moved)
mentioned in issue legacy/trac#21864 (moved)
- Trac moved from legacy/trac#15060 (moved)
moved from legacy/trac#15060 (moved)
- Trac added Needs Proposal Relay Research + 1 deleted label and removed 1 deleted label
added Needs Proposal Relay Research + 1 deleted label and removed 1 deleted label
- Author Owner
Looks like we are keeping myfamily, and improving it with something like proposal 321
- Nick Mathewson closed
closed
- Gaba added Network health label and removed 1 deleted label
added Network health label and removed 1 deleted label