Create a blog post about work done and future work

changed milestone to %sbws: 1.1.x-final

added component::core tor/sbws docs milestone::sbws: 1.1.x-final no-changes-version owner::juga points::1 priority::medium resolution::implemented reviewer::asn reviewer::steph reviewer::teor severity::normal status::closed type::defect version::sbws 1.0.5 labels

Add keyword to help planify releases/milestones. Tickets that doesn't imply a change of version are tickets which do not affect the code (docs, tests) and some time of refactors.

Trac:
Keywords: N/A deleted, no-changes-version added

Add keyword. docs are tickets that affect to documentation

Trac:
Keywords: N/A deleted, docs added

I should work on this this week so that it can be reviewed with 1 week in advance.

Trac:
Status: new to accepted
Owner: N/A to juga

https://pad.systemli.org/p/vT4ovkGst9hoajLIXhJm

Trac:
Status: accepted to needs_review

I reviewed the post in the pad. Someone else should review next.

Trac:
Reviewer: N/A to teor
Status: needs_review to needs_revision

i changed some of the things teor commented, still is missing the equilibrium goal which it seems teor will do in #28582 (moved). I'd still be awesome if someone else do a 2nd review

Trac:
Status: needs_revision to needs_review

Trac:
Cc: juga to juga, asn
Reviewer: teor to N/A

Replying to juga:

i changed some of the things teor commented, still is missing the equilibrium goal which it seems teor will do in #28582 (moved).

Eventually, I will turn #28582 (moved) into a pull request for the bandwidth-file-spec. But if you want text for the blog post, you should copy it from #28582 (moved) and rewrite it.

I'd still be awesome if someone else do a 2nd review

asn, can you assign someone to do a blog post review this week? mikeperry probably can't do a review, because he is busy.

It's kinda hard to assign reviews in the midweek, so I did a review myself.

There are currently lots of open comments on the pad, that ideally should be wiped or crossed-out to make sure they've been considered/resolved.

Also, perhaps this should go to the blog sooner-than-later to actually be able to see it's final form, and discuss structure etc.?

Trac:
Status: needs_review to needs_revision

This is something that could be included in the https://blog.torproject.org . Ccing Steph here.

Trac:
Cc: juga, asn to juga, asn, stephw

Again arrived late for the week review assinments :) There's a new version in https://pad.systemli.org/p/qz1gyqsBpFDRebUN-FqZ that we think could be final one. I'm putting this in review in case someone would like to have a last look, otherwise it could be just published.

Trac:
Status: needs_revision to needs_review

I did a review, and made some changes for readability and accuracy.

Juga, who is going to monitor comments on the blog post for the next 2 weeks?

Trac:
Status: needs_review to merge_ready
Reviewer: N/A to teor, asn, steph

Thanks a lot for the review. stephw and i are going to monitor the the comments.

Since the post has been published (https://blog.torproject.org/how-bandwidth-scanners-monitor-tor-network) i think this ticket can be closed.

Trac:
Resolution: N/A to implemented
Status: merge_ready to closed

closed

changed time estimate to 8h

moved to tpo/network-health/sbws#29724 (closed)