Alter flag-weight balancing equations

I have a few things I want to do to the flag-weight equations. This ticket will eventually be the parent ticket, but for now it's just a brain-dump:

1. I definitely want to correct the balancing issues discussed in #8240 (moved).
2. I might want to account for changes due to directory guards (#7757 (moved)).
3. I might want to factor in an optional Guard/Middle padding parameter. (#7028 (moved))
4. I might want to factor in an estimate of hidden service traffic somehow.

changed milestone to %Tor: unspecified

added 034-removed-20180328 034-triage-20180328 SponsorZ component::core tor/tor milestone::Tor: unspecified needs-proposal performance points::6 priority::medium severity::normal status::new tor-client type::enhancement labels

Trac:
Description: I have a few things I want to do to the flag-weight equations. This ticket will eventually be the parent ticket, but for now it's just a brain-dump:

1. I definitely want to correct the balancing issues discussed in #8240 (moved).
2. I might want to account for changes due to directory guards (#7752 (closed)).
3. I might want to factor in an optional Guard/Middle padding parameter. (#7208 (closed))
4. I might want to factor in an estimate of hidden service traffic somehow.

to

I have a few things I want to do to the flag-weight equations. This ticket will eventually be the parent ticket, but for now it's just a brain-dump:

1. I definitely want to correct the balancing issues discussed in #8240 (moved).
2. I might want to account for changes due to directory guards (#7757 (moved)).
3. I might want to factor in an optional Guard/Middle padding parameter. (#7028 (moved))
4. I might want to factor in an estimate of hidden service traffic somehow.

Trac:
Keywords: SponsorZ, performance deleted, performance SponsorZ tor-client added

Also, #8356 (moved) might involve the same sort of data. Might be worth looking at along the way.

See also #2395 (moved).

Trac:
Keywords: performance SponsorZ tor-client deleted, performance SponsorZ tor-client mike-0.2.5 added

Trac:
Keywords: performance SponsorZ tor-client mike-0.2.5 deleted, performance SponsorZ needs-proposal tor-client mike-0.2.5 added

Trac:
Milestone: Tor: 0.2.5.x-final to Tor: 0.2.???

Trac:
Parent: N/A to #9321 (moved)

Trac:
Cc: N/A to isis

Trac:
Parent: #9321 (moved) to N/A

Trac:
Keywords: performance SponsorZ needs-proposal tor-client mike-0.2.5 deleted, performance SponsorZ needs-proposal tor-client mike-0.2.5 028-triage added

Trac:
Sponsor: N/A to N/A
Milestone: Tor: 0.2.??? to Tor: 0.2.8.x-final

Trac:
Points: N/A to large

At the very least, I need to get at least get a proposal for this out in November, so we can consider it in combination with #16861 (moved).

Trac:
Keywords: performance SponsorZ needs-proposal tor-client mike-0.2.5 028-triage deleted, performance SponsorZ needs-proposal tor-client mike-0.2.5 028-triage TorCoreTeam201511 added
Severity: N/A to Normal

Bulk-move uncompleted items to december. :/

Trac:
Keywords: performance SponsorZ needs-proposal tor-client mike-0.2.5 028-triage TorCoreTeam201511 deleted, mike-0.2.5, TorCoreTeam201512, 028-triage, 201511-deferred, performance, tor-client, SponsorZ, needs-proposal added

I'd look at a patch for these if we got one, but AFAIK nobody's looking at them right now, and there's no reason to expect them to get done this month.

Trac:
Keywords: TorCoreTeam201512 deleted, N/A added

It is impossible that we will fix all 226 currently open 028 tickets before 028 releases. Time to move some out. This is my second pass through the "new" and tickets, looking for things to move to 0.2.9.

Trac:
Milestone: Tor: 0.2.8.x-final to Tor: 0.2.9.x-final

Trac:
Sponsor: N/A to SponsorU-can
Reviewer: N/A to N/A

Trac:
Keywords: N/A deleted, tor-sponsorU-orphan added

Trac:
Points: large to 6

Deferring more things -- even ones I love -- to 0.3.0. Please argue if I'm wrong.

Trac:
Milestone: Tor: 0.2.9.x-final to Tor: 0.3.0.x-final
Keywords: N/A deleted, nickm-deferred-20161005 added

Triaged out on December 2016 from 030 to 031.

Trac:
Keywords: N/A deleted, triage-out-030-201612 added
Milestone: Tor: 0.3.0.x-final to Tor: 0.3.1.x-final

Clear sponsorS and sponsorU from open tickets in 0.3.1

Trac:
Sponsor: SponsorU-can to N/A

0.3.1 feature freeze today: these don't seem like they will be all sorted out in time. Let's try to make progress in 0.3.2.

Trac:
Milestone: Tor: 0.3.1.x-final to Tor: 0.3.2.x-final

Trac:
Keywords: mike-0.2.5, 028-triage, 201511-deferred, nickm-deferred-20161005, tor-sponsorU-orphan, triage-out-030-201612 deleted, N/A added

Trac:
Milestone: Tor: 0.3.2.x-final to Tor: 0.3.3.x-final

Trac:
Sponsor: N/A to SponsorV-can

Deferring various "new"-status enhancement tickets to 0.3.4

Trac:
Milestone: Tor: 0.3.3.x-final to Tor: 0.3.4.x-final

Trac:
Keywords: N/A deleted, 034-triage-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

Trac:
Keywords: N/A deleted, 034-removed-20180328 added

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

Trac:
Milestone: Tor: 0.3.4.x-final to Tor: unspecified

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

Trac:
Sponsor: SponsorV-can to N/A

Trac:
Cc: isis to isis, mikeperry
Owner: mikeperry to N/A
Status: new to assigned

Change tickets that are assigned to nobody to "new".

Trac:
Status: assigned to new

changed time estimate to 48h

mentioned in issue #9321 (moved)

mentioned in issue #24456 (moved)

mentioned in issue #29098 (moved)

moved to tpo/core/tor#8453 (moved)

mentioned in issue tpo/core/tor#9321 (closed)