[tor-dev] Proposing sbws changes

[teor]

Hi all,

We finished our first working version of sbws in March, and deployed
it to a directory authority. We're now working on deploying it to a
few more directory authorities:
https://trac.torproject.org/projects/tor/ticket/29290

We're also working on archiving and analysing the bandwidth files
produced by sbws and Torflow:
https://trac.torproject.org/projects/tor/ticket/21378

During this work, we've discovered some missing sbws features:
https://trac.torproject.org/projects/tor/ticket/30255

We need a better process for proposing and reviewing sbws changes.

At the moment, I am spending a lot of time reviewing and designing
sbws changes. And that's not sustainable. We need a process that works
when I go on leave, or get busy with other tasks.

I suggest that we use the tor proposals process:
https://gitweb.torproject.org/torspec.git/tree/proposals/001-process.txt

We can submit small changes as diffs to the bandwidth file spec:
https://gitweb.torproject.org/torspec.git/tree/bandwidth-file-spec.txt

But large changes, controversial changes, and changes with multiple
competing options should have their own proposal. Then, once we decide
what to do, we can integrate those changes into the spec.

T

--
teor
----------------------------------------------------------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20190422/a10e1d2b/attachment.sig>