PrivCount noise specification

changed milestone to %Tor: unspecified

added 040-unreached-20190109 041-accepted-20190115 component::core tor/tor milestone::Tor: unspecified needs-proposal parent::25153 points::3 priority::low privcount severity::normal status::new teor-unreached-2019-03-08 type::defect labels

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

Here are the notes from the PrivCount Technical Issues session: https://trac.torproject.org/projects/tor/wiki/org/meetings/2018MexicoCity/Notes/PrivCountTechnical

They are mainly about noise.

Trac:
Sponsor: N/A to SponsorV

Tor 0.3.6.x has been renamed to 0.4.0.x.

Trac:
Milestone: Tor: 0.3.6.x-final to Tor: 0.4.0.x-final

These tasks are on the 0.4.1 roadmap for PrivCount and Sponsor V.

Trac:
Milestone: Tor: 0.4.0.x-final to Tor: unspecified
Keywords: N/A deleted, 041-proposed, 040-unreached-20190109 added

Let's review these tickets at the next meeting using our 041-proposed process.

They're on the roadmap, so the review should focus on ticket size and team capacity (and sponsor expectations).

Trac:
Keywords: 041-proposed deleted, 041-proposed-on-roadmap added
Milestone: Tor: unspecified to Tor: 0.4.1.x-final

Trac:
Points: N/A to 3

These PrivCount tickets are on the 041 roadmap, we accepted their points estimates in 041 without discussion.

Trac:
Keywords: 041-proposed-on-roadmap deleted, 041-accepted-20190115 added

The PrivCount proof of concept must have bandwidth. Everything else is optional.

Trac:
Keywords: N/A deleted, teor-unreached-2019-03-08 added
Priority: Medium to Low
Sponsor: SponsorV to SponsorV-can
Milestone: Tor: 0.4.1.x-final to Tor: unspecified
Owner: teor to N/A

Trac:
Sponsor: SponsorV-can to N/A

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

Trac:
Status: assigned to new

changed time estimate to 24h

moved to tpo/core/tor#27906 (closed)

PrivCount noise specification

Child items 0

Activity