> On 13 Feb 2018, at 06:32, David Goulet <dgou...@torproject.org> wrote:
> Hello everone!
> As an effort to better organize our 0.3.4.x release for which the merge window
> opens in 3 days (Feb 15th, 2018), we need to identify the enhancement(s) that
> we want so we can better prioritize the development during the merge window
> timeframe (3 months).
> Each feature should have its ticket marked for 0.3.4 milestone and with an
> Owner set so we know who is "leading" that effort. It doesn't have to be the
> person who code the whole thing but should be a good point of contact to start
> with (and it can change over time as well).
> It is possible that an enhancement can have more than one ticket so in this
> case, please make a "parent" ticket that explains the whole thing and child
> tickets assigned to it.
> The network team just had its weekly meeting and if I recall correctly, these
> enhancement should be planned for 0.3.4 (please the people who works on this,
> can you tell us the tickets and make sure they are up to date?)
> - Privcount (prop#280)

Now superseded by prop#288. We expect at least one more proposal for the
PrivCount counter config format.

#22898: Help get privcount standardized and merged

#23147: prop288: Merge privcount-in-tor data collector backend implementation
#25153: Specify how PrivCount in Tor statistics are configured and interpreted

As a stretch, we could implement part of the Tally Reporters (see prop#288).

While I am implementing PrivCount in Rust, I will also fix or replace similar
code in the C statistics implementation:

#25263: Fix the hidden service statistics noise

> If you plan to do a set of patches for a feature or enhancement, please do
> submit it on this thread and make sure a proper ticket exists with an Owner.

There are a lot of other things I'd like to do in 0.3.4, but I think I
should focus on PrivCount in Tor.



PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B

tor-dev mailing list

Reply via email to